RippleX has opened validator voting for LendingProtocolV1_1, a technical amendment that must activate before the XRP Ledger’s broader native lending stack can proceed. According to RippleX’s official Lending Protocol V1.1 documentation, the amendment adds closed-ended vaults and cash-basis accounting to the architecture defined by XLS-65 and XLS-66. The vote does not make lending live on XRPL; it advances one prerequisite for the eventual activation of the lending protocol and single-asset vaults.
The amendment entered the reference server in xrpld 3.4.0, released September 16, and RippleX said on September 30 that it was open for validator voting. XRPL amendments need support from at least 80% of trusted validators for two consecutive weeks before activation, so opening the vote starts a consensus process rather than setting a fixed mainnet date.
Closed-Ended Vaults Change How XRPL Lending Works
LendingProtocolV1_1 creates closed-ended vaults with three predetermined phases: subscription, investment and redemption. Depositors can add or withdraw assets during subscription; funds are locked for lending during investment; and withdrawals reopen during redemption after loans mature. The fixed lifecycle prevents new capital from entering midway through a lending period and restricts new loans to the investment phase.
The second major change is accounting. The original design recognized the full scheduled interest from a loan when it was originated, even before the borrower paid it. Under V1.1, new vaults use cash-basis accounting, meaning interest enters vault income only when a payment actually delivers it. That keeps AssetsTotal and vault share values tied more closely to realized income rather than expected future payments. Vaults created under the earlier accounting model retain that treatment permanently.
The underlying Lending Protocol is designed for fixed-term, uncollateralized loans funded from pooled single-asset vaults. Credit underwriting remains off-chain, while loan creation, repayment, impairment and default management are represented on the ledger. Loan brokers can also supply optional first-loss capital to absorb part of a default. This is therefore not an automated overcollateralized lending system like many DeFi money markets; borrower assessment remains an external risk-management function.
Mainnet Lending Still Depends on Multiple Amendments
RippleX has made the activation sequence explicit: LendingProtocolV1_1 must activate before the separate LendingProtocol and SingleAssetVault amendments can proceed. That means validator approval of V1.1 alone would still not launch native XRPL lending. The broader stack needs the vault primitive, the lending engine and the V1.1 rules that govern closed-ended lending and cash-basis accounting.
The work fits a wider push toward institutional credit and tokenized finance on XRPL. Ripple has expanded tokenization infrastructure through investments in ZILO and Licuido, while Aviva Investors has launched a tokenized liquidity fund share class on XRPL. RippleX’s Singapore infrastructure program is also targeting credit, financing, collateral and liquidity applications. Those initiatives provide potential use cases for native lending infrastructure, but they do not demonstrate demand for a feature that is not yet active.
For now, the network is still in governance mode rather than lending mode. Validators are deciding whether the revised accounting and closed-ended vault design should become part of XRPL’s consensus rules, while the lending engine itself remains dependent on the rest of the amendment sequence. The vote moves native credit infrastructure closer to production, but the gap between an approved protocol primitive and a functioning mainnet lending market still matters.