Community Update 100


  • Release
    • Node version 0.9.17 is the current release that includes cost accounting RNode-0.9.17 release plan
    • Testnet is running rnode version 0.9.17
    • Rnode 0.9.17 includes Cost Accounting and enhancements to and simplification of RSpace codebase. It is the base release for Testnet 3 before we go into public beta

  • Sprint 42 in progress
    • Main focus is (a) mergeability (b) feature cleanup, testing, hardening, security, bug fixing of Testnet 3, Network safety and reliability (c) getting ready for exchanges and dApp developers
    • Mergeability
    • Hardening
      • 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 actively 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
      • Planning a combination of Scala property and law testing + generative tests + formal methods to get high coverage in a cost-effective manner.
      • Addressing critical issues with Mercury_Stability label.
    • Planning to improve upon and simplify tools and documentation for dApp developers. 
      • Addressing dApp developer needs for HTTP interface 
      • 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.
      • Working on providing a two node network for dApp developers' exclusive use.
    • Performance improvements
      • Using flamegraphs to identify bottlnecks and adding improvements as possible. An example is improvement of ReplayRspace matching Seems to have provided 14x improvement
      • Investigating the concurrency settings on the monix library and JVM to make sure they're set optimally
      • Starting to capture more performance data, working with community members. 
    • Refactoring, Optimizations and bug fixes, hardening - ongoing 
    • Happy Thanksgiving
      • My thanks to the development team for all their hardwork and getting us closer to Public beta and main net
      • Thanks to everyone in the community,especially those that are helping with tools and dApp development and providing feedback on what we need to improve for developers.
      • You would have noticed that we are integrating more of the community members into the development team, such that the team is now a Core + Tools team, rather than just a Core Dev team. 

Mercury requirements and acceptance criteria

Blockers to testnet-3

  • TBD

Risks to code completion for Mercury

  • Evaluating backlog vs current velocity 

Developer website