Page Comparison

General

• Release
  • Node version 0.9.15 is being released later today RNode-0.9.15 release plan

  • The 0.9.15 includes the new type safe API (instead of Either), Fixes for Long Proposal Times Issue, Offchain-data API (events API) improvements and other incremental progress in features discussed below.

• Sprint 38 in progress
  
  • Main focus on (a) long proposal times (b) cost accounting (d) Casper tests independent of network layer (e) Type Safe API instead of Either (f) completing peek merge functionality (g) API to replace ListenForData@name (off-chain observability of deploy results) (h) Planning and implementation for Network safety, reliability and hardening
  • Ongoing implementation of hardening.
  • Launch readiness planning is ongoing
  • Cost accounting - implementation ongoing. 
  • Progress in long propose times: multiple streams of implementation and investigation:
    • Completed- Synchrony constraints implemented as a tunable parameter.
    • Completed- A second part of the solution is being implemented to promote efficient use of the network by sending block hashes instead of whole blocks to all the nodes. Details in

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

       
    • Completed-Additional Network layer improvements being implemented - Casper waiting on full outgoing message queue, eliminate delays and retries in block streaming, optimal sizes for incoming and outgoing message queues 

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

    • Completed - Implemented improvements in Estimator performance - Investigation of Estimator performance as a source of erratic behaviour
    • Exploring fairness constraints as an additional mechanism to address long proposal times.
    • We continue to explore various test parameters and more complex contracts, to both test the stability of this issue and make it manifest sooner if it exists.
  • Completed In Progress - In RSpace, an API is implemented for DAG discovery and block discovery, to enable an alternative to ListenForData@Name (Off-chain observability of deploy results). Relevant tickets are 

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

     

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

     and  

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

     and 

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

     
  • Ongoing - The changes are now being tested in development as well as in use cases like Rcat. Necessary changes to Rcat being made to use the new API, so it can be tested.
  • Ongoing - In Casper, ongoing work on pre-requisites for non-game-able source of randomness for the validator to use, to pick a new validator from the 'bonding draw set' 

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

  • In Review - Implementation of mult-sig vault features is ongoing as detailed in 

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

     

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

     

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

     and 

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

    .  Next step is to write tests for this.
  • Completed - New API has been implemented with type safety, responding to community requests.   https://github.com/rchain/rchain/pull/2729 and   

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

     
  • Refactoring, Optimizations and bug fixes - ongoing 
  • Exploring technical options and planning for Rhoc to Rev conversion, wallets and third party readiness - ongoing. Providing them documentation and support in node setup and testing, 
  • Getting ready to focus on documentation.

  • ---

    ---

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.
• Community testing
  
  • Sept 19 at 14:00 UTC. Please see RChain community RNode testing for more information.

Blockers to testnet-3

• TBD

Risks to code completion for Mercury

• Evaluating backlog vs current velocity 

Developer website

• https://developer.rchain.coop