rippled Version 1.3.1

Ripple has released version 1.3.1 of rippled, the reference implementation of the core XRP Ledger protocol. To learn more about how to build and run a rippled server, see Manage the Rippled Server.

This release supersedes version 1.3.0. Version 1.3.1 addresses deadlock conditions reported by some users late in the release cycle for 1.3.0.

Installing or Updating rippled

The installation instructions on supported platforms have changed for rippled 1.3.x.

• For all new installs, see Install rippled.
• On Red Hat Enterprise Linux 7 or CentOS 7, if you have automatic updates enabled, the updates should work successfully. For more information or for manual update instructions, see the Migration Instructions for RHEL 7 / CentOS.
• On Ubuntu Linux (16.04, 18.04, or newer), native (APT) packages are now available. If you already have rippled installed using the previous method (installing RPMs with Alien), see Migration Instructions for Ubuntu Linux for steps to migrate to the new, native packages. Additionally, it is now possible to enable automatic updates on Ubuntu.
• Debian 9 Stretch is now a supported operating system. See Installation on Ubuntu or Debian Linux for instructions.
• For other platforms, please compile from source.
  • Step-by-step instructions for compiling rippled are also available for macOS and Ubuntu.

Summary of Changes

The rippled 1.3.1 release introduces several new features and overall improvements to the codebase, including the fixMasterKeyAsRegularKey amendment, code to adjust the timing of the consensus process and support for decentralized validator domain verification. The release also includes miscellaneous improvements including in the transaction censorship detection code, transaction validation code, manifest parsing code, config file parsing code, log file rotation code, and in the build, continuous integration, testing and package building pipelines.

New and Updated Features

• The fixMasterKeyAsRegularKey amendment which, if enabled, will correct a technical flaw that allowed setting an account's regular key to the account's master key.
• Code that allows validators to adjust the timing of the consensus process in near-real-time to account for connection delays.
• Support for decentralized validator domain verification by adding support for a "domain" field in manifests.

Bug Fixes

• Improve ledger trie ancestry tracking to reduce unnecessary error messages.
• More efficient detection of dry paths in the payment engine. Although not a transaction-breaking change, this should reduces spurious error messages in the log files.
• Improved handling of deadlock conditions.