Page Comparison

General

• 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
    • Plan to release RNode v0.9.7 week of June 10. RNode-0.9.7 release plan
• Mercury requirements and acceptance criteria
  
  • Please see the documentation at https://github.com/rchain/rchain/blob/dev/docs/features.md. 
• 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.

Consensus

• Migration to secp256k1 is in dev and will be a breaking change for users when we release RNode v0.9.7 next week. 

  Jira Legacy
  server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 50130123-f232-3df4-bccb-c16e7d83cd3e key RCHAIN-3438

Node

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

Rholang

• Several PRs merged and in review to support the completion of 

  Jira Legacy
  server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 50130123-f232-3df4-bccb-c16e7d83cd3e key RCHAIN-3135

  . Much of the work here has been to refactor and improve aspects of the project to support the use With the introduction of cost accounting across the RevVault, Rholang interpreter, and proof-of-stake contractwe observe the current approach to block merging is insufficient.
• Work to make use of this in the RevVault, 

  Jira Legacy
  server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 50130123-f232-3df4-bccb-c16e7d83cd3e key RCHAIN-3424

  , blocked by discovery of need to move the creation of the deploy to a different tier of the interpreter, 

  Jira Legacy
  server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 50130123-f232-3df4-bccb-c16e7d83cd3e key RCHAIN-3506

RSpace

• 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  

  Jira Legacy
  server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 50130123-f232-3df4-bccb-c16e7d83cd3e key RCHAIN-3415

• 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 

  Jira Legacy
  server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 50130123-f232-3df4-bccb-c16e7d83cd3e key RCHAIN-3456

SRE

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

Developer website

• https://developer.rchain.coop