Mentioned in This Article
1. XRP Ledger lending protocol picks up support
Ripple's proposed XRP Ledger lending protocol, built for banks and payment companies, has gained three validator votes in roughly three weeks, reaching 22 of the 35 validators on the network's default list as of Wednesday, November 11, 2026. It still needs 29 votes, held for two consecutive weeks, before it can activate.
The gain moves the system meaningfully closer to launch but leaves it seven votes away from the level that would start the two-week countdown. A companion change that creates the deposit pools the lending system draws from sits slightly ahead, with 23 votes, and it too must clear the same bar.
Who changed their position is not publicly known. The dashboard that tracks amendment voting publishes only totals, so observers can see that support grew but cannot identify which validators moved.
The vote count matters because the XRP Ledger has no central operator that can simply switch on a new product. Even a feature developed and promoted by Ripple, the company most closely associated with the network, has to win over independent validators before it becomes part of the ledger's rules.
2. What is an XRP Ledger amendment?
An amendment is the mechanism the XRP Ledger uses to change its own rules. New features and fixes are packaged as amendments, and each one activates only after more than 80% of the 35 validators on the network's default list, meaning at least 29 of them, signal support continuously for two straight weeks.
Validators are the servers that agree on the state of the ledger and on which transactions are included. The default list is the set of validators that most servers on the network trust out of the box, which is why its members effectively decide whether a proposed change goes live.
The two-week requirement acts as a cooling-off period. If support drops below the 80% threshold at any point during that window, the clock resets. That design is meant to ensure that changes to a live financial network have durable backing rather than a brief spike of approval.
Because amendments are switched on network-wide once they pass, operators and developers building on the ledger closely watch vote counts. A feature that reaches the threshold gives businesses a firm date to plan around, while one that stalls can remain dormant for months.
3. Where the lending and vault votes stand
As of Wednesday, data from an XRPL amendment-tracking dashboard showed 22 yes votes each for LendingProtocol, the main lending amendment, and for LendingProtocolV1_1, its first patch. SingleAssetVault, the amendment that creates the pools lenders deposit into, had 23 votes.
The two pieces are linked. Lending draws its funds from these vaults, so the lending system cannot operate unless both the vault amendment and the lending amendments pass. In practice, the slower of the two determines when lending can begin.
On October 19, an earlier count showed 19 votes for lending and 21 for the vault. A snapshot taken on November 10 showed 22 and 23 respectively, which means the new support arrived by Tuesday. The totals had not moved by Wednesday.
Measured against the 29-vote threshold, SingleAssetVault needs six more yes votes and the lending amendment needs seven. Lending cannot open until two weeks after both have reached that level and held it.
4. How does the XRP Ledger lending protocol work?
The XRP Ledger lending protocol lets depositors place XRP (XRP) or other tokens into a vault, after which a loan broker lends those funds out for a fixed term. Borrowers do not post any collateral, so repayment depends on the broker's assessment of each borrower rather than on assets locked on the ledger.
That is a notable departure from the lending models common in decentralized finance, where borrowers typically lock up more value than they borrow and positions are liquidated automatically if collateral falls too far. Here, the ledger handles the movement of funds, while credit decisions happen elsewhere.
The ledger's own documentation states plainly that the system relies on off-chain underwriting and risk management. In other words, the evaluation of who should receive a loan, and on what terms, is carried out by the broker outside the blockchain.
For depositors, the main protection is the broker's judgment, supported by first-loss capital that the broker contributes. First-loss capital absorbs losses before depositors do, so a broker that makes poor lending decisions puts its own money at risk first. Beyond that cushion, depositors are exposed to defaults.
The split of roles is deliberate. Depositors supply the capital and earn a return, the broker selects borrowers and sets terms, and the ledger records each step of the process. Each party carries a distinct piece of the risk, and the arrangement only works if depositors trust the broker's ability to choose borrowers who will repay on time.
5. Why Ripple is targeting payment companies
Ripple has pitched the lending setup to payment companies that need short-term cash while cross-border settlements are still clearing. Firms that move money between countries often have to pay out funds before they receive the corresponding incoming payment, creating a temporary funding gap.
Fixed-term, uncollateralized loans are designed to fill that kind of gap. A payment company with a known settlement timeline could borrow for a set period and repay once the incoming funds arrive, without having to tie up its own assets as collateral.
The model resembles traditional trade and working-capital finance more than typical crypto lending. That positioning reflects Ripple's long-running focus on banks and payment providers as the core users of the XRP Ledger, rather than retail traders seeking leverage.
It also explains why the underwriting sits off-chain. Assessing the creditworthiness of a regulated payment business draws on financial statements, relationships and legal agreements that do not naturally live on a public ledger.
For the XRP Ledger, a working lending market would add a new kind of activity to a network best known for payments and token transfers. Funds that today sit idle between transactions could be put to use, and vault deposits would give holders of XRP and other tokens on the ledger a way to earn a return tied to real-world business borrowing.
6. Other amendments lose ground
Not every pending proposal gained support over the same period. ConfidentialTransfer, an amendment that would hide token balances, slipped from 22 votes to 21. DynamicMPT, which would let token issuers change settings after launch, fell from 18 votes to 16.
Those declines show that validators are actively weighing individual changes rather than approving them as a bloc. Support can move in both directions, and a proposal that appears close to the threshold can lose momentum.
The movements are visible only as totals. The dashboard's daily records note that no per-validator data is published on any public surface, so the switches can be counted but the validators behind them cannot be named.
That limitation leaves an open question for observers trying to understand the governance dynamics behind each change. Without validator-level data, it is impossible to tell whether the same operators are moving toward lending while moving away from other features.
Greater transparency would make it easier for businesses waiting on a feature to understand where resistance lies and what concerns remain unaddressed. As it stands, developers and would-be users can only infer validator sentiment from the direction of the totals.
7. Developers keep building ahead of approval
Work on the lending code has continued while the vote is pending. Pull request #8685 in the rippled repository, opened on November 4 and still open, would add a third lending amendment named LendingProtocolV1_2.
The proposed change addresses a specific sequencing problem. It would make a bundle of transactions that opens a loan, along with its linked escrows, fail as a single unit if another loan with the same broker is processed first. That prevents a partially completed loan setup from being left behind when two operations collide.
Separately, a cleanup fix that repaired parts of the existing lending code went live on November 4 at ledger 108,112,129. That fix had already reached activation, while the main lending and vault amendments remain short of the threshold.
The steady stream of patches indicates that developers are refining the system before it goes live, which could reassure validators who want to see edge cases addressed before giving their support.
8. What's next for lending on the XRP Ledger
The next milestone is reaching 29 votes for both the vault and lending amendments. SingleAssetVault needs six more validators to signal support, and LendingProtocol needs seven. Once both reach the threshold, a two-week countdown begins, and lending can open only if support holds throughout that period.
No public schedule exists for when the remaining validators might decide. The pace of the past three weeks, with three new votes for lending, gives a rough sense of momentum, but individual validator decisions are not announced in advance.
Meanwhile, LendingProtocolV1_2 remains under review as an open pull request, and further fixes could follow. Whether those changes are bundled into the current voting cycle or proposed as separate amendments will affect how many approvals are ultimately needed before the full system is ready.
For banks and payment companies considering the system, the key questions are when the threshold will be reached and how much protection broker first-loss capital will provide. For depositors, the design makes clear that the quality of off-chain underwriting will be central to the safety of their funds.