Testnet 0.13.0 had been running Since about March the 10th. This is the Single parent block merge version. All block merge code is now on the testnet, but finalization needs to be worked on and that is the current focus of the team. Current version on this LLBM test net is 0.13.0-alpha2, which fixes a memory issue in the 0.13.0-alpha version. There's a new 0.13.0-alpha3 release that enables testing the sharding related behavior but this will not be released to the testnet at this time. It is being made available only for individuals that want to test the sharding functionality (e.g. Dappy).
There were two planned hard forks: Hard Fork 2 for block merge (release versioning will be 0.13.x) and Hard Fork 3 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. Most of the Hard fork 3 changes are now likely to be included in Hard Fork 2. We will do a Hard Fork 3 only if needed.
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 (f) Prepare for trusted external validators in order to decentralize the network.
Other work includes resolving any identified bugs, hardening the network and working with external customers.
The team continues to make good progress on finalization using the simple protocol (i.e. ignoring any potential network partition where a part of the network is too slow to respond). Tomislav has issued a draft PR on refactoring Block metadata https://github.com/rchain/rchain/pull/3688 He expects to complete this code by tomorrow, to be then reviewed by the team. While working on finalization, he identified more parts of the code that need to be refactored. He will be doing that over the next few days.
Will is cleaning up last pieces of his work on registry update as a soft fork, implementing the PR review comments. He will be specifying and working on changing the calculation for random seed. Max will be implementing the scodec part of this task. Max was working on improvements and tests for the new RadixHistory implementation, working with Denis.
Nutzipper has completed refactoring deploy storage and the API changes necessary to get the enhanced deploy information https://github.com/rchain/rchain/pull/3682. There is a follow on PR needed to complete the epic. He also added a refactoring PR necessary to complete the task https://github.com/rchain/rchain/pull/3692. In addition, he has been working on generating rholang deploys in Scala based on RabbitMQ topics for integration with external systems. This exercise is useful in helping us understand what functionality to provide in future inside RNode, to simplify this kind of integration in future.
Denis has completed for now his investigations to improve performance of the Rholang map and other Rholang primitives. While some improvements can be implemented now, the full scope of improvements requires extensions and modifications to the reducer as well fully implementing the Rholang v1.1. This is a multi-week or multi-month effort scheduled for 2022 H2 and cannot be completed in the time frame for hard fork 2. He is documenting his learning and what needs to be done when he returns to this task later. He is switching to implementing the BigInt type in Rholang, which is a multi-PR task. There is a specific demand from the community for this https://github.com/rchain/rchip-proposals/issues/51
Substantial market engagement is underway with enterprise customers, systems integrators and others that want to develop and deploy solutions on the RChain platform.
Reminder: It's important for all Wallet makers to update their code to match the new implementation where minimum phlo price is a parameter. Please communicate this to any wallets you are using. Wallets will have to call /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#phlopriceWe 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:
Block merge release hard fork 2 plus any configuration changes that do not need extensive work - Leaderful and Leaderless block merge
Potentially one or more releases for Configuration changes and/or performance improvements,
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 + trusted third parties validation on the main net
External validators among extended ecosystem (e.g. exchanges, if they're willing)
External validators in the wild
Feature releases driven by external market engagement
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.
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