Community Update 134
- Rao Bhamidipati
Owned by Rao Bhamidipati
General
- Release
- All the main net validator nodes were running release 0.9.25.2. https://github.com/rchain/rchain/milestone/8?closed=1
https://github.com/rchain/rchain/releases/tag/v0.9.25.2 We will start testing shortly, the Rnode 0.9.26-lfs-alpha on a couple of the main net observer nodes. - Test net is currently running release 0.9.25.2. Main content of 0.9.25.2 is clean up of end of epoch bonding and unbonding. Once testing is complete, all environments will run 0.9.26-lfs-alpha
- 0.9.25.1.1 and 0.9.25.2 are bug fix release on top of 0.9.25.1. Release 0.9.25.1 and is the second and substantial part of the Last Finalized State milestone. The main content in this release is DAG Store, BlockStore and LMDB improvements, using the Key Value Store implemented in 0.9.25. Node catch up is now much improved. This release also includes many bug fixes including for the slashing /tuple space mismatch bug reported earlier. gRPC behaviour is improved with per validator grpc channel
- Release 0.9.26 will complete Last Finalized State and is a major milestone. It's currently being tested and more tests need to be written. Open PRs list at https://github.com/rchain/rchain/pulls the ones attached to 0.9.26 milestone
- Sequence of updates is testnet to mainnet observers and then main net validators if applicable. Current philosophy is to minimize updates/disruptions to validator nodes while enabling improved observer node functionality.
- Main difference between testing on Observer nodes vs. Validator nodes: When we test on the observer node, a large part of the code base is executed. The Block creation code runs only on the validator nodes. As a part of that, the portion of the Runtime Manager that plays the deploy is run on the validator node but not on the observer node.
- Main net has 20 nodes running plus observer nodes and exchange node.
- All the main net validator nodes were running release 0.9.25.2. https://github.com/rchain/rchain/milestone/8?closed=1
- Sprint 63 in progress
- Main Focus of release 0.9.26: Completing and testing Last Finalized State, identify and address as many slashing issues/bugs as possible, hardening the main net, improve performance. Current PR list at https://github.com/rchain/rchain/pulls
- Current Work In Progress
- Release 0.9.26
- In Process - Complete Last Finalized State https://github.com/rchain/rchain/pull/2913
- Completed - API changes to publish best validator to deploy to https://github.com/rchain/rchain/pull/3079
- In Process - Addressing the slow down in fork-tip calculations as the number of blocks and DAG size increase https://github.com/rchain/rchain/pull/3099 and https://github.com/rchain/rchain/pull/3100
- Completed - Implement API calls to getDataAtChannel and getContinuationAtChannel https://github.com/rchain/rchain/pull/2993 and https://github.com/rchain/rchain/issues/2992
- Fix additional identified bugs
- Release 0.9.27
- Creating a design spec and the code for how to update contracts on the main net. This will enable addressing some of the pressing issues such as faster epoch times, and other issues listed below
- Fix Rewards calculation bugs https://github.com/rchain/rchain/issues/2956
- Refactor Run Time Manager. This includes many changes including https://github.com/rchain/rchain/pull/2946
- Protection from 'too much free work' attack, policy to reject deploys when user doesn't provide sufficient phlo or does not have sufficient REV in the wallet to cover the phlo etc - https://github.com/rchain/rchain/issues/2997 and https://github.com/rchain/rchain/issues/2976
- Implement On-chain configuration and Shard configuration https://github.com/rchain/rchain/pull/2986
- Creating a design spec and the code for how to update contracts on the main net. This will enable addressing some of the pressing issues such as faster epoch times, and other issues listed below
- Ongoing - Improvements to last finalized state expected to be completed in the 0.9.26 release. Significant progress, some of which have been released in 0.9.25 and 0.9.25.1 . The PR and the branch are structured so that multiple people can collaborate/ work on different parts of the feature at the same time. The scope of this work enables (a) faster catchup by new nodes - you can start from the last finalized state - this is a differentiator for RChain (b) offloading older data, differentiated storage and retrieval strategies for the same (c) allows for a leaner / less bloated node. This change touches most parts of the code base. Having to pick between refactoring and work-arounds in various parts. Tomislav implemented a mostly modular and future-beneficial approach.
- SRE - Migration to IBM cloud
- CI/CD:
- A total of 20 validator nodes in the new epoch, new nodes set up on IBM in multiple regions.
- Will handle dependencies updates in a new repository rchain/dependencies or such, to not clutter up the main repository and hopefully allow more community collaboration on these
- Ongoing - We are slowly moving from Jira to Github for the development team, started publishing release notes in Github with release 0.9.25. New issues are entered only in github. For a while, we will maintain in both Jira and Github.
- TechGovernance:
- Thursday 10 AM Eastern. Meets alternate weeks. Meeting notes are at https://docs.google.com/document/d/1fvxMC6Bt5XwbVaLzYPy6ZPB8KzJvASO2sKRC6ZCPwpI Discussions and work on a model of economics to ensure network security is proceeding
- ToDo - There were questions from the community regarding enabling privacy and zero knowledge proofs on the chain - this is in active discussion. Greg will create a position statement on this and likely discuss the current state of the art, use cases and potential approaches in an RCast session. Same with sharding and cross-chain operation.
- In progress - Excel Model for 'economics of sustainable network security and decentralization' to enable community understanding of the inter-relationships and community conversation around these issues. Will be releasing the initial version soon. May have multiple releases.
- dApp Development:
- Dan Connolly continues to make progress on the RChat effort using zulip. SRT and possibly Will to add 'Rchain to zulip' functionality. Invite any community members with the expertise to help in this.
- Current Backlog (partial)
- Improve merging in system deploys
- Improve Casper by enabling more tests and resolving identified code issues
- Improve BlockMerge including refactoring RunTimeManager
- Improve multi-parent Casper enablement
- Implement sharding capabilities
- Improve logging to be able to learn what API calls are being used, so they can be related to resource use and performance etc
- Rholang 1.1 to improve syntax and user experience / learning curve
- Tuesday TeachOuts by Tomislav (Tuesday 10 AM Eastern, 7 Am pacific) in Jimscarver's zoom room https://zoom.us/j/6853551826
- Release 0.9.26
Tech-Governance meetings on Thursdays 10 AM Eastern, 7 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.
Testnet status
Please see RChain public testnet information to learn more about public testnet as well as a FAQ.
Tech Governance + Community testing
Thursdays at 14:00 UTC. Please see RChain community RNode testing for more information.
Blockers to Mainnet
NA
Risks to code completion for Mercury
Developer website
Date |
---|