XRP Ledger Retires Five Long-Active Protocol Amendments

The XRP Ledger has retired five long-active protocol amendments, but users can rest assured that their functionality remains unchanged. The amendments in question - Clawback, fixDisallowIncomingV1, fixInnerObjTemplate, fixNFTokenReserve, and fixUniversalNumber - have been part of the network for years, and their post-activation behavior is now permanent within the core protocol.

The retirement of these amendments means that the older code paths are being removed from the xrpld software, but this does not affect users. According to RippleX software engineer Mayukha Vadari, 'retiring an amendment means removing the pre-amendment code that still exists in the codebase for amendments that got activated a while ago.' In other words, the network is simply cleaning up old legacy code.

The XRP Ledger uses a governance mechanism where protocol changes can be introduced without immediately forcing every new rule onto Mainnet. Validators vote on amendments, and a proposal must maintain support from more than 80% of trusted validators for two continuous weeks before it becomes active. Once enabled, the new behavior applies permanently unless another amendment later changes it.

While five old amendments are leaving conditional status, version 3.3.0 adds six new proposals to xrpld. These new proposals - BatchV1_1, ConfidentialTransfer, DynamicMPT, PermissionDelegationV1_1, Sponsor, and fixCleanup3_3_0 - must still clear XRPL's validator process independently before they become active on Mainnet.

For server operators, it is recommended to upgrade to version 3.3.0 as soon as possible to maintain service continuity. This will ensure that the software contains the code for amendments that may later become active and prevent nodes from becoming amendment blocked.