Community Update 116

Owned by Rao Bhamidipati
Last updated: Apr 22, 2020
2 min read

General

  • Release
    • Node version 0.9.24 is the current release - second update post-mainnet - Housekeeping changes and meeting requirements of exchanges for reporting state and transaction history RNode-0.9.24 release plan
    • Testnet is currently running rnode version 0.9.24  

    • Mainnet is running RNode-0.9.23. 

    • RNode 0.9.24 changes are only in the read only node. We're in the process of setting up an 'exchanges only' read only node for now, running 0.9.24
  • Sprint 50 in progress
    • Main Focus: hardening the mainnet, improve performance, make usability improvements including configuration, API improvements for functionality needed by exchanges.
    • Current Work In Progress 
      • Still working on performance improvements in 'transaction history' functionality of 0.9.24.  Looking into other options to enable multiple simultaneous client calls. Caching with cryptographic assurance is the next planned improvement. Other improvements are linked to the main code improvements we're doing. So exposing 0.9.24 on the mainnet to exchanges only is a temporary solution - perhaps one per exchange or load balanced. Encouraging exchanges to run their own read only nodes.
      • Close to complete - Configuration changes to make node deployments easier and cleaner - Reviews complete, nutzipper resolving the comments. 
      • Ongoing - Improvements to last finalized state initial draft PR issued https://github.com/rchain/rchain/pull/2913  but quite a bit of work involved still. The PR and the branch are structured so that multiple people can collaborate/ work on different parts of the feature at the same time. The scope of this work enables (a) faster catchup by new nodes - you can start from the last finalized state - this is a differentiator for RChain (b) offloading older data and differentiated storage and retrieval strategies for the same (c) allows for a leaner / less bloated node. Tomislav continuing to work and test this.  Rest of the team being roped in to this to accelerate delivery. Having to pick between refactoring and work-arounds in various parts. This change touches most parts of the codebase. Trying to get a more modular and future-beneficial approach.
      • Completed - Creating a node.js API for exchanges that need it. We anticipate PR being available for review in the next couple of days - Will fixing one bug that was found. 
      • Ongoing - Augmenting and rationalizing monitoring of mainnet and other nets, including distributing monitoring over multiple cloud providers, for resilience 
      • Starting a focus on documentation inventory, requirements, gaps, and a way to address them
      • Tuesday TeachOuts by Tomislav (Tuesday 10 AM Eastern) in Jimscarver's zoom room https://zoom.us/j/6853551826 
    • Current Backlog (partial)
      • Improve merging in system deploys
      • Improve Triemerge
      • Improve multi-parent Casper enablement
      • Implement sharding capabilities
      • Improve logging to be able to learn what API calls are being used, so they can be related to resource use and performance etc
      • Rholang 1.1 to improve syntax and user experience / learning curve
  • Tech-Governance meetings on Thursdays 10 AM Eastern, 7 Am Pacific 

Mercury requirements and acceptance criteria

Blockers to Mainnet

  • TBD

Risks to code completion for Mercury

  •  

Developer website

Date