The Aeternity Foundation (ACF) supports the aeternity protocol and ecosystem.
The ACF is giving funding grants for application on the promotion of the success and growth of the aeternity ecosystem as well as the ae blockchain maintenance. Weekly detail reports on the progress of the developers can be found in the Active Grant Applications under the forum’s ACF Grant Category.
Our goal remains the same: to make the aenode faster, better and lighter and the ae ecosystem more attractive for the users. The hyperchain network using the aenodes has been designed to attract the Aeternity enterprise customers and their users. On top of the faster aeternity network and hyperchain network the decentralized applications (dapps) can be run with higher performance and in a private context. Therefore, the whole aeternity ecosystem will perform with higher availability, scalability, security and performance.
Short review of the worked tasks in Roadmap Q4 2021:
AeCanary received a refactoring and some new services have been added. Devmode was polished with some bugfixing. It proved to be a sufficiently useful for the development and the testing. The node operator interface was implemented. Both a CLI and a complementary group of HTTP endpoints can be used presently by the developers. The node GUI launcher is almost done and is to be release publicly soon. There have been quite a few challenges in order to get the graphics right. The node already compiles under M1 CPU. The M1 architecture docker image will be deliver soon. The aeternity code now supports OTP24. Some DB refactoring was done by forking and fixing the dependent external library by the core team. Some good progress has been made on the the Rosetta API but most of the work is yet to be finished. The current GC Names process needs a refactoring. It is working for accounts cleanup. However, by adding names and contracts to it, it can be overloaded. This process depends on the DB refactoring.
The following Ceres improvements
• bitwise operations (OR, AND, XOR, NOT)
• ZK/SNARK friendly hash function(s) - Poseidon hash (+ possibly more?)
• a dedicated MULMOD instruction
were done. Additionally, some work on multisig, a pygments lexer and an improvement of the production on microblocks was done. It was introduced a new test suite implementing a prototype State Channel Market structure (using hash-locked cross-channel transfers).
The work on Hyperchains was ongoing. The Hyperchains Alpha will be release next month for test. Please note that some of the previous tasks were needed also for hyperchains.
The node will be continuously improving and the focus will be put on further HyperChains research, design and development.
AeCanary and all basic features/tools as dev mode, node modes, etc. in general will be continuously supported and improved. A support for Hyperchains need to be provided in AeCanary. Rosetta API Implementation is ongoing. A native node GUI launcher to compile the node and provide some means of inspection of the live system will be released soon. The RocksDB refactoring is needed for a stricter control over transactions. The GC Names process improvement relies on this refactoring.
Hyperchains Alpha will provide a staking smart contract. A user friendly GUI will make a staking just an easy task. It will give users the control on assets and rewards behaviour. The research and design on Hyperchains will continue.
A showcase on a state channel market is to be made.
The sync is suboptimal and needs to be speed up. An RnD project on beam sync will be started.
Aeternity mainnet already supports multisigs but the process requires a good knowledge about cryptography and Erlang. This process needs to be simplify and to be made an easily accessible.
The updates on the aeroadmap and the aerelease schedule will follow dynamically in this topic. The previous roadmap can be found on the AETERNITY ROADMAP Q4 2021.
You are welcome to contact us under the Email: [email protected]
Release Date: February 27, 2022
Type: HyperChains Test, see HyperchainsAlpha.