Note that RNode-0.9.13 is NOT BACKWARD COMPATIBLE with previous releases of RNode due to refactoring of the dagstore as described in https://github.com/rchain/rchain/pull/2696 and RCHAIN-3800-Revamp DAG storage to minimize duplicate code and use scodec for data structure serializationDONE
The 0.9.13 release includes many bug fixes, optimizations, refactoring changes in addition to a lot of metrics and instrumentation implemented to enable faster analysis and resolution of problems like the Long Proposal Times issue we encountered.
Sprint 37 in progress
Main focus on (a) long proposal times - implementation of synchrony constraints solution (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 (off-chain observability of deploy results) (h) Mechanisms for Network safety, reliability and hardening
Ongoing implementation of hardening.
Launch readiness planning is ongoing
Cost accounting - implementation ongoing.
Progress in investigating long propose times: Synchrony constraints using number of parents based on stake weight is implemented, merged and tested. We see some improvement in proposal times. Results are being further analyzed. A second part of the solution is being implemented to promote efficient use of the network by sending block hashes instead of whole blocks to all the nodes. Details in
RCHAIN-3819Getting issue details...STATUS
In RSpace, an API implemented for DAG discovery and block discovery, to enable an alternative to ListenForData@Name (Off-chain observability of deploy results). Relevant tickets are
RCHAIN-3760Getting issue details...STATUSRCHAIN-3661Getting issue details...STATUS and
RCHAIN-3762Getting issue details...STATUS and
RCHAIN-3812Getting issue details...STATUS The changes are now being tested in development as well as in use cases like Rcat. Necessary changes to Rcat being made to use the new API, so it can be tested.
In Casper, ongoing 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-3195Getting issue details...STATUS
Design and Implementation of mult-sig vault features is ongoing (should be ready for review soon) as detailed in
RCHAIN-3392Getting issue details...STATUSRCHAIN-3196Getting issue details...STATUSRCHAIN-3223Getting issue details...STATUS and
RCHAIN-3773Getting issue details...STATUS.
Increased testing by Dev team - ongoing
New API has been implemented with type safety, responding to community requests. Tomislav and others from the community are engaged in review and comments of this PR https://github.com/rchain/rchain/pull/2729. Please join in the conversation in the #development channel in Pub-Rchain. We want as wide a feedback as possible. Will be merged only after we get good feedback from the community.
RCHAIN-3839Getting issue details...STATUS