XRP Ledger Retires Five Amendments to Streamline Protocol Code

The retirement process targets code that has been active on the Mainnet for at least two years. By removing these obsolete branches, developers reduce complexity within the codebase. According to RippleX software engineer Mayukha Vadari, the change is purely structural. The ledger continues to function exactly as it did before the update, as the amendments themselves—including the high-profile Clawback feature—remain permanent, unconditional parts of the protocol.

Alongside Clawback, the update retires fixDisallowIncomingV1, fixInnerObjTemplate, fixNFTokenReserve, and fixUniversalNumber. These components previously required the network to maintain dual logic: the modern rules and the pre-amendment versions used for historical debugging. While removing this "legacy baggage" streamlines the software, server operators are urged to upgrade to version 3.3.0 promptly. Failing to stay current with the latest software can lead to nodes becoming amendment-blocked, a state that prevents them from participating in network consensus.

While the five retirements are finalized, version 3.3.0 also introduces six new proposals, including ConfidentialTransfer and DynamicMPT. Unlike the retired amendments, these new features remain in a conditional state. They require sustained support from at least 80% of trusted validators over a two-week period before they can be activated on the Mainnet. For the average user, the distinction is clear: the retired code is a maintenance milestone, while the new proposals represent the next potential phase of protocol evolution.