XRP Ledger Lending Explained: Pre-Launch Fixes and Credit Risks
XRPL developers introduced a second lending amendment, LendingProtocolV1_1, to fix uncollateralized lending protocol flaws before validator approval. The update addresses code issues ahead of time to avoid launching a flawed system.
Developers working on the XRP Ledger have introduced a second lending amendment, known as LendingProtocolV1_1. This update aims to fix flaws in the ledger’s uncollateralized lending protocol before validators have approved or utilized it. Previously, the original LendingProtocol amendment and its associated SingleAssetVault received 19 and 21 affirmative votes on October 19, leaving them roughly ten and eight votes short of the 29 required to trigger a two-week activation countdown.
Rather than permitting the initial version to go live and patching it afterward, the new amendment addresses code issues beforehand. Documentation now designates both amendments as prerequisites for the feature, ensuring the network adopts the fixed version from day one. Currently, nothing has been activated, and no release date has been scheduled for the lending protocol.
What Happened: A Lending Protocol Patched Before It Ever Launches
The corrective measure is a code update to rippled, the underlying server software for the XRP Ledger. Because the original lending code failed to reach the approval threshold, integrating the fix prior to deployment avoids launching a flawed system onto the live network and attempting emergency repairs later.
Read More: XRP Ledger Fixes Critical Bug That Could Have Created 18 Trillion XRP, Protecting 100B Supply
Voting metrics tell the story. CryptoPotato noted that on October 19, both LendingProtocol and LendingProtocolV1_1 secured 19 yes votes, accounting for about 54.29% of the 35 trusted validators. SingleAssetVault, representing the shared pool funding the loans, held 21. A separate report by TokenPost on October 17 calculated the target at 29 out of 36 validators, showing the same three amendments trailing.
For an amendment to activate, more than 80% of trusted validators must maintain support for two consecutive weeks. Should support dip to 80% or lower within that window, the countdown resets.
Who Is Behind It: Core Developers and the Validator Set
XRPL core developers draft and release the amendments, while the validator set determines if they are implemented. There is no foundation vote or corporate switch; once the software is shipped, the trusted validators drive the tally.
This lending capability is part of a broader expansion of decentralized finance (DeFi) and credit tools on the XRP Ledger. Transaction batching launched on October 9. Confidential transfer, a privacy feature showcased by Ripple at XRP Seoul in early October, is closest to approval with 22 votes. The lending repair operates on an independent track from these other pending initiatives.
Background: How We Got Here
In its design, loans are fixed-term and uncollateralized. They are funded by depositors via a Single Vault managed by brokers, with borrowers adhering to predefined repayment schedules. Credit evaluations occur off-chain. Official documentation explicitly states that the current version “doesn’t include automated on-chain collateral and liquidation management.”
This pre-launch update reflects a cautious approach following the disclosure and patching of a critical payment engine bug. That flaw could have allowed an attacker to mint counterfeit XRP and had remained dormant for approximately a decade before a researcher identified it.
Another queued amendment, fixCleanup3_4_0, is bundled with rippled version 3.4.0 and tackles a PaymentBurn issue. Before activation, an account with delegated PaymentBurn privileges could occasionally generate trust-line tokens or Multi-Purpose Tokens during transactions meant to burn tokens. It also resolves vault calculation and loan management bugs. XRPL documentation advises against granting PaymentBurn privileges until this fix is fully active.
Why It Matters: Credit Without Collateral on the XRP Ledger
For depositors, the lending feature establishes a credit market using pooled XRP and issued tokens without underlying on-chain collateral. Risk mitigation relies on off-chain underwriting and first-loss capital—a financial buffer established by a broker to cover initial default losses—rather than an automated liquidation engine.
The limitations are visible in the documentation’s sample scenario. Out of a 1,090-token default, only 10.9 tokens are recovered because payouts are restricted to 10% of a minimum cover, which itself represents 10% of the total debt. Consequently, the vault absorbs a loss of 1,079.1 tokens, or roughly 99% of the principal.
Issuers of non-XRP tokens can only claw back first-loss capital down to the required minimum, and they retain the ability to freeze accounts. A frozen borrower cannot make repayments, yet they still owe the debt and ultimately face default. Brokers determine fee structures, though fees are waived if the cover drops beneath the minimum threshold.
Missed payments trigger a grace period, after which brokers can declare a loan in default. If a broker anticipates a missed payment, they can designate the loan as impaired to advance the next due date; a payment made prior to that revised date clears the flag.
Across the broader market, this setup functions as an institutional-grade credit model—combining off-chain underwriting with compliance controls—rather than utilizing the collateral-and-liquidation frameworks typical in DeFi.
Related: XRP Long Position Risks Mount With 97% Exposure Warning: Can the Recovery Hold?
The Numbers: Votes, Thresholds and the October 23 Date
On October 19, LendingProtocol and LendingProtocolV1_1 each garnered 19 yes votes, while SingleAssetVault registered 21. They require ten and eight additional votes, respectively, to meet the 29-vote threshold.
Meanwhile, fixCleanup3_4_0 surpassed 29 affirmative votes on October 9 and is projected to activate at 09:34 UTC on October 23, provided validator support remains above 80% throughout the 14-day voting window.
Risks and Open Questions
The October 23 target is only a projection. It depends entirely on validator backing remaining above 80% for the full two weeks, with any drop to or below 80% resetting the clock. The lending amendments trail further behind and could face indefinite delays since no vote is currently scheduled.
Credit risk is built directly into the system. First-loss capital does not eliminate this risk, and recovery in the provided default scenario accounts for only about 1% of the loan amount. Furthermore, account freezes by issuers can prevent borrowers from repaying, driving them into default. Because the lending protocol has never operated in production, the applied patches remain untested on the live network.
What Happens Next
Attention turns to October 23 at 09:34 UTC, the expected activation time for the cleanup fix during the first flag ledger following its window. Afterward, PaymentBurn delegation becomes possible; until then, documentation recommends withholding permission.
Regarding lending, all three amendments must independently achieve 29 votes and maintain an 80% approval rate for two weeks. Confidential transfer continues its separate trajectory with 22 votes. Any shifts in voting will first appear on the ledger’s amendment tracker and flag ledgers.
?FAQ
01When does fixCleanup3_4_0 activate?
It is projected to go live at 09:34 UTC on October 23, during the first flag ledger after its 14-day window closes, assuming validator support holds above 80% for the entire duration.
02What does fixCleanup3_4_0 actually fix?
It resolves a PaymentBurn vulnerability that could permit a delegated account to issue trust-line tokens or Multi-Purpose Tokens during a token-burning transaction. It also corrects vault calculations and loan management.
03Why publish LendingProtocolV1_1 instead of waiting?
Because the original version has not cleared the 80% approval threshold, developers integrated the fix before launch instead of patching an active system. Both amendments are now necessary requirements for the feature.
04How many votes does lending still need?
As of October 19, LendingProtocol and LendingProtocolV1_1 had 19 votes, and SingleAssetVault had 21, falling ten and eight votes short of the 29 required.
05Does the October 23 fix turn on lending?
No. The cleanup fix does not activate the lending feature. LendingProtocol, LendingProtocolV1_1, and SingleAssetVault must still pass independently.
What is first-loss capital?
This is a reserve posted by a broker to absorb initial default losses before depositor funds are affected. The documentation’s sample scenario caps payouts, resulting in a return of just 10.9 tokens on a 1,090-token default.
06Is there a set date for lending to go live?
No. No lending amendment has attained the 29-vote threshold, and no target date is scheduled for their approval or activation.
This article is for information only and is not financial advice.



