The XRP Ledger activated the fixCleanup3_3_0 amendment on Sept. 11 at 11:29 UTC in validated ledger 106,911,489, according to XRPSCAN. The package includes maintenance fixes for Checks, automated market makers (AMMs), pseudo-accounts, permissioned trading, Single Asset Vaults and the Lending Protocol. It also changes error handling: CheckCash and CheckCancel now reject an all-zero CheckID during preflight with temMALFORMED, while a narrow divide-by-zero condition involving AMMWithdraw returns tecAMM_FAILED instead of tefEXCEPTION. The code was included in xrpld 3.3.0, released Aug. 6, but activation moved the changes from supported software into mandatory ledger rules. XRPL’s amendment process can block servers that do not recognize an active amendment, preventing them from validating ledgers, processing or submitting transactions, or participating in consensus. XRPSCAN recorded 31 of 35 validations supporting the amendment against a threshold of 28 at 01:45 UTC on Sept. 12, after its two-week majority period. Separate amendments for LendingProtocol, SingleAssetVault, BatchV1_1, ConfidentialTransfer, DynamicMPT, PermissionDelegationV1_1 and Sponsor remained disabled on Sept. 12, although Ripple’s public server supported them. Service providers using maintained wallets or exchanges generally handle the compatibility work, while businesses operating their own XRP Ledger infrastructure must keep servers current.