Ripple Yes Vote Pushes XRPL Toward Native Institutional Credit

Ripple’s validator cast yes votes for the Single Asset Vault (XLS-65) and Lending Protocol (XLS-66) amendments, lifting support to 40 percent and just over 37 percent. Both still need 28 of 35 dUNL validators for two continuous weeks before mainnet activation.

The move is more than a tally tick. It advances a design that keeps credit underwriting and compliance off-chain while the ledger itself handles loan terms, interest, repayment and default, giving institutions a familiar risk model on native rails.

That split is the point of the design. Institutions keep the work they already know how to do. The ledger takes the work that benefits from shared state, final settlement and a single source of truth for balances and schedules.

Ripple’s Yes and the Current Tally

After Ripple’s support the current 40 percent and 37 percent tallies appear on XRPScan for SingleAssetVault and LendingProtocol. Threshold remains 28 yes votes out of the 35-validator unique node list.

Both amendments shipped in the 3.1.0 release and opened for voting in late January 2026. Earlier snapshots in spring and early summer sat near 20-23 percent. The climb has been deliberate.

The gap from the spring and early summer range near 20-23 percent to today’s figures is still large in absolute votes. Fourteen and thirteen yes votes leave a long path to twenty-eight. Ripple’s flip removes a high-profile holdout without closing that gap on its own.

Ripple also urged validators to move to the 3.3.0 release. Network data shows roughly 39 percent already running it. That upgrade path sits alongside the lending vote rather than blocking it.

Operators who delay the binary upgrade risk a different problem later. Once any amendment activates, older software can leave a node amendment-blocked. The lending pair and the 3.3.0 push therefore move in parallel even though they are separate decisions.

Vaults Pool One Asset at a Time

XLS-65 creates a standardized on-ledger structure that accepts deposits of a single asset type. XRP, RLUSD or another issued token can each have its own vault. Multiple depositors contribute; each receives proportional shares that can be transferable or locked by configuration.

The vault then supplies liquidity into other protocols. It is the capital base, not a free-floating pool that mixes assets and multiplies risk surfaces.

• Depositors keep proportional ownership via vault shares.
• One asset per vault keeps accounting and risk isolation clean.
• Permissioned domains and credentials can gate who may deposit or withdraw.
• Shares can feed directly into the lending layer once XLS-66 activates.

That design choice matters for institutions that already manage single-asset sleeves and want the ledger to enforce the boundaries they already use offline.

Mixing assets inside one pool would force joint accounting, joint risk limits and joint reporting. Separate vaults avoid that tangle. A sleeve of XRP and a sleeve of RLUSD can follow different mandates, different counterparties and different internal limits while still using the same on-ledger primitive.

Share configuration adds another control surface. Transferable shares support secondary movement of economic exposure. Locked shares keep participation inside a defined set of holders. Permissioned domains and credentials let operators decide who may enter or exit without rewriting the vault’s core accounting.

Loans Stay Fixed and Underwritten Off-Chain

XLS-66 builds directly on those vaults. It enables on-chain fixed-term uncollateralized loans funded from the pooled capital. Loan terms, interest schedules, amortization, repayment and default handling live on the ledger. Credit decisions and compliance stay with the institutions that already run those processes.

A first-loss capital layer sits in front of the depositors. The broker or originator posts its own funds that absorb initial losses before vault shares take a hit. That structure is closer to traditional structured credit than to over-collateralized DeFi loops.

Borrowers and lenders interact through on-ledger objects. No intermediary bank sits between the vault and the loan once the terms are set. Settlement finality remains the XRPL’s usual sub-second, low-cost path.

Fixed terms change the risk shape. Open-ended, market-priced borrowing invites recursive leverage and sudden liquidations. A fixed schedule with known amortization and an explicit default path gives depositors and originators a timetable they can model in advance.

Uncollateralized in this model does not mean unexamined. Underwriting and compliance remain off-chain with the parties that hold the credit files. The ledger records what those parties already agreed, then enforces the money flows that follow from that agreement.

How the First-Loss Layer Shields Vault Shares

The first-loss buffer is the bridge between institutional credit practice and on-ledger funding. Originators put their own capital at risk ahead of the pooled vault. Early losses hit that buffer first. Vault shares take damage only after the buffer is exhausted.

That ordering matters for depositors who want yield without taking first-dollar credit risk. It also disciplines the broker. Skin in the game at the front of the stack is a familiar demand in structured credit, and the amendment carries that demand onto the ledger rather than replacing it with a purely algorithmic rule.

Once terms are set, the path from vault to loan no longer needs a bank in the middle. On-ledger objects hold the relationship. Interest, repayment and default handling follow the recorded schedule. Settlement stays on XRPL’s normal finality path: sub-second and low cost, the same qualities the network already applies to payments.

The result is a credit surface that institutions can map to existing desks. Underwriters still underwrite. Compliance still clears counterparties. The ledger becomes the system of record for the economic terms and the settlement engine for the cash flows, not a replacement for credit judgment.

The Audit Path That Cleared the Code

Security work ran for months before public voting pressure rose. Halborn performed an initial Single Asset Vault assessment in early 2025, followed by Attackathons and a full Lending Protocol re-audit after fixes.

1. February-April 2025: Halborn smart-contract style review of vault create, deposit, withdraw, set, delete and clawback flows.
2. Later 2025: Immunefi and Sherlock Attackathons with large researcher pools and prize money; no critical findings remained open.
3. December 2025-January 2026: Halborn re-audit of the updated lending codebase covering transaction checks, accounting, access controls and state consistency.
4. Mid-2026: Final clear; five residual findings (one medium, two low, two informational) all addressed or accepted.

The re-audit found no critical or high-risk issues. That record is why some validators waited before flipping to yes: the code had to survive the same scrutiny institutions demand for production credit systems.

The sequence itself is part of the signal. Vault flows were reviewed first. Public Attackathons stress-tested the work with large researcher pools. Only after fixes did the lending codebase return for a full re-audit of transaction checks, accounting, access controls and state consistency. Residual items at the end were medium, low or informational, and all were addressed or accepted.

Validators that held back were not only watching feature scope. They were waiting for that chain of reviews to finish without open critical findings. For a credit system aimed at institutions, that bar is ordinary, not optional.

Institutions Already Mapping Yield

Builders did not wait for activation. Yield protocol SOIL has stated plans to use the vaults and lending layer for lending, yield generation and tokenized fixed-income products once live. Ripple-backed Evernorth is further along.

Today, we are thrilled to announce Evernorth’s intent to utilize the upcoming XRP Lending Protocol (XLS-66) as a core pillar of our digital asset strategy. This isn’t just another DeFi experiment; it’s what we believe could be a fundamental shift in how institutional liquidity moves onchain. By participating in this native lending ecosystem, Evernorth aims to help unlock what could be a multi-billion dollar annual yield opportunity for the XRP community.

Sagar Shah, Chief Business Officer at Evernorth, made that case in a January 2026 post cited in Ripple’s own institutional DeFi overview. The same page notes Evernorth preparing institutional-grade yield on its XRP holdings through the protocol.

Other names already mapping workflows include groups looking at bond-market rails and reporting infrastructure that already serves large asset managers. The pattern is clear: the capital is being staged before the switch flips.

Staging before activation reduces the cold-start problem. Vaults, shares and lending objects are only useful if capital and workflows are ready when the two-week window closes. SOIL’s stated plans and Evernorth’s positioning show that readiness work is already under way on the product side while validators still debate the tally.

What the Credit Layer Changes for Holders

Once live, idle XRP or RLUSD can sit in a vault, earn the spread from underwritten loans, and remain on the ledger the entire time. Private keys stay with the holder. No bridge or external smart-contract set is required for the core flow.

That creates a mechanical reason for large holders to keep coins vaulted rather than selling into every rally. Crowds on X have already noted the supply-side implication: yield that does not require leaving XRPL changes the sell-pressure math that has defined prior cycles.

It also gives the ledger a second major utility pillar beside payments and the DEX. XRP can be the asset lent, the bridge asset in related FX flows, and the reserve and fee token for every transaction the new credit layer generates. Fee burn and object reserves rise with usage.

The design deliberately avoids the recursive leverage loops that produced many DeFi liquidations. Fixed terms, first-loss buffers and off-chain credit files keep the risk profile closer to private credit funds than to open-market over-collateralized borrowing.

• Vaulted XRP or RLUSD can earn loan spread without leaving the ledger.
• Holders retain keys; the core flow needs no bridge.
• Usage lifts fee burn and object reserves as credit activity grows.
• Fixed terms and first-loss capital limit recursive leverage risk.

Those mechanics stack. Yield on native rails competes with simply holding idle balances. A second utility pillar beside payments and the DEX widens the set of reasons to keep value on XRPL through a cycle rather than only through a payment path.

Where On-Ledger Credit Differs From DeFi Loops

Much open-market DeFi credit relies on over-collateralization and continuous mark-to-market pressure. That model liquidates when prices move. It also invites leverage stacked on leverage when the same collateral is reused across venues.

XLS-65 and XLS-66 take a different route built from the pieces already described. Single-asset vaults isolate risk sleeves. Fixed-term loans replace open-ended debt. First-loss capital stands in front of depositors. Credit files and compliance checks stay with institutions off-chain.

None of those choices removes credit risk. They place it in a shape institutions already price and monitor. The ledger’s role is to hold terms, move funds and finalize outcomes without inserting a new intermediary bank once the loan objects exist.

That is why pre-positioned builders can talk about tokenized fixed-income products and institutional-grade yield in the same breath as native settlement. The amendment pair is trying to look like private credit infrastructure that happens to clear on XRPL, not like a new leverage game that happens to use XRP.

The Climb to Eighty Percent Still Ahead

Support must reach and hold more than 80 percent support for two full weeks. If it dips below that line the two-week clock resets. Default votes in the software start as no; operators must affirmatively switch.

Validators running older binaries risk becoming amendment-blocked once any new feature activates. That pressure already shows in the 39 percent figure for the 3.3.0 release. Operators watching the XRP Ledger v3.3.0 upgrade details know the pattern from prior cleanups and feature bundles.

Earlier amendment races on the ledger followed the same slow-then-sudden path. Some fixes and features sat for months before a cluster of yes votes pushed them over the line and the two-week timer started. The lending pair is larger in scope, so the caution is higher, yet the security record and pre-positioned builders reduce the usual unknowns.

Related coverage of earlier amendment activation patterns shows exchanges and node operators often lag the core validators. That lag can stretch the final stretch even after consensus is mathematically reached.

Ripple’s public yes removes one large uncertainty. The remaining work is ordinary validator coordination, not new design. If the tally keeps rising, the two-week window can open inside the current quarter. When it closes successfully, the XRP Ledger will settle its first native fixed-term institutional loans the same way it has settled payments for more than a decade: final, cheap, and on-ledger.