Not a network amendmentTier BUpcoming standardsSpec: Draft
WASMVM XLS-102
The draft defines the deterministic WebAssembly runtime, gas rules, and host functions for XRPL extensions. This is a proposal, not an active network feature. Whether any part of it will launch, and when, remains open.
Sources reviewed Oct 5, 2026 · English page updated Oct 5, 2026 · Phil · CryptoTuts founder
- Network status
- Not a network amendment
- XLS
- XLS-102
- Spec status
- Draft
- Spec revision
- Sep 3, 2026
What does this XLS propose?
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
- no new transaction types; initial execution through EscrowFinish
Ledger objects
- Escrow as the first host object
- FeeSettings for limits subject to voting
Fields and flags
- Gas / GasLimit / GasPrice
- BytecodeSizeLimit
- linear WASM memory pages of 64 KiB
- set_data as the only host function that writes ledger data in the initial scope
API methods
- ldgr_index / parent_ldgr_time / parent_ldgr_hash
- home_le_field / home_le_inner
- cache_le / le_field / le_inner
- transaction, keylet, NFT, and trace host functions
Invariants
- The same inputs must produce the same gas consumption and result on every node.
- Each execution starts in a new VM instance without reusing memory state.
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?
WASMVM has no amendment family with other members on this site, so there is no progression to show here.