Update Summary


Last week the dev team created a demo restarting a node and using the bookstore to catch up easily, which could be run side-by-side with a network visualization. The co-op created RSong equity vehicle documentation in anticipation of member/board input.  New channels were created: an announcement channel and member audio chat channel. Members can now submit their questions in the new member channel for Friday’s closed-door Q&A.

This week, Greg announced the completion of the RSong equity vehicle, with the exception of tax commitments. He noted that the dev team has reached a milestone of stability for reasonable fine-grain profiling. Getting traffic from the market to the platform were discussed. Concerns were raised regarding the collective involvement of the community and representation in management decisions.


Timeline


  • Technical update: public test net monitoring, long-running testing, improvements support consensus performance
  • Documentation for the RSong vehicle completed
  • Management system and co-op involvement in decision

Announcements



Content in Brief


Technical update: public test net monitoring, long-running testing, improvements support consensus performance


General

  • Sprint and Release
    • Two-week sprint ends April 1. Priorities: public test net monitoring, long-running testing, improvements support consensus performance
    • RNode v0.9 to release week of March 25. RNode-0.9.1 release plan.
  • Mercury requirements and acceptance criteria

  • Testnet status
    • A public test net is not yet available. There is a plan to launch one the week of March 25. Please see RChain public testnet information to learn about the rollout plan for launching the public testnet (as well as an FAQ)
    • At this time there are no known blockers to the delivery of Testnet-1
  • Community testing

Consensus

  • The dev team ran a test net over the weekend. They are investigating options for reducing the time required to add blocks. This work includes adding metric spans to Casper to support analysis. Investigating the possibility of improving how we record history as a way to reduce the time required to add a block. This would be a significant change in terms of development and is critical to achieving Mercury performance goals. Work in progress to analyze this plan and determine next steps.
  • Improved performance by limiting the check depth of deploy history duplication, RCHAIN-3070 – Limit deploy history duplication check depth DONE
  • Demonstrated successful attempts at validator bonding in 20190314 RNode community testing. We have observed some bugs related to bonding after the fact. Investigation in progress for RCHAIN-3106 – ERROR c.r.shared. UncaughtExceptionLogger$ – Uncaught Exception: justification Block is missing justification pointers to equivocating Validator even though justificationBlock isn’t a part of equivocation DetectedBlockHashes for this equivocation record; RCHAIN-1031 – Invalid block: JustificationRegression

Cost accounting

  • Ran into an issue investigating the underlying cause of running out of phlo, and why it doesn’t stop the evaluation of other execution branches: RChain-3077. The current implementation does not provide synchronization, which means that concurrent branches of execution would not always see the latest amount of available phlogistons and continue executing if the account was depleted. Testing if replacing Ref with MVar will be the resolution.

Node

  • Very pleased with RNode stability in this weekend’s testing.
  • Removed round trip from the transport layer and rely on heartbeat to improve node performance. RCHAIN-3110 – Remove roundTrip from TransportLayer DONE  
  • Many improvements to RNode over the past week. Some in RNode-0.8.5 release plan and others in RNode-0.9.1 release plan.
  • RCHAIN-3087 – Uncaught Exception : Atomic move is not supported
  • Very pleased with RNode stability in this weekend’s testing.
  • Removed round trip from the transport layer and rely on heartbeat to improve node performance. RCHAIN-3110 – Remove roundTrip from TransportLayer DONE  
  • Many improvements to RNode over the past week. Some in RNode-0.8.5 release plan and others in RNode-0.9.1 release plan.
  • RCHAIN-3087 – Uncaught Exception : Atomic move is not supported
  • RCHAIN-3074 – Restoring a node causes LatestMessagesLogIsMalformed error
  • RCHAIN-3028 – RNode creates rnode.data.dir_IS_UNDEFINED in working directory
  • RCHAIN-3017 – Error while streaming packet, error: ProtocolException(io.grpc.StatusRuntimeException: DEADLINE_EXCEEDED: deadline exceeded after 599999891038ns)
  • RCHAIN-3011 – Support loading Casper state from storage during a restart of RNode

RSpace

  • Tuning work in progress related to better support for Casper and the introduction of F in IStore. PR in today related to RSpace reset.

Test infrastructure and performance testing

  • Testnet support: Finishing off work to monitor the public test net.
  • Performance testing: Focused on performance related to consensus and time to add blocks this week.

Wallet

  • Wallet contracts are now in dev
  • Work in progress to ensure support for signing and validating the signatures of deployments

Questions and comments

Greg believes that the development team has reached a milestone of stability for reasonable fine-grain profiling. He is excited by the profiling information the dev team has been working on. Wallet demo scheduled for next week.

Documentation for the RSong vehicle complete

Documentation for using RSong as an equity vehicle has been completed. The co-op is ready to commit decisions that have to be made with respect to particular tax implications to trigger the formation of this equity vehicle. More information will be given in Friday’s Q&A. Greg recommends that community members look into the podcast about proof-of-stake economics to better understand why RSong was chosen for this purpose.

Questions and comments

Greg discusses data acquisition and privacy market approach to generating traffic on the platform. He feels the market is less sensitive to a privacy approach of data and information. Few end users care about sovereign identity. Nick Meyne suggests adopting an ecosystem approach with diverse solutions rather than just privacy to generate traffic. According to Greg, the ecosystem approach has been in view; Reflective Ventures and Pithia were funded for these reasons.

Management system and coop involvement in decision

Rich Jensen took the lead in a discussion centering on the degree of which the collective intelligence of the community could be employed to facilitate co-op’s management decisions. Greg welcomes community input.  Members are encouraged to approach board members, officers, or any empowered committee members directly.