Skip to content
Open for votingTier BDeFi & DEX

LendingProtocolV1_1 XLS-66

Closed vaults with fixed schedules and payment-based interest accounting extend the lending protocol. LendingProtocolV1_1 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?

An open vault has no fixed subscription or redemption window, while loans have fixed terms. A closed vault gives the operator a fixed capital base for that term and depositors a schedule known in advance. Withdrawal still depends on available liquidity and the vault's rules.

How does the mechanism work?

VaultCreate sets immutable VaultKind, SubscriptionDate, and RedemptionDate fields; ledger time determines the phase. Closed vaults accept deposits only during subscription, block withdrawals during investment, and permit LoanSet only during investment. New vaults carry LEVersion for cash-basis accounting: origination adds principal to DebtTotal without recognizing scheduled interest in AssetsTotal; payments reduce principal debt and add paid interest to AssetsTotal.

What changes compared with the predecessor?

BeforeAfter
Vaults were open, with no fixed deposit or withdrawal windows. All scheduled loan interest was recorded as vault income when the loan was originated.New LoanBrokers can be created only for closed vaults with fixed schedules. Newly created vaults record interest only when paid, while existing vaults and previously created LoanBrokers continue under their earlier rules.

Who is this change relevant to?

XRP holders and users

A depositor in a closed vault can exit during the subscription phase and then only from the redemption date onward. Late or defaulted loans do not postpone the redemption phase; they reduce the amount available for withdrawal.

Wallets and app developers

Apps derive the vault type and current phase from date fields and ledger time, enabling or disabling deposits and withdrawals accordingly.

Exchanges and issuers

Lending providers link new programs to closed vaults and schedule loan terms so the final installment falls due with a buffer before the redemption date.

Node operators

Nodes determine the vault phase from the previous ledger's close time and apply either the earlier accounting model or payment-based accounting according to LEVersion.

What limitations and risks remain?

  • The schedule and vault type cannot be changed after creation.
  • Deposits and withdrawals are blocked during the investment phase.
  • Loans remain unsecured. Credit assessment and lending decisions remain off-ledger.
  • The closed-ended vault extension is documented as XLS-65.1.4 and remains marked Draft.
Technical details: transactions, fields, codes and invariants

Transactions

  • VaultCreate
  • VaultDeposit
  • VaultWithdraw
  • VaultDelete
  • LoanBrokerSet
  • LoanSet

Ledger objects

  • Vault
  • LoanBroker
  • Loan

Fields and flags

  • VaultKind
  • SubscriptionDate
  • RedemptionDate
  • LEVersion
  • MemoData (VaultDelete, 1 to 256 bytes)

API methods

  • vault_info
  • ledger_entry

Result codes

  • tecNO_PERMISSION
  • tecTOO_SOON
  • temMALFORMED

Invariants

  • VaultKind, SubscriptionDate, RedemptionDate, and LEVersion remain unchanged after a vault is created.

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?

LendingProtocolV1_1 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