XRP Ledger Patches New Lending Protocol Before It Goes Live
Key Takeaways
- •Developers have published a follow-up amendment, LendingProtocolV1_1, that corrects the original LendingProtocol amendment while it is still awaiting validator approval, meaning no loans have yet been issued on the protocol.
- •XRP Ledger amendments must earn support from at least 80% of trusted validators over a two-week period before activation, and the pending vote is the next milestone for the lending feature.
- •The lending protocol targets institutional-style credit, offering on-chain fixed-term uncollateralized loans from pooled funds with off-chain borrower vetting and a first-loss capital buffer in place of automated on-chain collateral.
- •The pre-launch fix follows the recent disclosure and repair of a critical payment engine bug that could have enabled counterfeit XRP creation and had remained dormant for roughly a decade.
- •The lending feature is part of a broader expansion of credit and DeFi capabilities on the XRP Ledger that Ripple and others have said the network previously lacked.

The XRP Ledger is repairing its new lending protocol before a single loan has been written on it, adding a follow-up amendment that fixes the original LendingProtocol code while it still sits in the network's validator voting queue.
The lending protocol is a DeFi building block that enables on-chain, fixed-term, uncollateralized loans drawn from pooled funds. It was introduced through an amendment called LendingProtocol, which remains open for validator voting. Rather than waiting for that version to go live and then fixing it, developers have published a follow-up, LendingProtocolV1_1, that corrects issues in the original before it ever takes effect. The documentation now lists both amendments as requirements for the feature, meaning the network would adopt the repaired version from the start.
The approach reflects how changes reach the XRP Ledger. New features and fixes ship as amendments that must earn support from at least 80% of trusted validators over a two-week period before they activate. Because the original lending code has not yet cleared that bar, patching it with a second amendment avoids launching a known-flawed system onto the live network and then scrambling to repair it afterward. That ordering is the exception in decentralized finance, where flaws have more often surfaced — and been exploited — only after protocols are already live.
The protocol itself is built for institutional-style credit rather than the collateral-and-liquidation model common in decentralized finance. It relies on off-chain underwriting to vet borrowers and uses "first-loss capital" — a buffer that a loan broker puts up to absorb the initial hit from defaults — in place of automated on-chain collateral. Issuers retain compliance tools, including the ability to freeze accounts or claw back funds.
The pre-launch caution follows a close call elsewhere in the ledger's code. Developers recently disclosed and fixed a critical bug in the XRP Ledger's payment engine that could have allowed an attacker to mint counterfeit XRP, a flaw that sat dormant for roughly a decade before a researcher flagged it. Repairing the lending code before launch fits a more cautious posture around new functionality.
The lending feature is part of a broader buildout of credit and DeFi capabilities on the XRP Ledger, which has been adding the financial-market plumbing that Ripple and others have long said the network lacked. With both amendments subject to the same 80% validator threshold, the vote is the next milestone to watch before any loan is written on the protocol.