A package of XRP Ledger protocol fixes is scheduled to activate around 09: 34 UTC on Oct. 23 after reaching the required support from 29 of the network’s 35 trusted validators. The support must remain above the network’s 80% threshold for two weeks, leaving the amendment vulnerable to a delay if a validator withdraws its vote before activation.
The amendment, called fixCleanup3_4_0, repairs parts of the proposed lending stack before that system has been enabled. All require 29 votes and a two-week approval period, so the cleanup amendment will not itself launch XRP Ledger lending.
The proposed system would let depositors place XRP or another token into a vault while a loan broker issues fixed-term, uncollateralized loans from those pooled assets. The ledger would record the loans and repayments, but borrowers would not provide collateral; credit decisions and default exposure would remain with the broker.
4. 0 release also adds closed-ended vaults with subscription, investment and redemption phases, and changes vault accounting so interest is recognized when payments are received rather than when a loan is originated. The cleanup package includes precision and rounding corrections for vault deposits, withdrawals and clawbacks, along with changes to lending and vault handling of freezes, permissions and defaults.
Beyond lending, the amendment bundle tightens token, escrow, NFT, automated-market-maker and permissioned-exchange rules. It applies an issuer’s incoming-trust-line restriction to offers, strengthens checks on multi-purpose-token balances and transfers, prevents certain signature replays, and fixes an escrow reserve failure at the reserve boundary.
The release follows a separate warning over PaymentBurn permissions. Under certain conditions, an account authorized to destroy issued tokens could create them instead; guidance advised users not to delegate that permission until the relevant fix was active. The issue concerns issued tokens, not the creation of new XRP.
The immediate consequence is a protocol maintenance change rather than a lending launch. Node operators must run software that recognizes the amendment, while the lending and vault features remain dependent on separate validator votes and their own two-week approval periods.