XRP Ledger Lending: Bug Fix and Approval Status
XRP Ledger’s lending code is getting a bug fix, but lending and vault features remain unapproved. Learn what validator votes mean and what happens next.

XRP Ledger's Lending Code Is Getting Fixed Before Lending Is Approved
A code fix can be ready to activate even while the feature it supports is still waiting on approval. That's the awkward situation around XRP Ledger's proposed lending system: a bundle of changes is on track to go live, but the lending and vault amendments it depends on haven't cleared the validator vote threshold needed to activate.
As of the latest reported vote count, the fix package had 29 validator votes and was nine days into a two-week approval window. If things hold, it's expected to take effect at about 09:34 UTC on October 23, 2026. The lending amendment had 19 votes, and the vault amendment had 21 - neither had started its own countdown.
That gap matters because this isn't just "a software release." It's a change to how the ledger can record loans and vault assets, while leaving credit decisions and borrower approvals to a broker. Here's what the patch changes, how XRPL's approval process works, and what the vote numbers do - and don't - tell you about whether institutions will actually use it.
The fix is ahead of the lending feature
The package, fixCleanup3_4_0, is a set of XRP Ledger changes that had secured 29 validator votes as of Monday, according to the XRPL Dashboard. It was also nine days into the required two-week approval period, with an expected activation time of around 09:34 UTC on Friday, October 23.
Of course, the timing isn't guaranteed. The package has the minimum number of votes required - no extra cushion. If one of the supporting validators withdraws its vote, the support level would no longer be continuous, and the two-week clock would have to restart once the threshold is restored. So "on course" here really means "meeting the bar right now," not "locked in."
This package isn't only about the proposed lending code. The xrpld 3.4.0 release notes say it also closes a token-permission loophole: under certain conditions, an account that had permission to burn - or destroy - tokens on an issuer's behalf could create tokens instead. Fixing that kind of mismatch between intended permission and what the account can actually do is a ledger integrity issue on its own.
The package also updates how vault amounts are rounded and how the lending code determines whether a loan is late or in default. Those may sound like "implementation details," but they affect how loan balances and repayment status are represented. If a system is meant to track loans, disputes about rounding or default labeling can turn into real problems for lenders and brokers - not just a code-quality concern.
One distinction is worth repeating: the fix package and the lending feature are separate approvals. The fixes can activate without making the lending system available. In other words, the existence of the fix doesn't mean lenders can start issuing loans on XRPL.
For the original reporting and the vote counts, see CoinDesk's report on the XRPL lending code fix. The broader lesson is straightforward: in an amendments-based blockchain, code readiness and network approval are different milestones.
How XRPL's amendment approval process works
XRP Ledger changes that alter network rules require validator support. Validators are independent servers that help determine which transactions are valid and that back proposed amendments. The reported threshold is more than 80% of the 35 validators the network trusts by default - meaning at least 29 votes in practice.
But getting to 29 votes isn't enough on its own. Support has to stay above the threshold for two consecutive weeks. That waiting period gives validators a chance to review the change and adjust their support before activation. It also means a vote total is only a snapshot - both the number and its continuity matter.
Why a two-week countdown matters
If you want a simple mental model, it's two gates:
- Threshold gate: The amendment must receive at least 29 validator votes.
- Time gate: It has to hold that level of support for two straight weeks.
An amendment that reaches the threshold today doesn't activate today. It starts the countdown. If support drops below the minimum during that period, the process gets interrupted and the countdown restarts after the threshold is reached again.
So yes, it slows things down. But it also makes activation depend on coordinated, sustained support - something developers have to treat as part of the schedule, not an afterthought.
Reading the three vote counts
Those vote totals are why the fix and the lending proposals shouldn't be bundled together in your head:
fixCleanup3_4_0: 29 votes. It had reached the minimum and was already into its two-week countdown.- Lending amendment: 19 votes. It was 10 votes short and hadn't started its countdown.
- Vault amendment: 21 votes. It was 8 votes short and hadn't started its countdown.
The lending feature depends on more than one amendment. The vaults that are meant to hold lenders' funds are governed by a separate change. So approval of the lending amendment alone wouldn't finish the activation path. Both amendments have to clear the threshold and then hold support through their own two-week windows.
That's why the "earliest possible activation" timing points to early November even if both amendments magically jumped to 29 votes immediately. That's a best-case scenario, not a forecast. If an amendment takes longer to hit threshold - or loses support during its countdown - the timeline shifts.
For operators and users, the practical habit is to track each amendment separately: current votes, whether the two-week clock has started, and whether the support is steady. A headline like "XRPL lending is approved" would hide the differences that actually control the outcome.
How the proposed lending model would work
The proposed system is built around a lender, a vault, and a loan broker. A lender deposits XRP (or another token) into a vault. Then a broker lends from that pool to a borrower for a fixed term. The ledger records the loan and tracks repayments, while the broker decides offchain whether to approve the borrower.
That offchain decision is where the model's risk really sits. The loans are described as uncollateralized, meaning borrowers don't post collateral that can be automatically seized if they fail to repay. Instead, the broker's assessment of the borrower - and the broker's ability to manage the relationship and recover funds - directly shapes the exposure for lenders.
What the ledger handles - and what it does not
The design splits lending into two buckets: what ledger rules can represent, and what stays outside the chain. Onchain, the system can record loan terms and repayment activity. The broker, meanwhile, makes the lending decision.
In practical terms, the software can track what happens, but it can't independently prove that a borrower is creditworthy.
That distinction matters more for institutional users than for casual observers. A bank or payment company looking at the system would need to think beyond transaction speed and whether balances can be tracked. They'd also need to understand the broker's underwriting process, how the legal relationships among participants work, what happens in defaults, and what recourse lenders have if borrowers don't pay.
A code patch can help with representation - like how late payments and defaults get labeled - but it can't create guaranteed repayment. Rounding changes might improve how amounts are handled, but they don't remove the underlying economics of lending without collateral.
Why the proposal is being discussed for payment flows
Ripple has pitched the idea to payment companies that may need working liquidity while cross-border settlement is clearing. The business problem is familiar: funds can be in transit or temporarily unavailable, while a company still has payments and operating costs to cover.
In principle, a lending market could help bridge that gap. But whether it's useful depends on whether the system can offer terms, liquidity, compliance processes, and risk controls that fit the institution trying to use it. The existence of a proposed lending feature doesn't prove those requirements have been met - and the current vote status doesn't mean loans are active on XRPL yet.
There's a difference between a product concept and a working service. This proposal describes a possible structure. Approval, implementation, market participation, and real-world use are separate steps, each with its own constraints.
What the vote gap means for adoption
Right now, the story is about governance and release sequencing - not a live institutional lending market. The bug-fix package appears closer to activation because it already has the necessary votes and is progressing through its countdown. The two amendments needed for lending are still below threshold, and neither had started its two-week clock at the time of the reported figures.
None of that proves validators oppose the lending model. A vote count by itself doesn't tell you why a validator supported or didn't support an amendment. It does show that the required network consensus for activation hasn't been reached yet. If you're evaluating the proposal, that's the reliable signal - anything more speculative about the "why" would go beyond what the vote totals can actually support.
It helps to separate three different kinds of progress:
- Code readiness: Are the relevant changes implemented and being prepared for activation?
- Network approval: Have the amendments cleared the validator threshold and the required period?
- Operational adoption: Are brokers, lenders, and borrowers ready to use the system under workable commercial and risk terms?
Moving one piece forward doesn't guarantee the others will follow. The fix package can improve the code while governance approval is still missing. And even governance approval wouldn't automatically mean institutions are ready to adopt, or that the credit and liquidity problems the model aims to solve are actually handled well in practice.
What to monitor next
If you're following XRPL's lending proposal, focus on a few observable signals rather than treating one expected activation date as the whole picture:
- Whether
fixCleanup3_4_0keeps its 29 votes through the end of its countdown. - Whether the lending and vault amendments reach the 29-vote threshold.
- When each amendment begins its two-week approval period.
- Whether the final implementation and release notes clarify the changes to rounding, late status, and defaults.
- Whether brokers and institutional participants share concrete information about underwriting, liquidity, and how defaults are handled.
And separately, the token-permission fix deserves attention beyond the lending discussion. An authorization intended to allow burning, but that - under certain conditions - could allow token creation, is a meaningful control problem. Its inclusion in the same package is a reminder that amendment bundles shouldn't be judged only by whichever feature gets the most attention.
For another angle, read more about Ripple's institutional lending proposal. The core question isn't whether XRPL can represent a loan. It's whether governance, on-chain behavior, and the offchain credit model line up well enough for real users to rely on.
Conclusion
This XRP Ledger update highlights something that's easy to miss in crypto coverage: a fix can be close to activation while the feature it supports is still unapproved. fixCleanup3_4_0 had reached the 29-vote threshold and was moving through its countdown, while the lending and vault amendments were still short of the votes needed to start theirs.
For now, treat October 23 as conditional and the lending system as a proposal - not an active service. Track the amendments separately, then evaluate the broker and credit model on their own. If you're looking at XRPL for institutional lending, start with the approval status, the default and repayment mechanics, and who ends up carrying the risk when an uncollateralized borrower doesn't pay.