Sprint 111 in progress
Main Focus is to prepare the leaderless block merge Hard fork (hf2), specifically (a) complete the finalization feature for multi-parent block merge for release to Test net (b) a lot of testing + bug fixing and (c) performance improvements (d) Completed - Adding shardId inside the signatures, to enable multi-shard operation and prevent reusing of deploys from one shard in another shard (e) sdk project to make the code more modular and serve as a base for RNode domain logic with corresponding data types.
Other work includes resolving any identified bugs, hardening the network. Current PR list is at https://github.com/rchain/rchain/pulls . Project progress is at https://github.com/rchain/rchain/projects/4
The test net had been running the 0.13.0-alpha version beginning about March the 10th, which is now upgraded to the 0.13.0-alpha2 release. The release notes for the 0.13.0-alpha version are at https://github.com/rchain/rchain/releases . This has all the block merge code, but the team is currently working on the finalization code. The new alpha2 version fixes the memory issues reported with 0.13.0-alpha version.
Gurinder is testing the setting up of infrastructure on a new cloud provider. The goal is to have multiple cloud options. The experience so far is good and he should be able to run the testnets there in the next few days.
The team has made progress in implementing finalization using the simple protocol (i.e. ignoring any potential network partition where a part of the network is too slow to respond). Today Tomislav will demonstrate and explain progress to date. The code for epoch change finalization is also likely to be included in the upcoming release (0.13.1) for testnet. After that, the team will work on changes necessary for external validators and finalization in case of network partition.
Will is continuing his work on registry improvements to allow most updates as a soft fork. In addition, he has released v 0.12.6 that fixes a bug in the snapshot process. There are no other changes included in this version https://github.com/rchain/rchain/releases/tag/v0.12.6
Nutzipper and Stas are continuing the improvements and refactorings necessary for finalization. This is a significant part of the finalization work. https://github.com/rchain/rchain/pulls?q=is%3Apr+is%3Aclosed+sort%3Aupdated-desc and https://github.com/rchain/rchain/pulls?q=is%3Apr+sort%3Aupdated-desc+is%3Aopen
Denis is continuing with his work to measure and improve performance.
Max is continuing his work with the scodec based serialization and performance measurements to see if a switch makes sense.
External validators are getting familiar with running nodes on the testnet.
Substantial market engagement is underway with enterprise customers, systems integrators and others that want to develop and deploy solutions on the RChain platform.
Note:
/api/status
to get min phlo price accepted by the validator and put that value in deploy data instead of the currently used constant 1
.Tomislav has updated the wiki at https://github.com/rchain/rchain/wiki/Cost-accounting-in-RChain#phloprice We will start communications with exchanges also for HF2.Development Plans for the rest of the year and beyond - for reference
Near term plans and releases are as below:
Explanation of the different Hard Forks (for reference)
Proceeding further with block merge requires changes to the per validator vault to make it a per deploy vault/purse etc. We are currently finalizing the design for this. Actual code and test will take some time. We are potentially looking at this scenario:
1. First hard fork for balances and removing the slashed validator
2. Second hard fork for block merge - This is the fastest way to get block merge on the main net without holding it until the third hard fork. This includes REV balance merging (aka per deploy vault), attestation messages and the Tree depth being increased to four.
3. Third hard fork with all other changes. Third hard fork includes implementation of a lot of changes including the PoS contract changes, Soft fork process etc. Design for soft fork process is complete and is being reviewed by the team.
(Hard Fork) TEST NET 2 ADVISORY: (for reference)
To test the version of block merge with data changes that need a hard fork, we are creating a separate feature branch and a TEST NET 2 as the testbed for this feature branch. This content will be left here until we are close to Hard Fork 2 implementation on the main net. TestNet 2 is now available for the community to test their contracts on.
On all the hard forks on the main net, we will be starting from an empty state, with REV balances only. On Test Net 2, this 'loosing the state' will be repeated multiple times.
Tech-Governance meetings on Fridays 9:30 AM Eastern, 6:30 Am Pacific
Mercury requirements and acceptance criteria
Details on the acceptance criteria: Mercury acceptance criteria
Please see the documentation at https://github.com/rchain/rchain/blob/dev/docs/features.md.
|