Page Comparison

General

• Sprint and Release
  • 2-week sprint ends April 1. Priorities: public testnet monitoring, long-running testing, improvements support consensus performance
  • RNode v0.9 to release week of March 25. RNode-0.9.1 release plan.
• Mercury requirements and acceptance criteria
  
  • Please see documentation at https://github.com/rchain/rchain/blob/dev/docs/features.md. 
• Testnet status
  • Please see RChain public testnet information to learn about the rollout plan for launching the public testnet as well as a FAQ
  • At this time there are no known blockers to the delivery of Testnet-1. 
• Community testing
  
  • Thursdays at 14:00 UTC. Please see RChain community RNode testing for complete details.

Consensus

• Testing a fix to

  Jira Legacy
  server System JIRA serverId 50130123-f232-3df4-bccb-c16e7d83cd3e key RCHAIN-1031

   with 

  Jira Legacy
  server System JIRA serverId 50130123-f232-3df4-bccb-c16e7d83cd3e key RCHAIN-3150

  . This is a blocking bug for newly bonded validators.
• Support for wallet and node teams related to signing of deployments and rejection of unsigned deployments.

Cost accounting

• Last week's issue

  Jira Legacy
  server System JIRA serverId 50130123-f232-3df4-bccb-c16e7d83cd3e key RCHAIN-3077

   resolved and we are now complete for the implementation of common cost accounting in each tier of the interpreter, 

  Jira Legacy
  server System JIRA serverId 50130123-f232-3df4-bccb-c16e7d83cd3e key RCHAIN-2883

  .
• Work in progress to complete the union of cost accounting and wallet to demonstrate deployments having a cost,

  Jira Legacy
  server System JIRA serverId 50130123-f232-3df4-bccb-c16e7d83cd3e key RCHAIN-3135

  , deduction of the cost from the deployer, and payment of the cost. Plan to demo this Wed., April 1. 

Node

• Added new configuration options for node operators related to --max-message-size` and --packet-chunk-size. We recommend using the default values. However, can forsee a need some node operators might have related to message size and streaming packets. Please see 

  Jira Legacy
  server System JIRA serverId 50130123-f232-3df4-bccb-c16e7d83cd3e key RCHAIN-3117

   for more details.
• Work in progress for 

  Jira Legacy
  server System JIRA serverId 50130123-f232-3df4-bccb-c16e7d83cd3e key RCHAIN-3152

   to address concern for the possibility of a node, like bootstrap, rejecting new peers due to the current implementation of Kademlia.

RSpace

• Last week we discovered a critical issue to the success of mainnet related to how RSpace supports consensus and the ability to support long chains. The short-term fix is in and not a blocker to testnet-1. The long-term fix, and the one required for mainnet, is in progress and estimated to take 3 weeks. See 

  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-3138

   for more details.

Test infrastructure and performance testing

• Testnet support: Testing with testnet-1 infrastructure and monitoring in progress.
• Performance testing: Work in progress to automate the performance test harness on PR merge.
• Long-running tests: Work in progress to automate the the run of long-running tests, tests requiring 5+ hours to run, 

  Jira Legacy
  server System JIRA serverId 50130123-f232-3df4-bccb-c16e7d83cd3e key RCHAIN-3100

   and 

  Jira Legacy
  server System JIRA serverId 50130123-f232-3df4-bccb-c16e7d83cd3e key RCHAIN-3150

  .

Wallet

• Work in progress to ensure support for signing and for validating the signatures of deployments.
• Demo

Developer website

• https://developer.rchain.coop