Skip to content
Open for votingTier ADeFi & DEX

LendingProtocol XLS-66

The XRPL lending protocol represents fixed-term, unsecured loans funded by vault pools. LendingProtocol is open for Mainnet voting but is not enabled yet. The latest response reports support from 22 of 35 tracked validators.

Sources reviewed Oct 5, 2026 · English page updated Oct 5, 2026 · Phil · CryptoTuts founder

Status
Open for voting
XLS
XLS-66
Enabled
Not enabled

What is the current Mainnet vote?

22 of 35 yes votes; minimum: 29 (current 62%; support >80%)

What does this amendment change?

Why does this amendment exist?

Capital from a shared vault is intended to be lent and repaid through defined on-ledger loan objects.

How does the mechanism work?

A LoanBroker connects a Single Asset Vault to individual fixed-rate Loan objects. LoanSet atomically creates a loan with the broker's and borrower's consent, disburses principal, and records the repayment schedule, fees, and due dates in the ledger. LoanPay, LoanManage, and cover transactions manage repayments, impairments, defaults, and first-loss capital.

What changes compared with the predecessor?

BeforeAfter
A vault pooled assets and shares but had no loan agreement, repayment schedule, broker fees, or default status.Fixed-term, unsecured loans are disbursed from vault liquidity as separate ledger objects and repaid under defined rules.

Who is this change relevant to?

XRP holders and users

Vault depositors voluntarily provide capital for unsecured loans. Defaults and impairments can reduce the value of their vault shares.

Wallets and app developers

Apps must read the broker, vault, loan status, due dates, rounding, and payment types from stored ledger values. Formulas alone do not establish a current balance.

Exchanges and issuers

Brokers are responsible for off-ledger assessment, lending decisions, fees, and default management. First-loss capital limits risks but does not replace underwriting.

Node operators

Nodes deterministically execute repayment calculations, precision checks, status changes, and accounting between the borrower, broker pseudo-account, and vault.

What limitations and risks remain?

  • Loans are unsecured. There is no on-ledger collateral or automatic liquidation.
  • Credit assessment, identity checks, and lending decisions remain off-ledger.
  • The protocol represents fixed-schedule amortizing loans, not a variable interest-rate curve.
  • Participants must trust the LoanBroker and its off-ledger processes.
  • Asset precision can make terms invalid. MPTs allow only whole units, and payments are rounded under the specification's rules.
  • A loan can be marked as defaulted only after its due time and GracePeriod have elapsed.
  • The transaction invariants marked TBD in the specification are not asserted here as finalized rules.

What fee and performance figures does the specification provide?

  • LoanSet requires the borrower's reserve for the Loan object.
  • First-loss capital must cover at least DebtTotal multiplied by CoverRateMinimum.
Technical details: transactions, fields, codes and invariants

Transactions

  • LoanBrokerSet (type 74)
  • LoanBrokerDelete (type 75)
  • LoanBrokerCoverDeposit (type 76)
  • LoanBrokerCoverWithdraw (type 77)
  • LoanBrokerCoverClawback (type 78)
  • LoanSet (type 80)
  • LoanDelete (type 81)
  • LoanManage (type 82)
  • LoanPay (type 84)

Ledger objects

  • LoanBroker (0x0088)
  • Loan
  • Vault
  • AccountRoot of pseudo-accounts

Fields and flags

  • VaultID / LoanBrokerID / LoanID
  • PrincipalRequested
  • InterestRate / LateInterestRate / CloseInterestRate
  • PaymentTotal / PaymentInterval / GracePeriod
  • Counterparty / CounterpartySignature
  • DebtTotal / DebtMaximum
  • CoverAvailable / CoverRateMinimum
  • tfLoanDefault 0x00010000
  • tfLoanImpair 0x00020000
  • tfLoanUnimpair 0x00040000
  • tfLoanFullPayment 0x00020000

Result codes

  • temBAD_SIGNER
  • temINVALID
  • temINVALID_FLAG
  • tecNO_ENTRY
  • tecNO_PERMISSION
  • tecINSUFFICIENT_FUNDS
  • tecINSUFFICIENT_PAYMENT
  • tecLIMIT_EXCEEDED
  • tecPRECISION_LOSS
  • tecTOO_SOON
  • tecEXPIRED
  • tecFROZEN / tecLOCKED

What does a concrete workflow look like?

The broker and borrower sign the same LoanSet terms. The ledger disburses funds from the vault, creates the repayment schedule, and accepts later installments only through LoanPay.

How does this amendment relate to others?

Every direct relationship has a type, an explanation and a primary source.

What happens next for this amendment?

LendingProtocol is open for Mainnet voting but is not enabled yet. The latest response reports support from 22 of 35 tracked validators.

Activation requires support strictly above 80 percent for two uninterrupted weeks. A reported raw cutoff is not the minimum yes-vote count: with 35 tracked validators and a cutoff of 28, at least 29 yes votes are required.

Where does it sit within its amendment family?

Vaults and Lending: protocol progression

  1. DeletableAccountsEnabled · from rippled 1.4.0
  2. TicketBatchEnabled · from rippled 1.7.0
  3. DisallowIncomingEnabled · from rippled 1.10.0
  4. fixDisallowIncomingV1Enabled · from rippled 2.0.0
  5. PermissionedDEXEnabled · from rippled 2.5.0
  6. PermissionDelegationDeprecated · from rippled 2.5.0
  7. LendingProtocolOpen for voting · from rippled 3.1.0
  8. SingleAssetVaultOpen for voting · from rippled 3.1.0
  9. fixCleanup3_1_3Enabled · from rippled 3.1.3
  10. fixCleanup3_2_0Enabled · from xrpld 3.2.0
  11. SponsorOpen for voting · from xrpld 3.3.0
  12. PermissionDelegationV1_1Enabled · from xrpld 3.3.0
  13. fixCleanup3_3_0Enabled · from xrpld 3.3.0
  14. LendingProtocolV1_1Open for voting · from xrpld 3.4.0
  15. fixCleanup3_4_0Enabled · from xrpld 3.4.0

Which primary sources support this information?

← All XRPL amendments and XLS specifications