Community Update 99

Owned by Rao Bhamidipati
Last updated: Nov 20, 2019
2 min read

General

  • Release
    • Node version 0.9.16 is the current release RNode-0.9.16 release plan
    • Testnet is running rnode version 0.9.16

    • The 0.9.16 includes multisig features, Validator slashing and ejection rules, persistent last finalized block, websockets based events API to access live info about Rnode

    • Cost Accounting feature set was completed and released last Thursday
    • Cost Accounting is running in the Testnet3 branch https://github.com/rchain/rchain/tree/testnet3  We are in the process of merging this branch into the main dev branch and releasing RNode version 0.9.17 soon. It includes Cost Accounting and enhancements to and simplification of RSpace codebase
  • Sprint 42 in progress
    • Main focus is (a) testing, hardening, feature cleanup, security, bug fixing of Testnet 3, Network safety and reliability (b) mergeability (c) getting ready for exchanges and dApp developers
    • Cost accounting is completed and Testnet 3 reached.
    • Mergeability
      • Review comments being addressed before merge  - Created first PR to secure access to protocol-private PoS methods   RCHAIN-3888 - Getting issue details... STATUS
      • Additional mergeability designs being considered.
    • Hardening
      • Planning a combination of Scala property and law testing + generative tests + formal methods to get high coverage in a cost-effective manner.
      • Enhancing the exception handling framework to have better logs to identify quickly as well as 
    • Planning to improve upon and simplify tools and documentation for dApp developers. 
      • Identified a set of tools that exchanges are interested in such as block explorer. Will develop in coordination with the community.
      • Restarting Rcat (digital asset management) work to rebase on current code base. This should help dApp developers as well as help debug/harden the code base by exercising it.
      • Identified initial documentation needs for exchanges + developers, will be working on these.
      • To allow for varied needs of dApp developers, planning to split Testnet 3  into Testnet3-Stable (with less frequent updates) and Testnet3-Latest .
    • Starting to capture some performance data, working with community members. 
    • 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

Date