Community Update 193
General
- Status of the networks and Releases
- Main net is running RNode version 0.12.2. This version includes the block merge code that does not require a hard fork, but block merge is currently disabled until we have the block merge version coming up in hard fork 2, aka block merge hard fork. RNode version 0.12.2 includes Will's bug fix for transaction API.
- Current test net info is at RChain public testnet information
- There two planned hard forks: one for block merge (release versioning will be 0.13.x) and one for PoS changes (release versioning will be either 0.14.x or 1.x.x) to eventually enable a fully decentralized node with external validators.
- A block merge test net (currently running the 0.12.2 version) is available for the community at node{0-4}.bm.testnet.rchain.coop, observer.bm.testnet.rchain.coop, faucet is available at https://status.bm.testnet.rchain.coop/testnet/faucet/ and Tomislav's (TypeScript) test page with block merge network support is available at https://tgrospic.github.io/rnode-client-js-dev-test/
- Both *.bm.testnet.rchain.coop and *.llbm.testnet.rchain.coop are part of hard fork 2. the llbm version has the latest code. Having the two testnets will allow the community testers to trace any unexpected behavior in their tests to the latest code changes vs. the code that has been running on bm.testnet for a while. Current state of the llbm testnet is that it requires network restart every couple of days or so. The team is resolving any bugs/ reliability issues on *.llbm.testnet.rchain.coop (Leaderless blockmerge testnet) . However, we are making it available for community testing, so we get early feedback. Community members interested in testing can request testrev for llbm in the #testnet channel. Once we determine llbm.testnet to be stable, it will become the sole testnet for hard fork 2.
Sprint 99 in progress
Main Focus is to prepare the block merge Hard fork (hf2), specifically (a) merging REV balances directly - currently on hold until other llbm issues are resolved (b) leaderless block merge - work ongoing (c) a lot of testing + bug fixing and (d) performance improvements. Other work includes resolving any identified bugs, hardening the network. Current PR list is at https://github.com/rchain/rchain/pulls .
Block merge Hard Fork (hf2)
- Welcome Tomislav back to work. The team is reviewing the recent designs for llbm bringing everyone up to speed, clarifying and prioritizing the work that needs to be done to complete HF2 and the distribution of those tasks.
- The llbm work is leading to a fair amount of restructuring and in some cases, simplification of parts of the code base. Nutzipper is continuing with fixing any bugs in the llbm code and also completing additional llbm work. Once the team design review is complete, these changes will be implemented.
- Will's PR to replay multiple times when a 'tuple space error' is encountered was reviewed and merged. The team will create release 0.12.3 shortly and try it on bm.testnet, on main net observers, and then main net validators. We ran into the tuple space error again today on the main net. Note that the source of each tuple space error may be different. We need to separately add debugging code to get more information on what all conditions are causing the error.
- Denis is working on implementing caching and further improving his algorithm for radixTree implementation of History to increase concurrency and reduce the amount of data that needs to be handled and stored.
- Besides caring for the various networks, Gurinder is working on bringing all metrics, log, event data into influxdb as a first cut, to improve observability of the network.
- Status of various Block merge tasks is at
Release Plan for the rest of the year and beyond - for reference
Currently planned near term releases are
- Block merge release hard fork 2 plus any configuration changes that do not need extensive work - Leaderful and Leaderless block merge
- Configuration changes release,
- Performance improvements releases (one or more),
- Hard Fork 3 with PoS changes and other items,
- External validators process validation with trusted community validators (aka Friends & Family) on the test net
- Friends & Family validation on the main net
- External validators among extended ecosystem (e.g. exchanges, if they're willing)
- External validators in the wild.
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 4.
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.
- There will be no guarantees of data storage format compatibility on Test Net 2, as the data storage format changes are incrementally implemented. The anticipated changes are mostly storage level format changes visible only to node operators. We encourage the community to start using Test Net 2 in addition to the current test net, so that we can quickly identify and resolve any issues with the upcoming hard forks. All new development should be targeted to TEST NET 2 and all current code MUST BE tested against TEST NET 2 to ensure future compatibility.
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.
Developer website
| Date |
|---|