Community Update 73

Owned by Kelly Foster
Last updated: May 22, 2019

General

  • Sprint and Release
    • Sprint 29 ends May 27. Priorities are:
      • Consensus team
        • Bug fixes in genesis ceremony and network joining
        • Continue on implementation of validator incentives and slashing
      • Node team
        • UX improvements
        • Optimizations
      • Rholang team
        • Completion of work to bridge cost accounting with the wallet and proof of stake contract
        • Start work on multisig wallet
        • Bug fixes
      • RSpace team
        • Test and release the renovated RSpace
        • Complete analysis of bloat in the tuplespace
    • Release - Plan to release RNode v0.9.5 today. RNode-0.9.5 release plan
  • Mercury requirements and acceptance criteria
  • Testnet status
    • Testnet-1 is live. Our intention is to keep this functioning so the community can deploy rholang to this public testnet. Please see RChain public testnet information to learn more about public testnet as well as a FAQ.
    • Plan to update and relaunch testnet with RNode v0.9.5 this week.
  • Community testing
    • Thursdays at 14:00 UTC. 

Mainnet launch

  • Estimate is for Mercury to be code complete in Aug. This does not include work that may result from the investigation of Rholang bloat in the tuplespace or bugs.
  • Conversations in progress to clarify how to provide a community-driven, decentralized mainnet launch.
  • Conversations in progress to clarify issues related to the issuance of REV:
    • Clarify expectations for issuing REV based on RHOC related to the need to escrow Pithia-owned RHOC and to RHOC related to the Barcelona scam.
    • How to update communications to RHOC holders related to this process
    • Ensuring tooling in place to support REV holders claiming and transferring tokens after the launch.
  • Conversations in progress to finalize criteria for releasing Mercury from the hardening Mercury acceptance criteria.

Consensus

  • Support for failing test blocking introduction of renovated RSpace to the codebase. Result was refactoring the test to ensure it is deterministic.
  • Work in progress to migrate use of secp256k1 for validator keys and to update related tests.
  • Work in progress to ensure ability to move data from the file containing ETH addresses and RHOC balances provided to a genesis block moves successfully to REV vaults.
  • Postponed discussion Validator Incentives and Casper this week due to team availability. Will pick up again next week.
  • Slashing PR in review.  RCHAIN-2381 - Getting issue details... STATUS
  • Continuing discussions about ways to resolve  RCHAIN-3218 - Getting issue details... STATUS . Work this week included modeling the genesis protocol with TLA+.
  • Reopened  RCHAIN-3244 - Getting issue details... STATUS  when we observed it yesterday on the developer testnet.
  • Kent delivered a talk on CBC Casper to the Wrocław blockchain meetup.

Node

  • Many changes to node coming in the RNode v0.9.5 release. 

    key summary type status
    Refresh

Rholang

  • Work in progress to bridge cost accounting, wallets, and the proof of stake contract.  RCHAIN-3135 - Getting issue details... STATUS
  • Work in progress and draft PR created to implement the on-chain deployer ID.  RCHAIN-3405 - Getting issue details... STATUS
  • Bug investigations in progress. 

    key summary type status
    Refresh

RSpace

  • Renovated RSpace running in the developer testnet with a plan to run it in the public testnet with the upgrade to RNode v0.9.5. This delivers changes to the data, trie, and hot stores. It does not complete the work to optimize the new RSpace.  RCHAIN-3138 - Getting issue details... STATUS  shows what's done and the optimization work planned.
  • RSpace team leading the effort to investigate Rholang bloat in the tuplespace.

SRE

  • Performance test harness now runs on every PR. 
  • In addition to Whiteblock, work in progress to implement additional infrastructure to support the hardening effort. This sprint includes  RCHAIN-3381 - Getting issue details... STATUS
  • On-going support of the various networks

Developer website

Date