UPDATE 7-12-2017: This announcement now contains corrected SHA-256 values for the
RPM and source
rippled team has released
rippled version 0.70.1, which corrects a technical flaw in the newly refactored consensus code that could, in rare cases, cause a node to get stuck in consensus due to stale votes from a peer. Ripple requires upgrading to
rippled version 0.70.1 immediately.
There are no new features in the 0.70.1 release.
If you operate a
rippled server, then you should upgrade to 0.70.1 immediately.
Impact of Not Upgrading
- If you operate a
rippledvalidator server, but do not upgrade to
rippledversion 0.70.1, then your
rippledvalidator server could experience increased loss of synchronization with the network.
For instructions on updating
rippled on supported platforms, see Updating
rippled on supported platforms.
The SHA-256 for the
The SHA-256 for the source
For other platforms, please compile version 0.70.1 from source.
The first log entry should be the change setting the version:
commit 3bfd9de6779994e5bbbba864791429e2f7360947 Author: Nik Bougalis <email@example.com> Date: Wed Jun 28 07:15:07 2017 -0700 Set version to 0.70.1
(Note: a previous version of this announcement incorrectly reported the version-setting commit ID as 5044f2354cbf39c52f6ff910fdff368b9801ef67.)
0.70.1 Change Log
- Allow compiling against OpenSSL 1.1.0, which allows compiling under the latest version of Fedora. (#2151)
- Log invariant check messages at “fatal” level (#2154)
- Fix the consensus code to update all disputed transactions after a node changes a position (#2156)
The Ripple technical operations team deployed
rippled version 0.70.1 to all
rippled servers under its operational control, including private clusters, on Sunday, 2017-07-09.
Learn, ask questions, and discuss
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.