XRP Ledger lending amendments gain Ripple’s backing
Ripple has thrown its support behind two key XRP Ledger (XRPL) amendments, marking an important step toward bringing native lending and institutional-grade yield products directly into the core of the network.
The amendments, known as XLS-65 (Single Asset Vaults) and XLS-66 (Lending Protocol), are currently in the formal validator voting process. Ripple’s validator has voted in favor of both changes, signaling the company’s confidence in the technical design and potential market impact of the new lending infrastructure.
Where the amendments stand in the voting process
Validator voting on XRPL operates under strict rules designed to prevent rushed or controversial changes. Each amendment must maintain support from more than 80% of trusted validators for a continuous two-week period before it can be activated on the mainnet.
Recent voting data shows:
– XLS-65, which introduces Single Asset Vaults, has gathered close to 40% support so far.
– XLS-66, which defines the Lending Protocol, has surpassed 37% backing.
These numbers remain well below the activation threshold. Under the current default Unique Node List (UNL) configuration, at least 28 out of 35 validators would need to support an amendment to cross the required 80% line. Ripple’s affirmative vote gives the proposals momentum, but by itself does not determine if or when they will go live on XRPL.
Each validator on the network independently decides whether to support an amendment. While Ripple is still one of the most influential participants in XRPL’s development, the company does not control the outcome of the voting process and cannot unilaterally push protocol changes into production.
What XLS-65 aims to introduce: Single Asset Vaults
XLS-65 proposes a standardized mechanism for creating “Single Asset Vaults” on the XRP Ledger. In practical terms, these vaults function as pools that hold only one kind of asset contributed by multiple depositors.
Key characteristics of these vaults include:
– Single-asset structure: A vault would be restricted to one token type at a time. This could be XRP, Ripple’s RLUSD stablecoin, or any other issued token on XRPL.
– Proportional ownership: Contributors to a vault would receive shares representing their claim on the vault’s total holdings. These shares scale with the amount deposited, allowing transparent accounting of who owns what portion of the pool.
– Liquidity provisioning: Once funded, a vault can supply its liquidity to other on-ledger services, including the proposed lending protocol described in XLS-66.
The goal is to provide a native, standardized building block for applications that require aggregated liquidity, such as lending, yield products, or structured financial instruments, without resorting to external smart contract platforms.
How XLS-66 builds on these vaults: the Lending Protocol
XLS-66 defines how liquidity from these Single Asset Vaults can be deployed into fixed-term loans. Rather than copying typical overcollateralized DeFi lending models, it is specifically designed with institutional users in mind.
Core features of the proposed Lending Protocol include:
– Fixed-term loans: The system focuses on loans with predefined start and end dates, interest rates, and repayment schedules, rather than purely open-ended borrowing.
– Use of vault liquidity: Funds held in XLS-65 vaults can be lent out to approved borrowers under standardized terms.
– On-ledger enforcement of terms: The XRPL protocol would be responsible for tracking interest accrual, principal balances, repayments, servicing events, and default records.
One of the most notable design choices is that XLS-66 does not require every borrower to overcollateralize their loan. Instead, credit assessment and risk management are pushed off-chain.
Off-chain underwriting, on-chain settlement
In contrast to many decentralized finance protocols that rely on anonymous users, real-time collateralization, and automated liquidations, XLS-66 is structured around traditional credit practices:
– Off-chain underwriting: Institutions would perform credit checks, compliance screenings, legal reviews, and underwriting processes outside the blockchain environment.
– On-chain execution: Once a loan is approved, the agreed terms are encoded on XRPL. The ledger then acts as the source of truth for balances, repayments, interest, and defaults.
Loan brokers or arrangers are expected to play a central role in this ecosystem. They would:
– Match borrowers seeking capital with vaults that have available liquidity.
– Negotiate and structure loan terms with institutional lenders.
– Maintain the credit relationship over the life of the loan.
To further protect depositors, XLS-66 envisions a first-loss capital layer, which would absorb initial losses if a borrower defaults. This structure can help shield vault participants from immediate full exposure while still allowing risk to be priced and allocated among participants.
Regulatory positioning and institutional fit
The architecture is explicitly designed to be compatible with regulated financial institutions, particularly in jurisdictions like the United States where compliance obligations are stringent.
Using the lending protocol would not exempt institutions from:
– Lending and banking regulations
– Securities and investment laws
– Consumer protection statutes
– Sanctions compliance
– Anti-money laundering and know-your-customer rules
Instead, the XRP Ledger would function as robust settlement and record-keeping infrastructure after the required regulatory checks are completed. This separation-off-chain compliance and underwriting, on-chain execution and accounting-is intended to make it easier for banks, fintechs, and credit platforms to adopt on-ledger lending without abandoning established regulatory frameworks.
Security review: what the re-audit found
Before validators decide on mainnet activation, the lending code has gone through several layers of scrutiny. A recent re-audit by blockchain security firm Halborn took a detailed look at:
– Transaction validation and checks
– Ledger accounting rules
– Access controls and permissions
– Parameter limits and boundary conditions
– Consistency across different protocol states
The re-audit did not uncover any critical or high-severity vulnerabilities in the lending logic. Instead, Halborn flagged five issues:
– One medium-risk finding
– Two low-risk findings
– Two informational observations
According to the audit report, Ripple either fixed, accepted, or acknowledged all identified issues. The medium-risk item involved a scenario where accrued interest on loans could potentially cause a vault to exceed its configured maximum asset limit. Ripple implemented corrections for this, and also addressed a low-risk problem related to a missing freeze check in certain operations.
While the audit reduces the likelihood of major technical flaws, it does not eliminate other forms of risk, such as:
– Borrower default and credit risk
– Underwriting and model risk
– Liquidity and duration mismatch
– Operational and implementation risk at the application level
Still, clearing this technical review is a critical prerequisite for validators who want assurance that the underlying code is mature enough for production deployment.
Testing on the Lending DevNet
In parallel with the voting and audit processes, developers have begun experimenting with possible use cases on the XRPL Lending DevNet. This dedicated environment allows teams to:
– Integrate vaults and lending flows into their applications
– Simulate loan origination and repayment cycles
– Test different risk-sharing configurations
– Explore user experience and institutional workflow design
One early example is the yield-focused protocol SOIL, which has indicated plans to be among the first applications built around the new lending features once they are approved. Projects like this aim to turn the abstract protocol changes of XLS-65 and XLS-66 into concrete products that end users and institutions can interact with.
How this could change the XRPL ecosystem
If activated, XLS-65 and XLS-66 would represent one of the most significant functional expansions of XRPL in recent years. Potential impacts include:
– New yield opportunities: Holders of XRP, RLUSD, and other tokens could gain access to on-ledger yield products by depositing into vaults that participate in institutional lending.
– Institutional credit markets: Regulated lenders could originate and manage loans using XRPL as a transparent, verifiable accounting layer, while still relying on their own compliance and risk frameworks.
– Composability for builders: Developers would gain standardized primitives-vaults and lending positions-that can be integrated into trading, asset management, and structured finance apps.
– Enhanced liquidity: Aggregating assets in vaults and deploying them into loans could deepen liquidity and support more sophisticated financial products on XRPL.
Differences from typical DeFi lending models
Compared with widely used DeFi platforms, the XLS-65/66 design makes several deliberate trade-offs:
– Less anonymity, more due diligence: Borrowers are expected to be known entities vetted off-chain, rather than pseudonymous addresses.
– Lower or no overcollateralization: Rather than demanding collateral greater than the loan value, risk is managed via credit assessments and first-loss capital structures.
– Fixed terms vs. flexible pools: The focus on fixed-term lending contrasts with many variable-rate, pool-based markets in DeFi.
– Regulatory alignment: Instead of trying to avoid the traditional regulatory perimeter, the model assumes participants will remain subject to it.
This makes the system less “permissionless” than some DeFi options, but potentially far more attractive to banks, payment companies, and institutional lenders that must operate within regulated environments.
What validators and users should watch next
In the coming weeks and months, several developments will determine whether and when XLS-65 and XLS-66 become active on mainnet:
– Validator sentiment: Support levels must rise significantly from the current ~40%/37% toward the 80%+ threshold and then be sustained for two full weeks.
– Additional reviews or revisions: Feedback from validators, developers, or early testers could trigger minor updates before full activation.
– Ecosystem readiness: The more applications and institutions prepare to use the lending features from day one, the more compelling the case for activation becomes.
For XRPL users, the key implications will revolve around new ways to deploy capital, changing risk profiles, and the emergence of on-ledger credit markets that operate under institutional standards rather than purely automated collateral rules.
Strategic significance for Ripple and XRPL
Ripple’s backing of the amendments underscores a broader strategic direction: positioning the XRP Ledger not only as a fast payment network, but also as a foundation for institutional finance infrastructure. Native vaults and lending primitives expand the protocol’s role from simple value transfer to more complex financial intermediation, while still avoiding the full generality-and complexity-of smart contract platforms.
If validators ultimately approve XLS-65 and XLS-66, XRPL could become a competitive venue for regulated lending, structured yield products, and tokenized credit instruments, bridging the gap between traditional finance workflows and on-chain settlement.