fixCheckThreading and fixPayChanRecipientOwnerDir Amendments Lost Majority

On 2019-01-11, the fixCheckThreading and fixPayChanRecipientOwnerDir amendments lost the support of several validators, causing those amendments' support to fall below the 80% threshold for approval. (EnableAmendment LostMajority transactions: fixCheckThreading, fixPayChanRecipientOwnerDir.) As a result, these amendments are no longer expected to become enabled on 2020-01-18, and their status depends on more validators to resume voting in favor of the amendments.

XRP Ledger version 1.4.0 Upgrade Advisory

Version 1.4.0 of the XRP Ledger core server (rippled) contains a change that can cause upgrades to take much longer than usual.

Two Fix Amendments are Expected 2020-01-18

On 2020-01-03, the fixCheckThreading and fixPayChanRecipientOwnerDir amendments to the XRP Ledger gained support from a majority of trusted validators. These amendments were introduced in rippled v1.4.0. Currently, they are expected to become enabled on 2020-01-18. Each amendment that continues to have the support of at least 80% of trusted validators continuously will become enabled on the scheduled date.

Introducing XRP Ledger version 1.4.0

XRP Ledger (rippled server) version 1.4.0 has been released. The XRP Ledger version 1.4.0 introduces several new features and overall improvements to the codebase, including the DeletableAccounts Amendment, which allows users to delete XRP Ledger accounts and recover some of their account base reserve in the process.

The 1.4.0 release also includes improved peer slot management, improved CI integration and package building and support for C++17 and Boost 1.71.

Discover Upcoming XRP Ledger Amendments and Features with Devnet!

A new XRP Ledger Devnet is now available for developers to access upcoming features of XRPL on beta build versions of rippled, the C++ reference implementation of the XRP Ledger.

fixMasterKeyAsRegularKey is Now Available

As previously announced, the fixMasterKeyAsRegularKey amendment became enabled on the XRP Ledger on 2019-10-02.

fixMasterKeyAsRegularKey is Expected Tomorrow

The fixMasterKeyAsRegularKey amendment to the XRP Ledger, introduced in rippled v1.3.1, is expected to become enabled shortly past midnight UTC on 2019-10-02. Operators of rippled servers must upgrade to v1.3.1 (or higher) by that time.

The fixMasterKeyAsRegularKey Amendment is Expected 2019-10-02

The fixMasterKeyAsRegularKey amendment to the XRP Ledger, introduced in rippled v1.3.1, has gained support from a majority of trusted validators. Currently, it is expected to become enabled on 2019-10-02. As long as the fixMasterKeyAsRegularKey amendment continues to have the support of at least 80% of trusted validators continuously, it will become enabled on the scheduled date.

XRP Testnet Has Been Reset

Update: The second reset occurred as planned and the Testnet became fully available by approximately 7:56 PM PDT. The amendments that are enabled on the Testnet now match the status of amendments on the production Mainnet.

On 2019-08-27 at approximately 1:00 UTC (6 PM PDT), Ripple reset their XRP Testnet. This means that all accounts, balances, and settings in the Testnet have been deleted and all contents of the Testnet's decentralized exchange have been erased. However, in the process of resetting the XRP Testnet, a procedural issue caused amendments that were previously enabled to be disabled in the fresh ledger chain. Ripple plans to reset the XRP Testnet again today (2019-08-30) at 4 PM PDT. Starting at this time, the Testnet may be unavailable for a maintenance window lasting up to 4 hours.

The production XRP Ledger, or Mainnet, is completely unaffected. This also has no effect on other test networks not run by Ripple.

Introducing XRP Ledger (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.