Label: Amendments

Posted 2022-10-13 to

ExpandedSignerList Enabled and NFTs Approaching

The ExpandedSignerList amendment became enabled on the XRP Ledger on 2022-10-13, allowing multi-signing lists to support up to 32 entries (up from 8) and additional metadata on each signer. Additionally, the fixRemoveNFTokenAutoTrustLine amendment has gained support from over 80% of trusted validators, which puts XLS-20 Non-Fungible Token (NFT) support on track for becoming enabled on the XRP Ledger Mainnet in the near future. All XRP Ledger users should upgrade to version 1.9.4 of the core XRP Ledger server for service continuity.

Posted 2022-09-20 to

Introducing XRP Ledger version 1.9.4

Version 1.9.4 of rippled, the reference server implementation of the XRP Ledger protocol, is now available. This release introduces a new amendment to the XRP Ledger protocol, fixRemoveNFTokenAutoTrustLine, to mitigate a potential denial-of-service attack against non-fungible token (NFT) issuers.

Posted 2022-09-01 to

Get Ready for NFTs

The NonFungibleTokensV1_1 amendment to the XRP Ledger, introduced in version 1.9.2 of the rippled server implementation, has gained support from a majority of trusted validators. Currently, it is expected to become enabled on 2022-09-13. As long as the NonFungibleTokensV1_1 amendment continues to have the support of over 80% of trusted validators continuously, it will become enabled on the scheduled date, adding native support for non-fungible tokens (NFTs) to the ledger, following the XLS-20 specification.

Posted 2021-11-10 to

Five Amendments Expected Soon

Several amendments to the XRP Ledger protocol are expected to become enabled on the XRP Ledger Mainnet soon. Three of these amendments fix bugs in the XRP Ledger protocol, one (NegativeUNL) improves the ability of the network to make forward progress during periods of instability, and the last one (TicketBatch) adds the ability to prepare and send transactions in a more flexible order. The details are as follows (all dates are in UTC):

  • fixSTAmountCanonicalize (min version: 1.7.0) expected 2021-11-11.
  • FlowSortStrands (min version: 1.7.0) expected 2021-11-11.
  • fixRmSmallIncreasedQOffers (min version: v1.7.2) expected 2021-11-18.
  • TicketBatch (min version: v1.7.2) expected 2021-11-18.
  • NegativeUNL (min version: v1.7.3) expected 2021-11-21.

Each amendment will become enabled if it maintains support from at least 80% of trusted validators until its expected time. Operators of rippled servers must upgrade to the minimum version or higher by the time these amendments become enabled.

Posted 2021-03-30 to

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.

Posted 2020-05-06 to

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
Posted 2020-01-13 to

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.

Posted 2019-03-19 to

The fix1578 and fixTakerDryOfferRemoval Amendments are Expected

The fix1578 amendment to the XRP Ledger, introduced in rippled v1.2.0, has gained support from a majority of trusted validators. Currently, it is expected to become enabled on 2019-03-23.

The fixTakerDryOfferRemoval amendment to the XRP Ledger has also gained support from a majority of trusted validators. Currently, it is expected to become enabled on 2019-04-02.

As long as the amendments continue to have the support of at least 80% of trusted validators continuously, they will become enabled on the expected dates.

Posted 2017-02-10 to

TickSize Amendment Open for Voting

Previously introduced in rippled version 0.50.0, the TickSize amendment to the Ripple Consensus Ledger is now open for voting. The amendment changes the way offers are ranked in the RCL's order books, so that currency issuers can configure how many significant digits are taken into account when ranking offers by exchange rate.

Posted 2016-10-17 to

The Flow Amendment Will Soon Be Available

A majority of rippled validators voted to enable the Flow Amendment, which is scheduled to become active on the protocol on Thursday, 2016-10-20. This amendment replaces the payment processing engine with a more robust and efficient rewrite called the Flow engine. The new payments engine adds no new features, but improves efficiency and robustness in payment handling.

Posted 2016-10-07 to

The Flow Amendment is Open for Voting

Originally introduced in rippled version 0.32.1, but later vetoed after a flaw was discovered in the code while testing, the new Flow Amendment is now open for voting. This amendment replaces the payment processing engine with a more robust and efficient rewrite called the Flow engine. The new payments engine adds no new features, but improves efficiency and robustness in payment handling.

Posted 2016-08-10 to

The FlowV2 Amendment is Open for Voting

The FlowV2 Amendment is now open for voting. This amendment replaces the payment processing engine with a more robust and efficient rewrite called the FlowV2 engine. The new version of the payment processing engine is intended to follow the same rules as the old engine. However, the new engine occasionally produces different results due to floating point rounding.

Posted 2016-06-21 to

Multi-Signing Will Soon Be Available

The multi-signing amendment is currently supported by the majority of voting validators on Ripple, and is scheduled to become active on the protocol on Monday, 2016-06-27. For more information, please see the multi-signing documentation in the Ripple Developer Portal: