XRP Ledger Lending – The Default Math Nobody Shows

If an XRP Ledger loan defaults, the broker’s cover pays a capped amount set by formula and the vault’s depositors absorb the rest, whatever size the buffer was.
Key Takeaways
- Cover payout is a formula, not the buffer.
- A doubled buffer pays the same per default.
- Closed-ended vaults lock deposits for the full term.
- Issuers can claw back vault assets and cover.
Ripple’s Swell 2026 recap, published November 16, said a panel of VS1, Cicada, Arf and Clearpool discussed their plans for the proposed XRPL Lending Protocol, and that underwriting and credit decisions stay with the institutions running each pool. The recap does not say which of the four would act as broker, who would post cover, or on what terms. Those gaps are where a depositor’s money sits.
The lending and vault amendments still need validator approval, so nothing below describes a live product. It describes the rules any product built on them inherits.
What the ledger holds, and what it leaves to the broker
A depositor puts one asset into a Single Asset Vault and receives shares in it. A loan broker, an on-ledger object controlled by whoever operates the pool, lends the vault’s assets to borrowers on fixed terms. The protocol documentation is explicit that loans are uncollateralized and that the current implementation leaves out on-chain collateral and liquidation management. Validators confirm each transaction follows the rules; nobody on the ledger checks whether the borrower can pay.
Ripple’s design explanation keeps credit assessment, legal documentation and compliance off-ledger, a split Coindoo examined when the amendments first went to validators. The first product to assign those jobs publicly was the fund Ripple, Clearpool and Cicada Partners announced on August 20: Cicada sources borrowers, sets terms and underwrites; Clearpool builds the pool infrastructure; Ripple invests as a limited partner on the same terms as other investors; loans are denominated in RLUSD. VS1 and Arf appear in the Swell recap without a stated role.
Two details in that structure change what “backed” means. Ripple as a limited partner ranks beside depositors, not behind them. And RLUSD is an issued token, which gives its issuer clawback rights the protocol honours: the documentation allows issuers of trust-line tokens and MPTs to claw back from the vault and from the broker’s first-loss capital, leaving only a floor equal to total debt multiplied by the minimum cover rate. A pool denominated in native XRP has no issuer and no clawback path.
The day a payment stops
A missed payment opens a grace period. When it ends, the broker may declare the loan in default; a broker that expects a miss can also record an impairment earlier, which pulls the next due date forward. On default, the ledger deletes the loan, writes the loss against the vault, and moves one slice of the broker’s cover into the vault to offset it.
The size of that slice is set by three broker parameters in the XLS-66 specification: the cover actually deposited, the minimum cover rate (the share of total debt the broker must hold as cover) and the liquidation rate (the share of that minimum that can be spent on a single default). The amount paid out is total debt × minimum rate × liquidation rate, capped at the default amount and at the cover on hand. The broker’s full balance never enters the calculation.
Run that for a pool with 1,000,000 units of debt, a 10% minimum rate and a 10% liquidation rate, where a 50,000-unit loan defaults. Then run it again for a broker that posted twice the cover.
Broker A · 100,000 cover posted
Required cover · 100,000
Max per default · 10,000
Default · 50,000
Paid from cover · 10,000
Vault loss · 40,000
Cover after · 90,000 against 95,000 now required
Broker B · 200,000 cover posted
Required cover · 100,000
Max per default · 10,000
Default · 50,000
Paid from cover · 10,000
Vault loss · 40,000
Cover after · 190,000 against 95,000 now required
Illustrative parameters matching the protocol’s own documentation example. Ignores fees, rounding, accrued interest and concurrent defaults.
Depositors in both pools take the same hit. The extra 100,000 Broker B posted protects Broker B, not them: after the default, Broker A’s cover sits below the minimum the protocol now requires on the remaining debt, which blocks it from issuing new loans and diverts its fees into rebuilding cover until the gap closes. Broker B keeps lending. A large buffer is a sign the operator can stay in business through a default, which is useful to know. It is not a sign depositors are insured.
Interest due at the time of default counts toward the default amount, so the vault’s loss includes income it had already been promised. Anything recovered later through a legal claim on the borrower happens off-ledger under whatever contract the broker signed, and the protocol has no field for it.
The audit that priced the gap
Halborn’s re-audit of the lending code, run from December 16, 2025 to January 12, 2026, looked directly at the mechanism above. It found no critical or high-severity issues. Three of its five findings concern the cover rules, and all three were accepted rather than fixed.
HAL-02 describes the Broker A scenario taken one step further. With a liquidation rate under 100%, a run of defaults can push cover below the minimum while further loans are still outstanding and still able to default; the broker is frozen, the losses keep landing on the vault. HAL-05 means the ledger accepts any pair of rates a broker sets, including combinations that make the per-default payout trivially small. Neither is a bug in the code. Both are confirmation that depositor protection is a configuration the operator chooses and the protocol enforces as written.
Two ways a vault can look healthier than it is
The LendingProtocolV1_1 amendment, a separate proposal from the base protocol, adds closed-ended vaults and restricts all loans to them. A closed-ended vault runs through three phases: a subscription window in which deposits and withdrawals are free, an investment phase in which both are blocked and the assets are lent out, and a redemption phase in which loans have matured and depositors can withdraw. A pool with no default on its books can still refuse a withdrawal for the whole investment phase, so the dates in a product’s terms are the first thing to read.
The same amendment changes how interest is counted. Vaults created before it activates use instant recognition: the full interest a borrower is scheduled to pay over the life of the loan is booked as vault income at origination, and those vaults keep that method permanently. Vaults created after it use cash-basis accounting, recording interest only when a payment delivers it. Under the older method a vault’s share value can carry income that no borrower has yet paid, and a default erases it along with the principal.
Five things to check before depositing
- Who underwrites, and how concentrated the book is. One borrower and twenty borrowers produce different losses under identical ledger rules.
- The three cover numbers. Cover deposited, minimum rate, liquidation rate. Together they give the maximum payout per default; the headline balance alone gives nothing.
- Whether the vault is closed-ended, and its phase dates. That decides when money can leave, independently of whether any loan is performing.
- Which accounting method the vault was created under. Instant recognition shows income before it exists; cash-basis does not.
- The asset and its issuer. An issued token brings clawback rights over the vault and most of the cover; XRP brings none. Ripple investing in a pool puts it beside depositors, not behind them.









