Community Update 109


  • Release
    • Node version 0.9.19 is the current release - public beta 2 - that resolves all known mergeability issues and has improved web APIs RNode-0.9.19 release plan
    • Testnet is currently running pre-release version of rnode version 0.9.20  Preliminary release notes for 0.9.20 are at .RNode-0.9.21 release plan
    • Release 0.9.20 is currently being prepared with the last PR - this is likely the mainnet release.  

  • Sprint 46 in progress
    • Main Focus: hardening and making the mainnet release
    • Currently testing and merging the last PR likely to be included in mainnet release  RCHAIN-3989 Getting issue details... STATUS  .
    • Merged - Deposit Slashed Funds into coop wallet
    •  Hardening
      • Merged - Recently introduced CloseBlock System deploy seems to cause indeterminate errors
      • Merged - Slashing for invalid blocks sometimes causes issues. We are looking into the proper policy and code changes to resolve this.
    • Casper and block storage
    • dApp developer tools and documentation. 
      • Merged - Exploratory Deployments feature  - Initial version completed, to allow developers to run deployments and rollback. Exploratory deploy allows clients to get data from the blockchain. Exploratory deploy is executed on top of the last finalized block. Future versions will support custom block hash and other nice features.Method can be executed only on read-only RNode.
      • This is API3 described in Obtaining Data   RCHAIN-3979 Getting issue details... STATUS   RCHAIN-3981 Getting issue details... STATUS   and among other things, allows to check for balance without paying REV   RCHAIN-4002 Getting issue details... STATUS
    • Mainnet Readiness
      • Putting in place methods for key management, backup and restore etc.
      • Current plan is to backup the state of the block chain network from a Read Only node.
      • We will be doing a couple of trial runs of mainnet launch.
      • Waiting for 'DFI All Clear' on the exemption.
    • External Validators 
      • Working with one external validator to identify and resolve all issues, so we have a blue print for other validators.
    • Performance improvements
    • Refactoring, Optimizations and bug fixes, hardening - ongoing 

Mercury requirements and acceptance criteria

Blockers to Mainnet

  • TBD

Risks to code completion for Mercury


Developer website