The Ledger
XRP Ledger Patch Targets Lending Bugs Before Launch
An XRP Ledger amendment with 29 validator votes is on course to fix lending and vault code around Oct. 23. The lending and vault features remain inactive, with 19 and 21 votes, respectively, as of CoinDesk’s Oct. 19 report.

“The protocol offers straightforward on-chain uncollateralized fixed-term loans, utilizing pooled funds with pre-set terms for interest-accruing loans.”
Vytautas Vito Tumas and Aanchal Malhotra, XLS-66
The XRP Ledger’s proposed lending feature is still waiting for validator approval, but a separate patch addressing defects in its code is nearing activation. CoinDesk reported on Oct. 19 that the fixCleanup3_4_0 amendment had 29 votes, the stated threshold for a network of 35 trusted validators, and was expected to take effect around 09:34 UTC on Oct. 23 if support held.
The patch repairs parts of the lending and vault code before the features can be used on the main network. It also includes fixes beyond lending, among them a correction to a token permission that could let an account authorized to burn tokens create them in certain circumstances.
Two weeks of support stand between votes and activation
XRP Ledger rule changes require more than 80% support from trusted validators for two consecutive weeks. Reaching 29 votes puts fixCleanup3_4_0 at the threshold, but does not complete that waiting period; a drop below the required support interrupts the process. CoinDesk reported the amendment was on course for activation on Oct. 23, with no extra votes above the minimum.
The lending feature itself has a separate approval path. CoinDesk’s Oct. 19 count put the LendingProtocol amendment at 19 votes and the SingleAssetVault amendment at 21, both below the 29-vote threshold. Neither had begun its two-week countdown, so the patch’s projected activation would not, on its own, make lending available.
The patch changes how loan lateness is recorded
Under the proposed design, depositors put XRP or another supported asset into a vault, and a loan broker issues fixed-term loans from the pooled funds. The ledger records loans and repayments, while the broker handles borrower credit assessment offchain. The protocol also allows brokers to deposit optional first-loss capital that can absorb part of a default loss.
The amendment tightens the rules for marking a loan impaired. The XLS-66 specification says a loan can be impaired only after the ledger’s close time has passed its next payment due date; equality with the due date does not count as late. Impairing or restoring a loan will no longer rewrite that due date, preventing those management actions from shifting the payment schedule.
Permission fixes extend beyond lending
The xrpld 3.4.0 release notes also describe rounding and precision changes for vault deposits, withdrawals and clawbacks, along with revised handling of freezes, authorizations and loan defaults. A separate fix rejects PaymentBurn transactions that cross a zero balance. XRPL documentation warns that before fixCleanup3_4_0 activates, a delegated PaymentBurn permission can sometimes allow the delegate to mint fungible tokens under certain conditions.
The split between the patch vote and the feature votes matters: the code can be corrected while the network still declines to enable the lending system. As of CoinDesk’s Oct. 19 count, the cleanup amendment had the required 29 votes, but LendingProtocol was 10 short and SingleAssetVault was eight short. The amendment vote, not the patch alone, determines when borrowers and depositors can use the system on the XRP Ledger.
Sources
- Original source CoinDesk coindesk.com
Other pages read
- XRPL Foundation / GitHub github.com
- XRP Ledger Standards xls.xrpl.org
- XRP Ledger documentation xrpl.org
- XRPL Dashboard xrpldashboard.com