Update #2 [07 - 11 September]
Short update on the development progress.
CC: @yani.chain @sergiimaksiuta.chain
What was done this week:
- We finished and merged the initial Hyperchain parent DB
- We finished and merged initial Hyperchain parent conector
- Created a Chain Simulator parent connector
- Sophia compiler refactoring for the necessary Erlang ACI helper library
What we are working on right now:
- Sophia smart contract ACI helper
While working on the Staking contract deployment in HC and running benchmarks of our Sophia compiler it turned out that it is infeasible to ship hyperchains together with the compiler for encoding/decoding call data as the compiler would introduce a nasty bottleneck in block validation times - somewhere around 2-3 seconds for validating a single header… The ACI library is the only sensible option for proceeding further and will replace the compiler in some places in the node test suite.
- Chain simulator improvements
The state channel test suite provided a chain simulator for testing various forking scenarios - after we started testing our Staking Contract it turned out that the only sensible way to test it is by using the chain simulator. Unfortunetelly as the Simulator was designed only for SC we are now in the progress of major refactorings to allow testing smart contract behavior during forking scenarios.
- Connector DB integration
Save the data obtained from the parent chain in our DB
- Parent chain connector manager
Manage parent chains and keep track of hard forks(changing the parent chain over the lifetime of the Hyperchain)
@radrow @erlmachinedev1.chain Did I miss something?
Keep in mind that if [Active] Aeternity node maintenance - iris hard fork release candidate doesn’t get approved then some more important tasks listed in the proposal will become part of the Hyperchains project(Fast Sync, Peer pool fix, etc…).