Not a network amendmentTier BUpcoming standardsSpec: Draft
VaultMetadata XLS-98
An optional JSON convention for a Single Asset Vault's name and website in its existing Data field. This is a proposed ecosystem convention, not a network feature. It needs no protocol change; whether applications adopt it remains open.
Sources reviewed Oct 5, 2026 · English page updated Oct 5, 2026 · Phil · CryptoTuts founder
- Network status
- Not a network amendment
- XLS
- XLS-98
- Spec status
- Draft
- Spec revision
- Jan 28, 2026
What does this XLS propose?
What changes compared with the predecessor?
Who is this change relevant to?
What limitations and risks remain?
Technical details: transactions, fields, codes and invariants
Transactions
- VaultCreate
- VaultSet
Ledger objects
- Vault from XLS-65
Fields and flags
- Data (at most 256 bytes)
- n for name
- w for website
- valid JSON object
Invariants
- The convention is optional and does not change protocol validation of Data.
What does a concrete workflow look like?
How does this proposal relate to others?
Every direct relationship has a type, an explanation and a primary source.
What happens next for this proposal?
Where does it sit within its amendment family?
VaultMetadata has no amendment family with other members on this site, so there is no progression to show here.