Today, packages for XRP Ledger (rippled) version 1.6.0 were made available for XRP Ledger Mainnet. rippled version 1.6.0 introduces several improvements and new features to the XRP Ledger, including: proposed changes to the XRP Ledger's consensus mechanism to make it even more robust in adverse conditions; hardening of validator server monitoring and notifications; compressed server bandwidth; and numerous bug fixes and optimizations.
We encourage rippled server operators to explore the proposed Amendments highlighted below in rippled version 1.6.0, and upgrade to rippled version 1.6.0 by Wednesday 2020-09-02, which is the earliest date that the Amendments could reach network quorum by the community of validators, in order to ensure service continuity.
XRP Ledger Testnet, which Ripple hosts for developer’s to test the latest stable version, will be upgraded to rippled version 1.6 on Wednesday, 2020/08/19.
Version 1.6.0 includes a proposed change to harden validations, which will require an Amendment, and subsequent 80% quorum approval among the community of validators on Ripple’s recommended UNL for two-consecutive weeks. The change allows servers to detect accidental misconfiguration of validators, as well as potentially Byzantine behavior by malicious validators.
With the proposed hardened validations change, servers can now log a message to notify operators if they detect a single validator issuing validations for multiple, incompatible ledger versions, or validations from multiple servers sharing a key. As part of this update, validators report the version of rippled they are using, as well as the hash of the last ledger they consider to be fully validated, in validation messages.
Beginning with version 1.6.0, server operators can enable support for compressing peer-to-peer messages. This can save bandwidth at a cost of higher CPU usage. This support is disabled by default and should prove useful for servers with a large number of peers.
Version 1.6.0 also comes with a new Health Check Method to perform a simple HTTP request to get a summary of the health of the server: Healthy, Warning or Critical.
Another known "fix" Amendment is being introduced in version 1.6.0, which fixes the 14 day timer to enable an Amendment to start at the correct quorum size due to rounding semantics.
The proposed changes above are some of the key highlights of the version 1.6.0 release. For a more comprehensive list of all the proposed changes in version 1.6.0, please review the version 1.6.0 release notes on xrpl.org or GitHub.
XRP Ledger Devnet, which Ripple hosts for developer’s to test the latest beta version, will be upgraded to the latest beta version next week.
Introducing a Negative UNL
The latest beta version includes a proposed change to the XRP Ledger consensus mechanism with an initial implementation of a Negative UNL, which can improve the liveness of the network during periods of network instability, by allowing servers to track which validators are temporarily offline and to adjust quorum calculations to match.
Ripple expects to run extensive public testing for the Negative UNL functionality on the XRP Ledger Devnet in the coming months. If public testing satisfies all requirements across security, reliability, stability, and performance, then the amendment could be included on an Amendment for quorum review in an upcoming version 2.0 release.
Again, we encourage rippled server operators to review the proposed upgrade to rippled version 1.6.0, learn more about the Amendments above, and upgrade to rippled version 1.6.0 as soon as Wednesday 2020-09-02, which is the earliest date that the amendments could reach network quorum, in order to ensure service continuity.
This release further demonstrates Ripple's continued commitment to developing open protocols, such as the XRP Ledger.