Skip to content
Open for votingTier ADeFi & DEX

SingleAssetVault XLS-65

A Single Asset Vault pools one asset from multiple depositors in a ledger object. SingleAssetVault is open for Mainnet voting but is not enabled yet. The latest response reports support from 23 of 35 tracked validators.

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

Status
Open for voting
XLS
XLS-65
Enabled
Not enabled

What is the current Mainnet vote?

23 of 35 yes votes; minimum: 29 (current 65%; support >80%)

What does this amendment change?

Why does this amendment exist?

Multiple depositors should be able to provide a single asset in a shared ledger pool represented by shares.

How does the mechanism work?

A vault holds exactly one asset in its pseudo-account and issues MPT shares. The first deposit uses Scale; later deposits mint shares from the ratio of AssetsTotal to the share issuance's OutstandingAmount. Withdrawals burn shares and account for LossUnrealized when pricing redemptions. Private vaults control deposits through a permissioned domain.

What changes compared with the predecessor?

BeforeAfter
There was no general native object for a share-based pool of XRP, IOUs, or MPTs that other protocols could use as a capital source.Multiple depositors can pool one asset, hold shares, and redeem available funds under a defined withdrawal policy.

Who is this change relevant to?

XRP holders and users

Depositors exchange their asset for vault shares. The redemption value can exceed or fall below the original deposit because of protocol outcomes, rounding, and LossUnrealized.

Wallets and app developers

Apps must show the share price, AssetsAvailable, AssetsTotal, loss status, domain access, and the differences between XRP, IOUs, and integer MPTs.

Exchanges and issuers

Vault owners define the asset, capacity, metadata, private status, and share transferability. They cannot arbitrarily block shareholders' withdrawals outside the protocol's withdrawal conditions.

Node operators

Nodes manage the vault pseudo-account, share issuance, and asset accounting. VaultCreate creates several linked ledger objects atomically.

What limitations and risks remain?

  • A vault holds exactly one asset.
  • The first version supports only First Come, First Serve as its WithdrawalPolicy.
  • Private deposits require valid domain credentials unless the depositor is the vault owner, who is implicitly authorized. Shareholders can withdraw without domain membership so access changes cannot trap their funds; closed-vault extensions still impose their schedule restrictions.
  • Nontransferable shares can be redeemed but cannot be sent to other accounts.
  • For MPT assets, Scale is fixed at zero. Values that cannot be represented as integers may be lost through rounding.
  • A frozen vault asset cannot be deposited. Withdrawals are then allowed only to the issuer.
  • The specification lists vault and transaction invariants, with separate rules for SingleAssetVault, LendingProtocolV1_1, and fixCleanup3_4_0. Apps must distinguish those versions when checking accounting and lifecycle conditions.

What fee and performance figures does the specification provide?

  • VaultCreate burns one owner reserve because the transaction creates a pseudo-account.
  • VaultDeposit, VaultWithdraw, and internal protocol movements do not charge issuer TransferFee.
Technical details: transactions, fields, codes and invariants

Transactions

  • VaultCreate (type 65)
  • VaultSet (type 66)
  • VaultDelete (type 67)
  • VaultDeposit (type 68)
  • VaultWithdraw (type 69)
  • VaultClawback (type 70)
  • Payment

Ledger objects

  • Vault (0x0084)
  • AccountRoot of the pseudo-account
  • MPTokenIssuance for shares
  • MPToken

Fields and flags

  • Asset
  • AssetsTotal / AssetsAvailable / AssetsMaximum
  • LossUnrealized
  • ShareMPTID
  • Scale
  • WithdrawalPolicy
  • DomainID
  • tfVaultPrivate 0x00010000
  • tfVaultShareNonTransferable 0x00020000
  • vaultStrategyFirstComeFirstServe 0x0001

API methods

  • vault_info

What does a concrete workflow look like?

A public XRP vault accepts a deposit and mints shares for it. If a lending protocol later uses some of the XRP, AssetsAvailable shows only the portion immediately available for withdrawal.

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?

SingleAssetVault is open for Mainnet voting but is not enabled yet. The latest response reports support from 23 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