Introducing XRP Ledger (rippled) version 1.1.2
Ripple is proud to announce the release of XRP Ledger (
rippled) version 1.1.2.
The XRP Ledger version 1.1.2 release includes a fix for a technical issue in the consensus "preferred ledger by branch" code, which could cause a validator to fail to settle on a single preferred branch of unconfirmed ledger history. While this is not entirely unexpected and the code is designed to handle it, this issue exposed a corner case where the stringent safety guarantees of the consensus algorithm, as outlined in the recent Analysis of the XRP Ledger Consensus Protocol paper, make it difficult for the entire network to efficiently recover from this condition.
If you operate a XRP Ledger validator server, then you should upgrade to XRP Ledger version 1.1.2 as soon as possible.
Impact of Not Upgrading
If you are not running release 1.1.2 or greater, then your validator server can potentially fail to settle on a single preferred ledger branch during consensus and resort to issuing partial validations, until it can resync with the network.
For instructions on updating
rippled on supported platforms, see Installing rippled.
The SHA-256 for the RPM is:
The SHA-256 for the source RPM is:
For other platforms, please compile version 1.1.2 from source.
- Build and Run
rippledon Ubuntu Linux
- Build and run
- See https://github.com/ripple/rippled/tree/master/Builds for instructions by platform.
The first log entry should be the change setting the version:
commit 4f3a76dec00c0c7ea28e78e625c68499debbbbf3 Author: Nik Bougalis <email@example.com> Date: Thu Nov 29 21:49:10 2018 -0800 Set version to 1.1.2
Ripple plans to deploy version 1.1.2 to all XRP Ledger servers under its operational control, including private clusters, on Tuesday, 2018-12-11 at 22:00:00 UTC.
Learn, ask questions, and discuss
Bug Bounties and Responsible Disclosures
On behalf of the XRP Community, Ripple welcomes reviews of the XRP Ledger open source codebase and urge reviewers to responsibly disclose any issues that they may find. For more on Ripple's Bug Bounty program, please visit https://ripple.com/bug-bounty/.
When compiling XRP Ledger from source, you must use a compatible version of the Boost library. As of XRP Ledger version 1.1.2, Boost 1.67.0 is required for all platforms.
1.1.2 Change Log
Improve preferred ledger calculation (#2797)
Properly bypass connection limits for cluster peers (#2795)
We welcome external contributions to the XRP Ledger codebase. Please submit a pull request with your proposed changes on the GitHub project page at https://github.com/ripple/rippled.
On behalf of the XRP Community, Ripple would like to thank those who have contributed to the development of the XRP Ledger (
rippled) open source code, whether they did so by writing code, running the software, reporting issues, discovering bugs or offering suggestions for improvements.
The following is the list of people who made code contributions, large and small, to rippled prior to the release of 1.1.2:
Aishraj Dahal, Alex Chung, Alex Dupre, Andrey Fedorov, Arthur Britto, Bob Way, Brad Chase, Brandon Wilson, Bryce Lynch, Casey Bodley, Christian Ramseier, crazyquark, David Grogan, David Schwartz, Donovan Hide, Edward Hennis, Elliot Lee, Eric Lombrozo, Evan Hubinger, Frank Cash, Howard Hinnant, Iroskam, Jack Bond-Preston, jatchili, Jcar, Jed McCaleb, Jeff Trull, Joe Loser, Johanna Griffin, Josh Juran, Justin Lynn, Keaton Okkonen, Lieefu Way, Luke Cyca, Mark Travis, Markus Teufelberger, Miguel Portilla, Mike Ellery, MJK, Nicholas Dudfield, Nikolaos D. Bougalis, Niraj Pant, Patrick Dehne, Roberto Catini, Rome Reginelli, Scott Determan, Scott Schurr, S. Matthew English, Stefan Thomas, The Gitter Badger, Ties Jan Hefting, Tim Lewkow, Tom Ritchford, Torrie Fischer, Vahe Hovhannisyan, Vinnie Falco, Warren Paul Anderson, Will, wltsmrz, Wolfgang Spraul and Yana Novikova.
As XRP Ledger progresses through the 1.0 series, we look forward to more external contributions and are excited to see the broader XRP Ledger community grow and thrive.