Three Amendments Expected on 2021-04-08

Two bug-fixing amendments to the XRP Ledger protocol and one amendment that improves robustness of consensus, all introduced in rippled v1.6.0, have gained support from a majority of trusted validators: fix1781, fixAmendmentMajorityCalc, and HardenedValidations. Currently, they are expected to become enabled on 2021-04-08. Any of these amendments that continue to have the continuous support of at least 80% of trusted validators will become enabled on the scheduled date.

Server operators should be sure to upgrade rippled before this date.

Introducing XRP Ledger version 1.7.0

Ripple has released version 1.7.0 of rippled, the reference server implementation of the XRP Ledger protocol. This release significantly improves memory usage, introduces a protocol amendment to allow out-of-order transaction execution with Tickets, and brings several other features and improvements.

Introducing XRP Ledger version 1.6.0

XRP Ledger (rippled server) version 1.6.0 has been released. This release introduces several new features including changes to the XRP Ledger's consensus mechanism to make it even more robust in adverse conditions, as well as numerous bug fixes and optimizations. (This post has been updated with recommendations for upgrading.)

Moving Devnet to a Validator List

Ripple plans to upgrade the XRP Ledger Devnet to use a recommended validator list like the ones used on the Testnet and Mainnet. Ripple also plans to reset the Devnet history and state at this time. If you operate a server on the XRP Ledger Devnet, or run software on the Devnet, you must upgrade your configuration to remain synced.

RequireFullyCanonicalSig, fixQualityUpperBound, and FlowCross are Now Available

As previously announced, the RequireFullyCanonicalSig amendment became enabled on the XRP Ledger on 2020-07-03. Additionally, the fixQualityUpperBound amendment became enabled on 2020-07-09 and the FlowCross amendment became enabled on 2020-08-04.

With these amendments enabled, version 1.5.0 is the minimum server version to remain synced to the XRP Ledger.

The RequireFullyCanonicalSig Amendment is Expected 2020-07-03

The RequireFullyCanonicalSig amendment to the XRP Ledger, introduced in rippled v1.5.0, has gained support from a majority of trusted validators. Currently, it is expected to become enabled on 2020-07-03 (UTC). As long as the RequireFullyCanonicalSig amendment continues to have the support of at least 80% of trusted validators continuously, it will become enabled on the scheduled date.

The Checks Amendment is Now Enabled

As previously announced, the Checks amendment became enabled on the XRP Ledger on 2020-06-18.

The Checks Amendment is Expected 2020-06-18

The Checks amendment to the XRP Ledger, introduced all the way back in rippled v0.90.0, has gained support from a majority of trusted validators. Currently, it is expected to become enabled on 2020-06-18. As long as the Checks amendment continues to have the support of at least 80% of trusted validators continuously, it will become enabled on the scheduled date.

DeletableAccounts is Now Enabled

As previously announced, the DeletableAccounts amendment became enabled on the XRP Ledger on 2020-05-08.

Get Ready for Deletable Accounts

The XRP Ledger is currently expected to enable the deletion of on-ledger accounts for the first time, through the DeletableAccounts Amendment, on 2020-05-08 (UTC). This amendment comes with changes to some fairly fundamental details of the XRP Ledger protocol. If you use the XRP Ledger for your business, this is a good time to do a last check to make sure you're ready.

Read on for some tips on:

• Deletable accounts in general
• Handling changes to account creation
• Dealing with accounts that could be deleted
• Getting XRP back by deleting your extra accounts