What to know:
- XRP Ledger retires five amendments, while all approved features now remain fully active.
- Clawback remains active, while retirement only removes the obsolete pre-amendment code.
- Six new XRPLd proposals still need validator approval before any activation on Mainnet.
XRP Ledger developers have retired five long-running amendments in XRPLD version 3.3.0. The Aug. 6 release removes obsolete pre-amendment code while preserving every activated feature. XRP holders do not need to update wallets, move funds, or complete any transaction.
The retired amendments are Clawback, fixDisallowIncomingV1, fixInnerObjTemplate, fixNFTokenReserve, and fixUniversalNumber. Their established rules now operate as unconditional parts of the core protocol.
Why XRP Ledger Retires Old Amendments
RippleX software engineer Mayukha Vadari said retirement only clears old code from the software. Developers kept that code after activation because it remained useful for investigating historical transactions.
Also Read: Solana (SOL) Targets $97.50 After Wedge Breakout and Whale Accumulation
XRP Ledger introduces transaction-processing changes through its amendment system. Trusted validators vote on each proposal before it reaches Mainnet.
An amendment needs support from more than 80% of trusted validators for two continuous weeks. Support of 80% or lower resets the approval period. Once enabled, the new rule applies permanently unless another amendment changes it.
xrpld initially retains both the new rules and the earlier transaction logic. This approach helps developers reproduce past ledger behavior during testing or investigations. However, old code increases maintenance work and software complexity.
Official XRP Ledger documentation allows developers to retire an amendment after two years of mainnet activation. Retirement removes the earlier code path and places the approved behavior directly into the protocol. Historically accurate testing can then require the xrpld version that originally processed a transaction.
Which XRP Ledger Features Remain Active After Retirement?
Clawback is by far the most well-known out of the five amendments. It was activated on February 8, 2024. Issuers of eligible tokens are able to reclaim their tokens if the appropriate account setting is activated.
The feature does not support native XRP tokens. The retirement of Clawback means that XRPLD no longer enforces any transaction restrictions from the pre-clawback era. The issuers still have the ability to use the same recovery mechanism.
The other four amendments solved certain technical problems. fixDisallowIncomingV1 restored trust-line authorizations for the users who have disallowed incoming trust lines. fixInnerObjTemplate fixed the inability to read certain properties in the automated market makers’ objects.
fixNFTokenReserve enforced reserve checks when accepting an NFT offer. This rule ensures that the accounts do not conduct a purchase unless they have satisfied reserve requirements. fixUniversalNumber standardized some of the ledger’s floating point numbers.
Six New Proposals Enter XRPLD 3.3.0
The new releases included BatchV1_1, ConfidentialTransfer, DynamicMPT, PermissionDelegationV1_1, Sponsor, and fixCleanup3_3_0. The addition of all these proposals to XRPLD does not turn them on on Mainnet. Each proposal is yet to be approved by the validator.
BatchV1_1 would enable an account to submit eight inner transactions. ConfidentialTransfer would enable private multi-purpose token transfers with compliance measures. DynamicMPT would give issuers the ability to update certain aspects of tokens.
Sponsor would enable third parties to pay fees on behalf of other accounts and transactions. PermissionDelegationV1_1 would give account permissions. fixCleanup3_3_0 combines the fixes for various protocol functions.
XRP Ledger server operators should upgrade to version 3.3.0 to maintain service continuity. Older servers risk becoming amendment blocked if the network activates an unsupported amendment.
Amendment blocked servers cannot process transactions, ledger validation, voting, or joining consensus. All five retirements need no more validator vote because they mark the completion of transitional periods.
Also Read: Ethereum Supply Tightens as $6.13B Shorts Face $1,950 Test
Be the first to comment