Version 1.10.0 of rippled, the reference server implementation of the XRP Ledger protocol, is now available. This release introduces six new amendments and cleans up code to improve performance.
As previously announced, the NonFungibleTokensV1_1 amendment became enabled on the XRP Ledger on 2022-10-31 following the fixRemoveNFTokenAutoTrustLine amendment on 2022-10-27. As a result, native Non-Fungible Tokens (per the XLS-20 spec) can now be minted and used on the XRP Ledger Mainnet.
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.
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.
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.
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):
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.
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.
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.
As previously announced, the Checks amendment became enabled on the XRP Ledger on 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.
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:
As previously announced, the fixCheckThreading and fixPayChanRecipientOwnerDir amendments became enabled on 2020-05-01.
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):
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.
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.
As previously announced, the fixMasterKeyAsRegularKey amendment became enabled on the XRP Ledger on 2019-10-02.
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 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.
As previously announced, the MultiSignReserve amendment became enabled on the XRP Ledger on 2019-04-17.
The MultiSignReserve 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-04-17. As long as the MultiSignReserve 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 fixTakerDryOfferRemoval amendment became enabled on the XRP Ledger on 2019-04-02.
As previously announced, the fix1578 amendment became enabled on the XRP Ledger on 2019-03-23.
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.
The DepositPreauth and fix1515 amendments, added in rippled v1.1.0, became enabled on the XRP Ledger today, 2018-10-09.
As previously announced, the fix1571 amendment became enabled on the XRP Ledger on 2018-06-19. Furthermore, the fix1623 amendment is expected to become enabled on 2018-06-20, followed by the fix1543 amendment on 2018-06-21.
Previously introduced in rippled version 1.0.0, the fix1543, fix1571 and fix1623 amendments are now open for voting.
The DepositAuth & fix1513 Amendments became available on the XRP Ledger in ledger sequence number 37,753,345 (2018-04-06T01:44:42Z).
A majority of rippled validators voted to enable the Escrow, PayChan, and fix1368 Amendments, which are scheduled to become enabled on the network on Thursday, 2017-03-30.
As predicted previously, the TickSize amendment became available on the Ripple Consensus Ledger yesterday afternoon (PST) in ledger 27841793 (2017-02-21T23:02:52Z).
This notice is for all validator operators, and may be useful for gateways that intend to use tick sizes.
This notice is for all validator operators, and may be useful for gateways that intend to use tick sizes.
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.
The Flow Amendment became available on the Ripple Consensus Ledger in ledger 24,970,753 (2016-10-21T19:47:22Z).
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.
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.
Originally, the FlowV2 amendment was planned to replace rippled’s payment processing engine with a more robust and efficient implementation. It was previously expected to become active on Wednesday, 2016-08-24.
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.
As predicted previously, TrustSetAuth became available on the Ripple Consensus Ledger this afternoon (PDT) in ledger 22,721,281 (2016-07-19T15:10).
TrustSetAuth Will Soon Be Available
This notice is for all validator operators, and may be relevant to gateways that utilize the Authorized Account feature.
As predicted previously, multi-signing became available on the Ripple Consensus Ledger this afternoon in Pacific time (2016-06-27T11:34:41Z, to be exact).
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: