Covering July 8 – July 16
|Jul 16||Public post|
Zack Hess simplifies the new lisp smart contract for markets, added comments and changed variables names. More info here.
Amoveo Community describes every step of the crowdfunding process with a detailed guide on how to create fundraisers on Amoveo. Check it out here.
Amoveo.io launches the community-dedicated forum and published first public contract.
Zack Hess presents a new macro that acts as a compiler. You can feed it lisp code, and it compiles it into a chalang program.
The chalang lisp macro system was used by Zack to write a lisp macro system. This proves that with chalang lisp, anyone can now use any syntax for both run-time and compile-time computation.
The update of the light node now allows both participants to keep a copy of the bytecode of the contract.
From now you can make macros that generate macros and it keeps track of the context lexically.
The binary market smart contract was rewritten into lisp. The binary it compiles to is about 15% longer than the fourth version.
There are 15 open issues in the Amoveo depo.
There were 10 commits created in 2 repositories.
Digital assets exchange qTrade launches a special topic on Amoveo forum, dedicated to discussing qTrade, its policies, suggestions for features or improvements.
Here’s a weekly hashrate graph provided by Sy:
URL to share this article: https://amoveo.substack.com/p/18-amoveo-community-forum-and-guide
This newsletter is curated by Denis Foster, for the Amoveo community. Any views expressed are personal.
If you are a developer working on an Amoveo-related product, or have any suggestions, feedback, ideas and articles that you think should be mentioned in this newsletter, contact me via Email.