A lender clicks "Fund" on a 30-day XRP loan to a vetted merchant. Settlement takes seconds. Interest starts accruing immediately. No bank desk, no intermediary, no waiting. That's not a whitepaper promise anymore: Ripple has published the actual specs, opened devnet for testing, and validators on mainnet are already casting votes.
On June 29, Ripple's team formally introduced two technical proposals: XLS-65 (Single Asset Vaults) and XLS-66 (the native Lending Protocol). Within days of the announcement, a public demo at lending.xls-demo.com showed the full loan cycle running on devnet, including vault creation, liquidity deposits, uncollateralized fixed-term loans, and repayments. Builders could watch the whole thing in motion before a single validator approved anything for mainnet.
Why credit, and why now
XRPL has handled payments and asset exchange for years. Liquidity moves fast on the ledger. But credit, the mechanism that stretches capital across time, has lived almost entirely offchain or inside DeFi protocols on other networks. Ripple's proposal is a direct attempt to fix that gap by making lending a first-class object on the ledger itself, not a layer bolted on top.
The people with the most to gain are payments businesses that need predictable funding costs, market makers who manage short-term liquidity windows, and retail depositors willing to supply assets into vaults in exchange for yield. Uncollateralized fixed-term loans are part of the picture too, which puts XRPL in territory that most blockchain credit markets haven't touched at scale.
Two specs, one credit layer
XLS-65 defines Single Asset Vaults. Each vault holds one asset type and tracks depositor shares in a standardized way, so any application reading the ledger gets the same accounting view. XLS-66 sits on top: it handles loan terms, fund disbursement, interest accrual, and repayment settlement. Together they give developers a common interface instead of forcing every lending app to rebuild core credit logic from scratch.
Neither amendment is active on mainnet yet. XRPL's governance model requires a supermajority of validators to support an amendment continuously through a defined voting window before it activates. The LendingProtocol amendment (ID: 565B90CA1AB2B9D42208ED10884188C64F9E19083DECB9634AAF06EB03299509) and SingleAssetVault are both listed as open for voting on mainnet as of late June, according to the official XRPL Known Amendments documentation. Sustained supermajority support is required, and that's not guaranteed.
If the amendments do pass, applications won't need bespoke smart contract logic for every lending operation. Vault deposits, loan creation, and repayment tracking all become standardized ledger objects, which generally means fewer failure points and more consistent fee behavior across the ecosystem. The devnet demo already shows what that flow looks like in practice. Whether mainnet validators agree is the next question.
This article is for informational purposes only and does not constitute financial advice or an investment recommendation.
