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.)
XRP Ledger (
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.
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 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 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.
As previously announced, the DeletableAccounts amendment became enabled on the XRP Ledger on 2020-05-08.
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
The DeletableAccounts amendment is still expected for 2020-05-08.
Three amendments to the XRP Ledger protocol currently hold support of a majority of trusted validators, and are expected to become enabled on the following dates (in UTC):
Like most new releases, version 1.5.0 of the XRP Ledger core server (
rippled) contains new amendments which are not understood by earlier versions of the software.
XRP Ledger (
rippled server) version 1.5.0 has been released. The
rippled 1.5.0 release introduces several improvements and new features, including support for gRPC API, API versioning, UNL propagation via the peer network, new RPC methods
submit method, improved
tx method, improved CLI parsing, improved protocol-level handshaking protocol, improved package building and various other minor bug fixes and improvements.
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.
Version 1.4.0 of the XRP Ledger core server (
rippled) contains a change that can cause upgrades to take much longer than usual.
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.