Community Update 88

Owned by Rao Bhamidipati
Last updated: Sept 04, 2019
2 min read

General

  • Release
  • Sprint
    • Sprint 37 in progress 
      • Main focus on (a) long proposal times analysis and resolution (b) cost accounting specification and implementation (d) Specifying Casper tests independent of network layer (e) Increased testing including validator slashing (f) completing peek merge functionality (g) API to replace ListenForData@name (h) Mechanisms for Network safety, reliability and hardening
      • Analysis and planning for hardening in progress. Identified tickets being worked.
      • First iteration of Launch planning and analysis in progress. 
      • Genesis vault creation ceremony 'required signatures issue' resolved and tested.  
      • Cost accounting - progress in cost replayability (continuing work). Increased team working on ticketed items in system deploy and cost accounting, to reduce completion risk. 
      • Progress in investigating long propose times: It seems that once a validator falls behind, they fall further behind, leading to rabbits and tortoises. Have a meeting scheduled to discuss potential solutions. Each test has been taking a long time because of cumulative behavior taking a while to show up. Correspondingly, the analysis.
      • Progress in replacing the old registry with Rholang based registry. Near-term solution for Implementing replayability support in Peek is being added now, should be available in the next relase. Long-term solution to be discussed and designed later.  Details at Replay issues
      • RNode version 0.9.13 should be released during this sprint.
      • In RSpace, an API is implemented for DAG discovery and block discovery, to enable an alternative to ListenForData@Name, Two tickets are currently in review. Relevant tickets are  RCHAIN-3661 - Getting issue details... STATUS  and   RCHAIN-3762 - Getting issue details... STATUS  and  RCHAIN-3812 - Getting issue details... STATUS
      • In Casper, starting work on pre-requisites for non-game-able source of randomness for the validator to use, to pick a new validator from the 'bonding draw set'  RCHAIN-3195 - Getting issue details... STATUS
      • Increased testing by Dev team
        • Specification under review for tests needed to harden the network against the parameters identified as enablers for the 'incentivized testnet planning' tests - ongoing.  Details at /wiki/spaces/OP/pages/752058391
        • Specifying Casper tests independent of network layer - ongoing
        • We have an extra developer testing environment to enable parallel runs of long-running tests (where some problems/bugs show up only after building a large number of blocks) in addition to current integration tests - ongoing
      • Increased testing by community
        • Analysis of previous community test has identified an extra 50 contracts (total of approx. 350 contracts) that can be used for testing.
        • This testing has revealed a JVM heap / out of memory error with certain types of contracts. Starting analysis and discussion to address what needs to be done apriori, to prevent big / bad contracts causing slowdown or disabling of part of the network.
      • Refactoring, Optimizations and bug fixes - ongoing e.g. refactoring validate.scala to use EitherT  RCHAIN-3616 - Getting issue details... STATUS
      • Exploring technical options and planning for Rhoc to Rev conversion, wallets and third party readiness - ongoing

Mercury requirements and acceptance criteria

Blockers to testnet-2

  • See complete view in  RCHAIN-3168 - Getting issue details... STATUS

Risks to code completion for Mercury

  • Evaluating backlog vs current velocity 

Developer website

Date