Community Update 115


  • 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.  

  • 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 
      • Looking into performance improvement possibilities in the API calls in 0.9.24, getting ready to push 0.9.24 to mainnet read only nodes, possibly with caching enabled on the read only nodes. 0.9.24 impacts only observer nodes. Team is focused on completing these investigations and enabling on the mainnet in the next few days.
      • Ongoing - Configuration changes to make node deployments easier and cleaner - nutzipper testing this and resolving the issues discovered in testing. 
      • Ongoing - Improvements to last finalized state initial draft PR issued  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.  
      • Completed - Creating a node.js API for exchanges that need it. We anticipate PR being available for review in the next couple of days. 
      • Ongoing - Augmenting and rationalizing monitoring of mainnet and other nets, including distributing monitoring over multiple cloud providers, for resilience 
      • Tomislav competed the first TeachOut yesterday (Tuesday 10 AM Eastern) in zoom room demonstrate node building in different environments / scenarios.  Video will be available in the #education channel shortly
    • 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