The XRP Ledger (XRPL) activates fixCleanup3_4_0 at approximately 09:34 UTC on Oct. 23, fixing a security flaw that secured supermajority validator backing on Oct. 9.
Approximately 26 to 29 validators out of 32 to 35 currently support the change, according to XRPSCAN amendment tracking—exceeding the required 80 percent threshold. If support drops to 80 percent or lower before Oct. 23, the two-week countdown resets and the amendment must maintain backing for another uninterrupted two weeks.
The upgrade focuses on fixing existing software behavior rather than introducing new products. The rippled version 3.4.0 package corrects lending infrastructure, automated market makers (AMMs), token handling, escrow transactions and account permissions.
The critical fix targets PermissionDelegationV1_1, a feature activated Oct. 8 that allows an account owner to grant limited authority for specific actions to another account without surrendering main keys. A permission called Paymentburn is designed to allow an authorized account to destroy tokens. A software flaw in PermissionDelegationV1_1 could, under specific conditions, allow tokens to be created instead—the inverse of the intended behavior.
XRPL documentation advises operators against granting the Paymentburn permission until fixCleanup3_4_0 activates. The update also tightens rules for declaring loans overdue and corrects how vaults calculate withdrawals. It prevents certain AMM transactions from destroying liquidity tokens without returning corresponding assets.
These changes are largely invisible to ordinary XRP holders, but node operators require compatible software to maintain network consensus after activation.
Despite the cleanup including several lending-related fixes, the XRPL's proposed native lending system remains unapproved. This Lending Protocol would enable users to pool assets and fund fixed-term loans directly on-chain. Borrowers would not necessarily provide collateral, with loan brokers arranging terms and assessing creditworthiness off-chain.
The complete lending system requires three separate amendments to activate. As of Oct. 15-17, two amendments had approximately 17 to 19 supporting validators, or roughly 53 percent. The Singleassetvault amendment had around 19 to 21 supporters. All three amendments remain short of the necessary supermajority, leaving their activation dates undetermined.
For traders and node operators: the Oct. 23 date marks essential security and stability fixes. Native lending remains a separate, pending development—core protocol integrity takes precedence as the network evolves.
