XRP Ledger activates fixCleanup3_3_0; lending protocol inactive

The XRP Ledger activated the fixCleanup3_3_0 amendment on Sept. 11 at 11:29 UTC in validated ledger 106,911,489. The change makes a set of transaction, automated market maker (AMM) and compatibility fixes mandatory for servers that validate ledgers and process transactions.

The update includes maintenance corrections for Check operations, AMMs, pseudo-accounts, permissioned trading, Single Asset Vaults and parts of the proposed Lending Protocol. Several fixes address rare failure conditions: CheckCash and CheckCancel now fail preflight when given an all-zero CheckID with temMALFORMED, and an edge-case divide-by-zero in AMMWithdraw returns tecAMM_FAILED instead of causing a tefEXCEPTION. Other changes tighten freeze handling for transfers involving pseudo-accounts and add safeguards around permissioned markets and cleanup processes.

The code for these fixes has been in xrpld 3.3.0 since its Aug. 6 release. The ledger’s amendment process allows software to be distributed before validators adopt it as a consensus rule. After an amendment secures the required majority for its prescribed period and activates, the new rules become mandatory. Validator data showed 31 of 35 validators supporting fixCleanup3_3_0 against a threshold of 28 at 01:45 UTC on Sept. 12, following the amendment’s two-week majority period.

A server that is amendment blocked cannot determine whether ledgers are valid, submit or process transactions, or participate in consensus. Operators that run exchanges, custodial services, payment systems or other XRPL infrastructure must run xrpld builds that recognize active amendments to restore full node functionality. XRPL documentation recommends running the latest appropriate xrpld release to remain compatible.

Several features included in xrpld 3.3.0 remain disabled pending separate approvals. Amendments for LendingProtocol, SingleAssetVault, BatchV1_1, ConfidentialTransfer, DynamicMPT, PermissionDelegationV1_1 and Sponsor were not active at the time fixCleanup3_3_0 enabled. Nodes can report software-level support for those amendments, which means the software recognizes them even though validators have not added them to the network rule set.

For users who rely on maintained wallets and exchanges, service providers handle compatibility updates. For firms operating self-hosted XRPL nodes, the activation requires verifying node software is up to date and running builds that include support for active amendments. The amendment mechanism allows developers to release and test protocol changes in software before the validator community votes to make them mandatory.