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
- Version
- rippled 3.1.0
- Enabled
- Not enabled
What does this amendment change?
What changes compared with the predecessor?
Who is this change relevant to?
What limitations and risks remain?
What fee and performance figures does the specification provide?
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?
How does this amendment relate to others?
Every direct relationship has a type, an explanation and a primary source.