Ripple’s XRP Ledger lending framework, comprising amendments XLS-65 and XLS-66, is now open for mainnet validator voting with devnet integration testing available to outside developers. Ripple’s open-source documentation confirms both amendments carry “Open for Voting on Mainnet” and “Available for testing on Devnet” status.
Key Takeaways
- XLS-66 and XLS-65 both carry open-for-voting status on mainnet as of June 30, 2026, with activation requiring more than 80% of trusted validators to continuously support the amendments for two weeks.
- Both amendments are simultaneously available for integration testing on devnet, according to Ripple’s open-source documentation, inviting outside developers to build against the protocol ahead of mainnet activation.
- XLS-65 pools XRP, trust-line tokens, or MPTs from depositors and issues transferable or non-transferable vault shares with public or gated Permissioned Domain access configurations.
- XLS-66 enables fixed-term, uncollateralized loan functionality with pre-set amortization schedules, on-ledger contracts between lenders and borrowers, and optional first-loss capital for depositor protection.
- Security firm Halborn completed a third-party audit of both amendments before the protocol entered the mainnet validator voting stage.
What Happened?
Ripple’s open-source portal shows both amendments have reached the same current status. XLS-66’s documentation lists the amendment as “Open for Voting on Mainnet” and “Available for testing on Devnet.” XLS-65 carries the identical status in its own documentation.
Mainnet activation requires more than 80% of trusted XRPL validators to continuously support both amendments for two weeks. The threshold means the validator set must hold its vote without interruption, a rolling two-week window, not a single-moment count.
Developers building on Decentralized finance platforms can now test the full lending stack on devnet. Halborn completed a third-party security audit of both amendments before they entered the validator queue, and performance testing documentation is available through Ripple’s open-source portal.
NEW: @Ripple proposes the XRPL Lending Protocol, letting banks and payment providers borrow against tokenized assets directly on the XRP Ledger. pic.twitter.com/iw0AWAlSpn
— CoinDesk (@CoinDesk) June 30, 2026
Two-Layer Architecture: Single Asset Vault and Lending Protocol
The XRPL Lending Protocol separates liquidity aggregation from credit mechanics into two interdependent amendments, each subject to an independent validator vote.
XLS-65 is an on-chain primitive for aggregating assets from one or more depositors. It pools XRP, trust-line tokens, or MPTs into a shared vault and issues transferable or non-transferable vault shares. Access can be configured as public or restricted to a gated Permissioned Domain, giving vault operators control over which participants can deposit or borrow.
XLS-66 draws from a Single Asset Vault to issue fixed-term, uncollateralized loans. On-ledger contracts govern the terms between lenders and borrowers, with pre-set amortization schedules and optional first-loss capital tranches for depositor protection. The amendment relies on off-chain underwriting while providing peer-to-peer lending without traditional financial intermediaries.
Ripple stated the institutional case for the design in its Insights blog: “No financial institution will turn down low cost capital if it can be sourced within KYC/AML standards.“
The Permissioned Domain gating in XLS-65 addresses the access-control requirement that institutions operating under SEC crypto enforcement data and equivalent regulatory frameworks need before deploying capital into pooled on-chain instruments. The fixed-term, fixed-schedule structure of XLS-66 loans gives institutional treasurers a rate predictability that variable-rate, governance-adjustable lending pools cannot guarantee.
XRPL’s Position in Institutional Lending Markets
The XRP Ledger has surpassed $1 billion in monthly stablecoin volume and holds a top-10 global ranking for real-world asset activity, according to Ripple’s Insights blog, providing a live liquidity base rather than a theoretical one.
Target use cases span stablecoin payments and issuance, RWA tokenization and secondary markets, collateral management, and institutional lending at protocol level with pooled liquidity. A payment company holding stablecoin reserves could borrow short-term against incoming cross-border settlements through XLS-66 rather than drawing on a traditional bank credit line.
Participants tracking crypto adoption by country across jurisdictions will note that the Permissioned Domain architecture is the mechanism, not a regulatory approval, that enables compliant institutional participation in on-chain lending pools.
CoinLaw’s Takeaway
The XRPL Lending Protocol’s dual entry into validator voting and devnet testing on the same day converts what had been architectural documentation into an active governance event. The combination signals the protocol has moved from design to execution phase, with a specific, binary outcome: the continuous 80% validator threshold is either met within the coming weeks or the amendments cycle back to the queue for a new attempt.
The two-layer design is a structural choice worth tracking. Separating XLS-65’s liquidity aggregation from XLS-66’s credit mechanics means each component was audited and can activate independently, reducing the risk of a single technical issue stalling the entire protocol. Pre-activation security review and an open devnet environment address two of the adoption hurdles that typically arise after a mainnet deployment, not before it. Whether the XRPL validator network aligns quickly will serve as the first concrete signal of how urgently institutional lenders want native on-chain credit on the ledger.
