Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
Following
XRP XRPLD 3.3.0 released, five amendments retired and made permanent
XRPLD 3.3.0 (a reference server implementation of the XRP ledger protocol) was released last week, marking an important milestone for the network. The update introduces a series of bug fixes and improvements, while retiring five long-standing amendments.
The five amendments are retired and the new version of
makes the Clawback, fixDisallowIncomingV1, fixInnerObjTemplate, fixNFTokenReserve, and fixUniversal Number amendments permanent. With their retirement, these functions have become a complete and unchangeable part of the XRP ledger protocol.
Mayukha Vadari, a software engineer at RippleX, provided insight into the process, explaining that the amendment's retirement and removal functions are different. Instead, this involves removing pre-amendment code from the codebase that remains some time after the amendment took effect. Removing pre-amendment code is a necessary part of maintaining the code base and will not affect the user experience or existing XRPL functionality.
Vadari said that for example, the Clawback amendment has taken effect since February 2024 and will only be retired after a considerable period of time to ensure that it will not interfere with users or developers.
Why the XRP ledger amendment will be retired
The amendment retirement process is not immediate. Vadari pointed out that development teams typically wait about two years before removing old pre-fix code in case they need to debug past transactions or resolve historical technical issues. The goal is to keep the code base clean while retaining enough data for troubleshooting. This approach supports continuous development while minimizing risk to network participants.
Small Dictionary: RippleX is the software and developer platform division of Ripple, focusing on promoting the development of the XRP ledger ecosystem and supporting developers to build applications on XRPL.
How amendments introduced and adopted
XRP ledger using the amendment system to manage and implement protocol changes. Amendments are introduced as new features or updates to the way transactions are processed. Each proposed amendment must go through an online consensus process that requires verifiers to review and vote on it. If any amendment receives at least 80% validator support within two weeks, it will become an integral part of the XRPL agreement from then on. These measures ensure that updates receive widespread support and that the network remains stable and secure.
Amendment status and activation date
Clawback: Retired (permanent)--February 2024
fixDisallowIncomingV1: Retired (permanent)--Not specified
fixInnerObjTemplate: Retired (permanent)--Not specified
fixNFTokenReserve: Retired (permanent)-Not specified
fixUniversalNumber: Retired (permanent)-Not specified
Repealing an amendment that has already been adopted can only be achieved by proposing and accepting a new amendment, which must also go through a full ratification process. This ensures the continuity and integrity of XRP ledger transactions.
Fully functional protocol updates on XRPL must pass consensus, and once integrated, disabling them requires a separate amendment and approval from the Verifier Network.
