Community Update 75


  • Sprint and Release
    • Planning in progress for sprint 31
    • Sprint 30 started May 27. Priorities are:
      • Consensus team
        • Bug fixes in genesis ceremony and network joining
        • Building foundation for bonding and unbonding in Rholang
        • Development work for providing randomness to the validation protocol
        • Provide property based testing for the estimator
      • Node team
        • Resolve challenges connecting to a busy network with fairness property
        • Metrics improvements to support investigating consensus bugs
        • UX improvements and optimizations
      • Rholang team
        • Completion of work to bridge cost accounting with the wallet and proof of stake contract
        • Start work on multisig wallet
        • Bug fixes
      • RSpace team
        • Optimizations for new RSpace
        • Changes to address Rholang bloat in the tuplespace
    • Release
  • Mercury requirements and acceptance criteria
  • Testnet status
    • Testnet-1 is live. Our intention is to keep this functioning so the community can deploy rholang to this public testnet. Please see RChain public testnet information to learn more about public testnet as well as a FAQ.
  • Community testing
    • Thursdays at 14:00 UTC. Kent will be there to address questions related to the consensus protocol.


  • Migration to secp256k1 is in dev and will be a breaking change for users when we release RNode v0.9.7 next week.  RCHAIN-3438 - Getting issue details... STATUS


  • Many bug investigations and fixes this sprint.
  • Metrics support for consensus team.


  • Several PRs merged and in review to support the completion of  RCHAIN-3135 - Getting issue details... STATUS . With the introduction of cost accounting we observe the current approach to block merging is insufficient.
  • Work to make use of this in the RevVault,  RCHAIN-3424 - Getting issue details... STATUS , blocked by discovery of need to move the creation of the deploy to a different tier of the interpreter,  RCHAIN-3506 - Getting issue details... STATUS


  • PR in review to deliver trie merging. Tests indicate this merging strategy gets us very close to the lower bound for any change to the trie. Next steps are to work to optimize the cold store. Reduce bloat - RSpace (current) analysis   RCHAIN-3415 - Getting issue details... STATUS
  • PR in review to provide an alternate way of determining if a deployment is in a block. The current way is to call `show-block <block hash> and search the tuplespace. This is a poor user experience and we want to remove printing all of the tuplespace in a call to show-block. The change will support users using the new deploy ID to confirm it's presence in a block. More details in  RCHAIN-3456 - Getting issue details... STATUS


  • Delivery of a new devnet environment
  • Work continues on the orchestration component of hardening network #1.

Developer website