Community Update 154

Owned by Rao Bhamidipati
Jan 13, 2021
7 min read

General

  • Release
    • We are in epoch 3.
    • All main net nodes (validators as well as observer nodes) are running the Last Finalized State version 0.9.26. Gurinder just completed the consolidation of the main net nodes. We will update main net to 0.10.0 at the next opportunity - there's a single commit difference between 0.10.0 and 0.9.26  https://github.com/rchain/rchain/compare/v0.9.26...v0.10.0
    • All test net nodes (validators as well as observer nodes) are running the Last Finalized State version 0.10.0  https://github.com/rchain/rchain/releases/tag/untagged-58ef9bab275dea958220
    • Main net has 30 nodes, with a few large configuration machines running 5 nodes each. 
    • We're noticing a slow daily degradation in deploys per day on the main net - we are investigating this issue.
    • 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.
  • Sprint 75 in progress
    • Main Focus is continue Block merge work, resolve any identified bugs, update dependencies, hardening the main net, improve performance.  Current PR list is at https://github.com/rchain/rchain/pulls .
    • Current Work In Progress
      • Good progress on block merge - The full team is focused on block merge. Nutzipper is close to complete on implementing the conflict resolution in a formulaic manner (i.e. check for race-free condition). The team did the initial review of the code. They are working on fixing the bugs found during review, testing and bugs discovered in the earlier code. We should soon have an early release candidate of block merge.  There will be further testing, optimization, fixing bugs and creating necessary enhancements after that. 
      • This is a partial list of what needs to be fixed as part of the block merge delivery https://github.com/rchain/rchain/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22v0.11+Block+merging%22  We will add more issues as we discover them.
      • Plan is to release block merge in small releases, into the feature branch. We will demo once the block merge branch is ready. 
      • Dependencies: We continue to work on more dependencies updates as they are available, with the eventual goal of making the code base and dependencies compatible with migration to Scala 2.13. Next on the list are the dependencies needed to prepare us to improve the monitoring framework - kamon, zipkin, influxdb, jaeger etc. Once we run well on Scala 2.13 for a few months, we should be ready to use the new reflection and other features in Scala 3.0. 
      • Rholang v1.1 (complete for now) : Joe has completed the implementation of the full source to source translation of the Rholang v1.1 syntax into current Rholang. He's resolving the last few review comments. He added tests and they're passing. The feature branch is at https://github.com/rchain/rchain/tree/feature/rholang-1.1  I encourage the community to test these releases early and often so that Joe gets the necessary testing feedback and we can move it towards deployment sooner than later. You can run a version of the node locally with this.  dckc pointed out that this can be neat developer tool meanwhile - i.e. write your contracts in rholang v1.1 to generate the rholang v1.0 code.  rholang v1.1 is much more compact and is the future. So this should be practiced by the community and developers as much as possible. 
      • Quite a lot of work needs to be done before we get Rholang v1.1 into production. We are currently planning the steps and will have some milestone updates after this planning process is complete. A fuzzer to substantially increase the testing and identify performance optimization areas is one of the immediate steps. 
      • Rholang v1.1 spec is at https://drive.google.com/file/d/1FvPuiPm7ytGyklex_PEmVyJ8XgbTdIEg/view   Most of these changes will need extensive testing when the system contracts etc. are re-written using the Rholang1.1 syntax. These changes will be in a separate feature branch and we will likely run a separate network eventually, to thoroughly test this implementation. We also need to create documentation to help end users verify their existing code and/or how to modify it to use the new syntax. The expectation is that the new syntax will make the learning curve a lot easier for people familiar with other languages. Separately, we need to update the IDE level tools to work with the new syntax.  We will run much of this through the RCHIP and Tech Governance process.
      • Ongoing - Fix additional identified bugs
      • API and usability improvements (no change this week) - in conjunction with the community
        • In Process - Will has mostly completed the OpenAPI/Swagger documentation of the RNode API  https://github.com/rchain/rchain/pull/3128  He's will try to resolve the reviewer comments after he's done with block merge work or as time permits. Familiarity with Swagger and the available swagger tools should make it easy for developers to use our API.
        • Future - Also in the thinking stage is an improvement to revdefine.io or elsewhere, a graph representation of payments / transfers on the network, with perhaps date+time and amount on the arcs.
      • Release 0.11.0 - Block merge
      • Release 0.12.0 and beyond
        • Near term road map is block merge, updating PoS contract, sharding, name spaces, Rholang v1.1. Milestone dates have been revised based on our current estimates. There will be further updates as we revise the plans.
        • 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: Finish dependency updates and plugin updates
        • To Do: Improve error logging, debugging and monitoring infrastructure. This will help improve developer productivity, both on the core team as well as dApp developers
        • Completed for now - Rholang v1.1, Refactor Run Time Manager. We may need more refactoring in future, but we want to do this incrementally, as needed. 
        • 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
      • Explanation for last finalized state (released in 0.10.0): 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.
      • Hackathon Next hackathon tentatively scheduled for some time in late February or March. 
        We need to make building the developer ecosystem an ongoing task, just like development.  Ian, Steve Henley and team are actively reaching out to as many universities and groups as possible. Please promote the much improved hackathon page at https://rchain.coop/hackathon.html to all the groups you are part of. 
        • Ongoing - We need to further increase and properly size the Problem Statements, brief sessions on tips and tricks during the hackathon, and office hours during the hackathon. We will keep adding to the problem statements.
        • Ongoing - Learning examples,  links  to and improvement of documentation.  Dan (dckc) has substantially improved the Rholang learning resources. Current plan is to make https://rholang.github.io/ the hub of all learning materials. dckc has been making substantial improvements to the learning materials as well as the API tools.  The community is requested to contribute to any or all of these.
      • CI/CD:
        • 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.  Last meeting focused on how to implement and manage shard configuration. 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. Most recent discussion was about ensuring some amount of stake beyond a 4 month window, spreading out stake over a longer time and how to incentivize that, while ensuring that everyone pays for network security.
        • 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:
        • Looking for developers to help 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 
        • Improve multi-parent Casper enablement
        • Resolve slashing bugs, including additional refactoring of RunTimeManager
        • 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 

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

https://developer.rchain.coop 

Date