XRPL Weighs XLS-66 Native Lending for Pooled Fixed-Term Loans

The XRP Ledger is considering a base-layer lending standard, XLS-66, that would let pooled assets fund fixed-term, uncollateralized loans on the network. It sits on XLS-65 Single Asset Vaults. Features have been available on a development network. Mainnet use still needs validator approval. The design records loan terms on the ledger and leaves credit judgment with a broker. That is infrastructure, not a credit market.

Vaults Hold Cash, Brokers Take Risk

A vault gathers one asset—XRP, an issuer-backed IOU or a Multi-Purpose Token—and issues shares that mark each depositor’s claim. Shares are ownership, not a promise of instant cash. Once the pool has lent, a holder may not redeem the same liquid amount. Vault documents will have to say how withdrawals work while loans are outstanding, whether requests queue, and whether lending is capped against free cash.

XLS-65 allows public vaults and private ones that restrict access with on-ledger credentials. Institutional pools and open pools can coexist. “Native lending” will not mean one product.

A loan broker stands between the vault and the protocol. The broker creates the pool, originates loans, sets management fees and decides whether to post first-loss capital. Under XLS-66, broker and borrower write a loan with principal, rate, payment interval, maturity and grace period. The loan object tracks what remains unpaid and can record late interest, origination fees and early-repayment charges. If payments slip past the grace period, the broker can mark the loan impaired or defaulted.

Defaults Stay Off the Ledger

A default flag is an accounting event. It does not collect the unpaid sum. Recovery still depends on the legal contract and the broker’s work-out. The spec omits automated on-chain collateral and forced liquidations. Authors chose off-chain underwriting instead.

The broker must decide if a borrower can repay. That may rest on financial statements, trading books, guarantees or collateral held outside XRPL. The proposal does not set one underwriting method. That may fit market makers and firms that already run credit desks. It also means depositors are buying the broker’s discipline. Settlement on a shared ledger can cut reconciliation fights. Evernorth chief business officer Sagar Shah has made that point in a company communication filed with the SEC. Shared data does not replace a credit file.

First-Loss Capital Is Not a Guarantee

A broker may deposit first-loss capital. In a default, part of that buffer can be liquidated back to the vault so depositors take less of the hit. The size only matters against the book. One million XRP against five million of loans is not the same as one million against 100 million.

Before money enters a pool, the terms that matter are ordinary bank questions: the broker’s legal entity and governing law; who may borrow, including affiliates; how much of the vault can go to one name; first-loss capital as a share of outstanding debt; when shares can be redeemed if most of the pool is lent; and who pursues recovery after default. An advertised yield without those answers is incomplete.

XLS-66 still depends on XLS-65 and related amendments. Activation would publish the primitives. It would not produce borrowers, liquidity or a tested broker set. The Block reported on Aug. 20 that Evernorth, an XRP treasury firm preparing to go public, is exploring DeFi uses and that Shah is interested in XLS-66. Evernorth does not control the spec and no primary filing names an Evernorth-run pool.

Conclusion

XLS-66 would put loan terms and payment status on XRPL and leave default risk with brokers and depositors. The first useful evidence will be named brokers, published coverage ratios, withdrawal rules and an on-ledger repayment history that lasts more than a marketing cycle. Until those exist, treat the standard as a draft rail. Native settlement does not make unsecured credit safe.