Skip to content
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 problem is the proposal intended to solve?

Without a shared structure, the free-form Data field does not identify a vault's purpose or where reliable operator information can be found. Applications would otherwise need to maintain that mapping separately.

How is the mechanism designed in the current draft?

A participating vault stores a compact JSON object in Data. The n key specifies the display name and w an operator or fund website; the convention recommends both values. VaultSet can update them later without prohibiting other free-form uses of Data.

How settled is the proposal?

This is a proposed ecosystem convention, not a network feature. It needs no protocol change; whether applications adopt it remains open.

What changes compared with the predecessor?

BeforeAfter
Vault.Data was a free-form byte field without a shared machine-readable meaning.Participating vaults could publish a name and website in a small JSON object with a consistent format.

Who is this change relevant to?

XRP holders and users

Users could identify vaults more easily. A displayed name or link proves neither operator identity nor trustworthiness.

Wallets and app developers

Explorers should parse JSON defensively, sanitize output, and tolerate unknown keys. Historical changes may matter for audits.

Exchanges and issuers

Vault operators can publish a readable name and context link but should not store sensitive information there.

Node operators

Nodes gain no new execution logic. They continue enforcing only the existing 256-byte limit for Vault.Data.

What limitations and risks remain?

  • XLS-98 is a voluntary ecosystem draft, not a network amendment.
  • The ledger does not check whether the JSON follows this convention.
  • The website is not cryptographically verified and is not proof of ownership.
  • All information is public and can be changed through VaultSet.
  • The entire Data field remains limited to 256 bytes.
  • Applications must sanitize content before rendering names or URLs.
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?

A hypothetical vault stores {"n":"USD Credit Vault","w":"example.org"}. An explorer displays the name while continuing to mark the website as an unverified statement by the operator.

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?

This is a proposed ecosystem convention, not a network feature. It needs no protocol change; whether applications adopt it remains open.

The draft needs further technical development and may still change fundamentally or be abandoned. As an ecosystem convention it needs no xrpld (formerly rippled) amendment and no network vote; it builds on SingleAssetVault, so it can only be used where that amendment is enabled.

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.

Which primary sources support this information?

← All XRPL amendments and XLS specifications