XRPL Lending Amendments Gain Validator Support

The XRP Ledger’s proposed lending infrastructure has gained additional validator support, but the system remains short of the threshold required for mainnet activation. As of November 12, LendingProtocol and LendingProtocolV1_1 each had 22 affirmative votes among 35 validators tracked on the current trusted list, while SingleAssetVault had 23. None of the three amendments has yet entered its required two-week majority period. XRPLDashboard’s November 12 amendment snapshot shows the lending amendments seven votes short and the vault amendment six votes short.

XRPL requires an amendment to receive support from strictly more than 80% of trusted validators and maintain that majority continuously for two weeks before becoming enabled. With 35 validators currently counted, that means 29 affirmative votes. Reaching 29 votes would begin the activation window rather than immediately switch lending on. If support falls back to 28 or fewer during that period, the majority is lost and the 14-day clock must start again after support recovers.

Lending Moves Credit Risk Offchain

The proposed system combines Single Asset Vaults with a lending primitive for fixed-term, uncollateralized loans. Depositors supply XRP or supported tokens to a vault, while a Loan Broker originates and manages loans using those pooled assets. Borrower credit assessment and underwriting remain offchain rather than being enforced through automated onchain collateral and liquidation. XRPL’s official Lending Protocol documentation describes the architecture as an onchain credit-origination primitive rather than a conventional collateralized DeFi money market.

Loan Brokers can also provide first-loss capital that absorbs part of a default before losses reach vault depositors. That protection is configurable and does not eliminate credit risk. The design therefore shifts significant responsibility toward the broker’s underwriting, loan management and capital configuration. XRPL separately documents institutional credit facilities using permissioned access and KYB controls, while Ripple has illustrated a potential use case in which a payment provider borrows short-term working capital while cross-border settlement is pending.

The lending stack fits a broader expansion of financial primitives on XRPL. The network has already added coordinated transaction functionality through Batch V1.1, while regulated infrastructure provider CSD BR is mirroring BTG Pactual fund records on XRPL. Those deployments demonstrate separate capabilities and should not be treated as evidence that the lending protocol itself is already operational.

LendingProtocolV1_2 Remains Under Development

Development is continuing while validators consider the current amendments. An open standards proposal for LendingProtocolV1_2 would replace the existing custom counterparty-signature process for creating loans with a two-step structure. A broker would first submit LoanSet, reserving the required vault assets, and the borrower would then accept through a separate LoanAccept transaction. The proposed change is intended to make borrowing compatible with wallets and custodians that do not support XRPL’s custom dual-signature lending flow.

The network has meanwhile already activated fixCleanup3_4_0, a broader amendment bundle that includes corrections for Single Asset Vaults and the Lending Protocol alongside fixes affecting permissioned trading, trust lines, NFTs, escrow and other features. The amendment became effective on November 4. Its activation fixes underlying protocol behavior but does not itself activate lending or vaults on Mainnet.

Institutional-facing XRPL infrastructure is also developing through other channels. CSD BR’s fund-record deployment is already live, while programmable wallets from Ripple and Privy support XRP and RLUSD payment workflows and EURØP operates on XRPL as part of a multichain regulated euro stablecoin strategy. These developments expand XRPL’s institutional tooling without changing the validator requirements governing the lending amendments.

Separately, XRPL Testnet and Devnet are scheduled to reset on November 25 because of full-history server stability issues. The operation will delete accounts, transactions, balances and other existing test-network state, while Mainnet remains unaffected. The immediate milestone for lending remains validator consensus, not the test-network reset: LendingProtocol, LendingProtocolV1_1 and SingleAssetVault still need to cross and sustain the amendment threshold before the current lending architecture can become active on Mainnet.