XRP Ledger
XRPL Lending Reaches 22 Votes: Three Amendment Paths to Track
XRPL lending has 22 of 35 validator votes, below the 29 needed. Separate vault and V1.1 approvals determine when operators can use the planned lending design.

What the November 12 XRP Ledger lending snapshot establishes
XRPL lending is still awaiting approval. A November 12 tracker snapshot shows 22 of 35 votes for LendingProtocol and its V1.1 extension, with 23 for SingleAssetVault. Each remains below the 29-vote threshold. A validated ledger check confirms none is enabled, so there is no confirmed launch date. [1][4]
XRPL Dashboard’s 13:44 UTC roll call supplies the vote counts below. CoinDesk’s November 12 report and Bitcoinist’s same-day coverage corroborate the lending and vault totals. The primary ledger record answers a different question: at ledger 108283352, captured at 13:58 UTC, the enabled-amendment list excluded all three identifiers and the Amendments object contained no pending majority. [1][4][5][9]
The useful distinction is between a changing tally and an enforceable network state. Votes indicate support; a recorded majority starts an approval period; enabled status establishes which rules transactions actually face. Keeping these observations separate lets an operator update a launch checklist without treating a favorable news report as permission to accept production deposits. [1][3][4]
| Amendment | Yes votes | Required at 35 | Additional votes needed |
|---|---|---|---|
| SingleAssetVault | 23 of 35 | 29 | 6 |
| LendingProtocol | 22 of 35 | 29 | 7 |
| LendingProtocolV1_1 | 22 of 35 | 29 | 7 |
| Source: XRPL Dashboard’s dated roll call [4]. Required votes follow XRPL’s strictly-more-than-80% rule [3]. Gaps are calculated as 29 minus yes votes. Counts can change. | |||
Why 28 votes would still leave an amendment short
XRPL’s official amendment process requires support above 80 percent for two weeks. With 35 counted validators, 28 is exactly 80 percent, so 29 is the first qualifying whole-number tally. The number 29 belongs to this denominator; it should not be presented as a permanent threshold independent of the validators counted. Independent tracking and reporting use the same current threshold. [3][4][9]
Analysis: the gaps in the table cannot be added into a request for 20 new validators. The same operator may support several amendments, and each amendment has its own result. Equally, a yes vote for the vault cannot be transferred to the lending tally. A useful readiness report therefore records three amendment identifiers and three states, rather than one combined approval percentage. [2][3][4]
Nor does “two weeks” mean two weeks from today’s article. The qualifying period follows a majority, and support can be lost before activation. Uncertainty: no current majority was present in the validated record checked here. There is no sound basis for publishing a calendar launch promise by adding 14 days to November 12. [1][3][4]
How to interpret the next XRPL voting alert
A useful alert should identify the amendment, the observation time, the count and the threshold used. A second alert with the same headline percentage is not necessarily a second approval event. Compare like-for-like observations before deciding that support changed. The current ledger object is the stronger record for whether a majority or enabled state exists. [1][3][4]
Analysis: an internal status report could have separate fields for observed votes, recorded majority and activation confirmation. Assigning those fields separately prevents a news headline from overwriting an operational control. It also gives the person authorizing a launch a specific missing condition to resolve, instead of a vague assessment that the network is almost ready. [3][4]
Uncertainty: the counts alone do not explain individual validators’ motives, prove a durable coalition, or identify customers preparing to borrow. Equal totals for LendingProtocol and V1.1 also do not establish that exactly the same operators supplied every vote. Assess the proposals individually and seek operator statements before attributing a change to security confidence, commercial demand or a coordinated strategy. [4][5]
SingleAssetVault, LendingProtocol and V1.1 answer different questions
SingleAssetVault provides pooled assets; LendingProtocol supplies the base loan mechanism. LendingProtocolV1_1 extends those designs with closed-ended vaults and cash-basis accounting. Ripple’s current V1.1 documentation describes subscription, investment and redemption phases, while Crowdfund Insider independently reported that structure on October 21. These are operating rules with separate approval status, not interchangeable names for one proposal. [2][6][8]
For a team building the V1.1 product, “lending is enabled” would be an incomplete acceptance condition. Its checklist must also establish the vault capability and the extension governing its chosen workflow. That does not mean V1.1 is a prerequisite for every possible use of the original lending amendment. It means a product specified around V1.1 must verify that particular version of the rules. [2][6][8]
Analysis: suppose vault support reaches a majority before loan support. The earlier vault milestone would not start the lending amendment’s clock. If the loan amendment later qualifies, its own approval period must be evaluated separately. The same reasoning applies to V1.1. Operators should tie readiness to the last required capability actually enabled, without assuming the three schedules will align. This is a conditional planning example, not a forecast of vote order. [2][3][4]
V1.1 changes what depositors should ask before committing assets
The phase structure makes the deposit and redemption schedule part of the product specification. A prospective depositor should ask when subscriptions stop, when lending may occur, when redemption becomes available, and which terms govern the interval between those events. Those questions help assess whether a proposed vault fits the depositor’s cash needs. A phase name alone supplies neither a personal withdrawal commitment nor a service-level guarantee. [6][8]
The accounting change is equally practical: interest is recognized as income when payments arrive, rather than treating all scheduled interest as earned at origination. The official amendment description and independent reporting agree on this distinction. Analysis: a repayment schedule, a recognized income balance and spendable assets answer different questions. A report that displays an expected return should make clear whether it represents a forecast, received interest or money available for distribution. [2][6]
For example, an operator assessing a proposed distribution should reconcile what borrowers were due to pay with what was actually received, then explain any difference before describing a depositor payout. That is a suggested reporting control, not a claim about a deployed XRPL fund. Cash-basis recognition makes the timing distinction clearer, but it cannot establish that a borrower will meet a future obligation. [6][8]
What lending operators can prepare before activation
The protocol’s credit model still depends on off-chain underwriting and risk management. Official documentation describes fixed-term, uncollateralized lending, with first-loss capital available to help absorb defaults; CoinDesk independently describes these same credit dependencies. Validator approval evaluates a network rule change. It does not substitute for reviewing the borrower or establish the financial strength of a particular lending operation. [5][7]
Analysis: operators can prepare a borrower-review procedure, identify who is responsible for missed-payment decisions, and describe how they intend to fund loss protection before opening a vault. They can also prepare reports that separate outstanding principal, payments received and overdue amounts. These are suggested operational deliverables, not evidence that named institutions have completed them or committed capital. [5][7]
For application teams, the immediate task is to define a fail-closed launch checklist: identify the intended amendment combination, confirm its Mainnet enabled state, and verify that the application’s advertised deposit and redemption behavior matches that combination. Test results should identify the network and enabled features used. A demonstration against one feature configuration does not establish that another configuration will accept the same workflow. [2][7][8]
For XRP holders, the vote totals measure protocol governance. They do not measure new loan balances or borrower demand for XRP. The next meaningful operating evidence would identify the asset in a real vault, deposits, executed loans and subsequent payments. Uncertainty remains over whether and when any proposed service will attract that activity. Those records, rather than an approval percentage alone, would support a later analysis of usage. [4][5][7]
What to watch next
- • A recorded majority for each named amendment, with its start time and any subsequent loss of support, followed by the enabled state. [1][3][4]
- • Fresh vote counts with the observation time and validator denominator, rather than a percentage copied from an older snapshot. [3][4]
- • A lending operator’s explicit declaration of whether its product uses the original rules or the V1.1 closed-ended design. [2][8]
- • Published subscription and redemption terms, borrower-assessment responsibilities, and evidence of funded loss protection for a specific offering. [5][7][8]
- • Validated Mainnet vault, loan and repayment records identifying the asset used before attributing activity to XRP demand. [2][7]
Sources and verification
We prioritize primary records and label supporting coverage. Dates reflect each source’s publication record.
- [1]XRP Ledger public RPC, validated Amendments object at ledger 108283352 (undated service; observed November 12, 2026, 13:58 UTC)primaryUndated reference
- [2]XRP Ledger, Known Amendments (undated reference; checked November 12, 2026)primaryUndated reference
- [3]XRP Ledger, Amendments (undated reference; checked November 12, 2026)primaryUndated reference
- [4]XRPL Dashboard, validator roll call at November 12, 2026, 13:44 UTC (undated live tracker)supportingUndated reference
- [5]CoinDesk, Ripple’s bank-lending system moves closer to launch on the XRP Ledgersupporting
- [6]Crowdfund Insider, XRP Ledger Nears Activation of Protocol Cleanup Amendment Addressing Lending Codesupporting
- [7]XRP Ledger, Lending Protocol (undated reference; checked November 12, 2026)primaryUndated reference
- [8]Ripple Open Source, Lending Protocol V1.1 (undated reference; checked November 12, 2026)primaryUndated reference
- [9]Bitcoinist, XRP Ledger Lending Proposal Gains Momentum as Validators Move Closer to Approvalsupporting