The XRP Ledger activated the fixCleanup3_3_0 amendment on September 11 at 11:29 UTC in validated ledger 106,911,489. The update bundles maintenance corrections for transaction handling, automated market makers (AMMs), Checks, pseudo-accounts, permissioned trading, and Single Asset Vaults.
The amendment introduces several technical fixes targeting edge cases in transaction processing. CheckCash and CheckCancel operations now reject all-zero CheckID values during preflight validation, while a divide-by-zero condition in AMMWithdraw transactions returns a failure code instead of an exception. The update also adjusts freeze handling for transfers involving pseudo-accounts and tightens safeguards around AMM and permissioned market operations.
Code supporting these changes has been available since xrpld version 3.3.0 released on August 6. The amendment's activation this week marks the transition from optional software support to mandatory consensus rules that all servers must recognize to remain fully compatible with the ledger.
Operational Implications for Node Operators
Under the XRP Ledger's amendment system, servers that do not support the active amendment can become amendment-blocked. An amendment-blocked server cannot determine whether ledgers are valid, submit or process transactions, or participate in consensus. The project recommends operators update to the latest appropriate xrpld release to restore full functionality.
The amendment secured 31 of 35 validator votes, exceeding the 28-vote threshold required for activation. This creates immediate operational requirements for exchanges, custodians, payment companies, and other businesses running their own XRP Ledger infrastructure.
Other Features Remain Disabled
The activation of fixCleanup3_3_0 does not enable all features included in version 3.3.0. Separate amendments covering the Lending Protocol, Single Asset Vault, Batch operations, Confidential Transfers, Dynamic Multi-Purpose Transactions, Permission Delegation, and Sponsor features remain disabled pending their own validator approval. Ripple's public server reported support for these amendments, indicating the software recognizes them even though validators have not yet activated them as network rules.
For users relying on maintained wallets or exchanges, compatibility updates are handled by service providers. Operators running independent XRP Ledger servers face the more immediate requirement of maintaining current software as validator-approved amendments transition from available code into active network rules.
