Sprint 120 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 (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.
Tomislav made good progress this last week on the finalization and Block merge (LLBM) code with simple protocol (i.e. potential network partitioning ignored). There are some bugs he discovered and is methodically working through these. Once these are resolved, we should be able to release the 0.13.Beta1 version to the test net. Nutzipper is on a short summer vacation and Tomislav will be taking a break after the 0.13.Beta1 release is on the test net.
The team has been simplifying and improving the testing framework to make writing and running the tests fast. Stas has been leading the charge on this and making good progress.
We are inviting rholag-knowledgeable community resources to provide some informal auditing of the PoS contract changes.
Denis and Nutzipper made good progress on the work with the external customer project.
Roadmap: We will be updating the roadmap in the next couple of weeks taking into consideration the near-term foreseeable external customer requirements and any R&D grant applications we may make, in addition to the core platform requirements. The main focus the rest of 2022 would be to stabilize the external validator version of the code. Most, if not all Mercury version requirements are being delivered as part of Hard Fork 2. So the project will be entering a new phase and the roadmap planning conversations are more intricate and involved.
Current closed list of PRs is at https://github.com/rchain/rchain/pulls?q=is%3Apr+sort%3Aupdated-desc+is%3Aclosed Current full PR list is at https://github.com/rchain/rchain/pulls?q=is%3Apr+sort%3Aupdated-desc+is%3Aopen . Project progress is at https://github.com/rchain/rchain/projects/4 Latest updates to the issues list are at https://github.com/rchain/rchain/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc
External validator engagement as well as customer/market engagement continues.
Development Plans for the rest of the year and beyond - for reference
Near term plans and releases are as below:
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.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.
|