The XRP Ledger Lending Protocol (XLS-66): how it works and where it stands in November 2026

Lending on the XRP Ledger (XRPL) has usually meant a separate application sitting on top of the network. The XLS-66 Lending Protocol (XRPL-Standards, XLS-66) proposes building it into the ledger itself, on top of another proposal, the Single Asset Vault (XLS-65) (XRPL-Standards, XLS-65). Both shipped in version 3.1.0 of the server software (xrpl.org), but neither is live on mainnet yet: as of 12 November 2026, validator support was below the activation threshold (XRPScan).

Below: what the protocol does, exactly where it stands, and what is still unknown.

A vault is a shared pool on the ledger that holds one type of asset collected from several depositors. The specification describes it as a new on-chain building block that aggregates assets so other protocols can use them.

• Depositors receive shares, issued as Multi-Purpose Tokens (MPTs). Withdrawing burns shares and returns the asset.
• A vault can be public (anyone can deposit) or private, where only accounts holding on-ledger credentials can deposit (via Permissioned Domains).
• The specification notes that a holder may get back more or less than they put in. The deposit is not guaranteed.

The proposal has three roles:

1. Depositors put assets into the vault.
2. The Loan Broker manages the vault and the protocol and issues the loans.
3. The Borrower receives a loan funded from the vault.

The key design choices, according to the specification:

• Uncollateralised, fixed-term loans. The protocol deliberately leaves out automated on-chain collateral and liquidation. Creditworthiness is assessed off-chain (off-chain underwriting).
• A fixed repayment schedule. Each loan has a known end date and a constant periodic payment, amortisation-style. The ledger tracks the remaining payments and the next due date.
• First-loss capital. The broker can optionally post its own cover. If a loan defaults, a set share of that cover goes back to the vault to reduce depositors' losses. If cover drops below the minimum, the broker cannot issue new loans.
• Interest and fees. There is a regular rate, a late rate and an early-repayment rate, plus broker fees (origination, service, late and early payment). The management fee comes out of the interest that would otherwise go to depositors.
• Default. After each due date there is a grace period; once it passes, the broker can mark the loan as defaulted.

The release notes put it in one line: loan brokers can create fixed-term, uncollateralised loans using pooled funds from a Single Asset Vault (xrpl.org).

New rules on the XRPL are called amendments. According to the official documentation, an amendment is enabled once more than 80% of trusted validators support it for two weeks without interruption; if support falls to 80% or below, the two-week clock restarts (xrpl.org – Amendments). Servers that do not upgrade become "amendment blocked".

Support at two points in time:

A follow-up amendment, LendingProtocolV1_1, arrived with release 3.4.0 and also stood at 22 of 35 on 12 November (XRPScan).

On 18 June 2026, RippleX, Ripple's developer arm, published a long post on the security work behind the protocol (RippleX on DEV Community). The factual milestones:

• Halborn audit of the vault (February–April 2025): seven findings, two of them critical; RippleX says all were addressed.
• Immunefi Attackathon (October–November 2025): a $200,000 prize pool paid in RLUSD, 455 submissions, 94 unique valid findings.
• A second Halborn audit of the full protocol (December 2025–January 2026).
• Community testing: 257 test cases run by XRPL Commons, all passing.
• Formal verification by Common Prefix (February–April 2026), modelled in Lean 4.

RippleX split the fixes between releases 3.1.3 and 3.2.0, and the post frames the work as the road toward mainnet, not as a finished process.

1. When it will activate. We found no source confirming a mainnet activation date. Validator votes can move in either direction.
2. Why support changed between September and November. We found no official statement explaining it.
3. The specification is still a Draft. Details may change before activation.
4. Credit risk is not assessed here. Uncollateralised lending depends on off-chain underwriting, and no protocol can guarantee its quality.
5. This is not price analysis. The article describes technical status only. It says nothing about prices and makes no forecast.

• XLS-66 enables uncollateralised, fixed-term loans funded from pooled vaults (XLS-65).
• The code has been in the server software since January 2026, but it is not active on mainnet.
• On 12 November 2026 support stood at roughly 63–66%, against a threshold of 80% for two weeks.

Our earlier XRP piece: Fake XRP airdrops: how the scam works. How networks and wallets work, from the ground up: Crypto Academy. The history of the XRP Ledger and Ripple, from documents: RIPPLE – the book.

• XRPL-Standards, XLS-66 Lending Protocol: https://github.com/XRPLF/XRPL-Standards/blob/master/XLS-0066-lending-protocol/README.md
• XRPL-Standards, XLS-65 Single Asset Vault: https://github.com/XRPLF/XRPL-Standards/blob/master/XLS-0065-single-asset-vault/README.md
• xrpl.org, rippled 3.1.0 release notes: https://xrpl.org/blog/2026/rippled-3.1.0
• xrpl.org, Amendments (activation rule): https://xrpl.org/docs/concepts/networks-and-servers/amendments
• xrpl.org, Known Amendments (snapshot of 16 September 2026): https://xrpl.org/resources/known-amendments
• XRPScan, amendment voting status (checked 12 November 2026): https://xrpscan.com/amendments
• RippleX, "The Road Toward Mainnet: A Security-First Approach to XRPL Lending Protocol" (18 June 2026): https://dev.to/ripplexdev/the-road-toward-mainnet-a-security-first-approach-to-xrpl-lending-protocol-3bn6

Educational content. Not financial or investment advice, and not a forecast. Data Analytic Investments is not affiliated with Ripple Labs Inc., the XRP Ledger Foundation, XRPScan or the organisations cited; names are used for identification only.