Community Update 103


  • Release
    • Node version 0.9.18 is the current release - public beta - that includes per validator vaults to improve mergeability RNode-0.9.18 release plan
    • Testnet is running rnode version 0.9.18
    • Rnode 0.9.18 includes per validator vaults. This is the public beta release.

  • Sprint 43 in progress
    • Main focus is (a) further improvements to mergeability (b) feature cleanup, testing, hardening, security, bug fixing (c) Network safety and reliability (d) getting ready for exchanges and dApp developers
    • Mergeability
      • Additional mergeability designs being considered, based on potential improvements to Tuple space merging in Rspace RNode feature gaps.
      • Refactor (modularize, decouple) PoS.rho proof of stake contract to minimize mergeability conflicts.
      • Completed design discussion on addressing mergeability. A hierarchical wallet solution is being considered because that is needed for other market requirements also.  We will evaluate implementation difficulty and decide soon.
    • Hardening
      • In Progress - PR to secure access to protocol-private PoS methods   RCHAIN-3888 - Getting issue details... STATUS
      • Continuing to debug the 'insufficient phlo' bringing down the node. Manual debugging is taking a long time due to the many interactions with the state and where the problem occurs vs. where it bubbles up. We will create a tool and better instrumentation to help debug such issues faster. This is necessary to reduce the effort involved in resolving bugs and also to enable us to respond quickly when in production/main net.
      • Currently being analyzed - One bug since Cost accounting release is being addressed. Some times, if there are problems with a particular contract (e.g. insufficient funds, the node is unable to move forward with other deploys). We're investigating the issue and enhancing exception handling to catch and isolate such situations to not impact node  RCHAIN-3923 - Getting issue details... STATUS    RCHAIN-3912 - Getting issue details... STATUS   and  RCHAIN-3937 - Getting issue details... STATUS  .  PR for some of this is getting ready to be issued.
    • Casper and block storage
    • dApp developer tools and documentation. 
    • Performance improvements
    • Refactoring, Optimizations and bug fixes, hardening - ongoing 

Mercury requirements and acceptance criteria

Blockers to testnet-3

  • TBD

Risks to code completion for Mercury

  • Evaluating backlog vs current velocity 

Developer website