Definition and scope
How the XRPL Lending Protocol Works addresses a distinct part of compliance, identity, and interoperability. Introduce vault-backed credit mechanics while verifying current amendment and network availability.
XRPL includes tools for controlled deposits, issuer compliance, public identity, and cross-network systems. Several features in this category are amendment-dependent or evolving, so every eventual article must verify current Mainnet status and distinguish protocol capability from a particular service's legal obligations. Protocol controls can support a policy but do not establish identity, trustworthiness, regulatory compliance, or legal permission by themselves.
How it works
The proposed LendingProtocol uses Single Asset Vault liquidity, LoanBroker entries, on-ledger fixed-term uncollateralized loans, repayments, first-loss capital, and off-ledger underwriting and risk management.
- LendingProtocol: verify this field, object, or component against the cited protocol documentation.
- LoanBroker: verify this field, object, or component against the cited protocol documentation.
- Single Asset Vault: verify this field, object, or component against the cited protocol documentation.
- first-loss capital: verify this field, object, or component against the cited protocol documentation.
- underwriting: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
On an enabled development network, a team can create a vault and loan broker, model first-loss coverage, originate a test loan, process payments, and exercise grace and default paths.
For production use, preserve the exact signed or queried data, record the network and validated ledger reference, and compare the result with the current primary documentation before changing off-ledger state.
Open the related live demo or evidence lab →Limits, risks, and common confusion
LendingProtocol and SingleAssetVault were not enabled on XRPL Mainnet at review time. The design does not provide automated collateral liquidation, creditworthiness, guaranteed repayment, or legal compliance.
Protocol controls can support a policy but do not establish identity, trustworthiness, regulatory compliance, or legal permission by themselves.
Current network status
Not enabled on XRPL Mainnet. Official public-server feature responses showed LendingProtocol supported but not enabled on Mainnet at review time. Documentation describes protocol design, not a live Mainnet lending product.
Status reviewed 2026-08-23. Amendment-dependent behavior must be rechecked against the network's live feature state before operational use.