XRP Ledger Activates FixCleanup3_3_0 Amendment, Updating Core Transaction Rules

The XRP Ledger’s latest amendment, fixCleanup3_3_0, went live on Sept. 11 at 11:29 UTC (validated ledger 106,911,489). The update bundles a series of maintenance corrections that affect transaction handling, automated market makers (AMMs), checks, pseudo‑accounts, permissioned trading, single‑asset vaults and the lending protocol.

Key technical changes

• Checks: CheckCash and CheckCancel now reject an all‑zero CheckID during preflight with temMALFORMED.
• AMM withdrawals: A divide‑by‑zero edge case now returns tecAMM_FAILED instead of tefEXCEPTION.
• Freeze handling: Adjusted for transfers involving pseudo‑accounts.
• Safeguards: Tightened around AMMs, permissioned markets and cleanup processes.

Amendment activation process

The code for these fixes has been available since the xrpld 3.3.0 release on Aug. 6. Activation required a two‑week majority vote among validators; 31 of 35 validations supported the amendment, surpassing the 28‑validation threshold on Sept. 12.

Impact on server operators

Once an amendment is active, servers that do not support it become amendment‑blocked. Blocked servers cannot validate ledgers, submit or process transactions, or participate in consensus. Operators are therefore urged to upgrade to the latest xrpld release to maintain full compatibility.

Future protocol features

Although fixCleanup3_3_0 is active, other amendments bundled in the 3.3.0 codebase—such as LendingProtocol, SingleAssetVault, BatchV1_1, ConfidentialTransfer, DynamicMPT, PermissionDelegationV1_1 and Sponsor—remain disabled. Validators have not yet activated these features, so they are not part of the live rule set.

What this means for users

For end‑users, the immediate effect depends on the wallets and exchanges they use. Service providers must ensure their infrastructure runs the updated software, while users of self‑hosted XRPL nodes need to upgrade promptly to avoid disruption.