Not a network amendmentTier BUpcoming standardsSpec: Draft
SmartContracts XLS-101
An early draft for native, stateful WASM smart contracts on XRPL pseudo-accounts. 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-101
- Spec status
- Draft
- Spec revision
- Jul 28, 2025
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
- ContractCreate
- ContractCall
- ContractModify
- ContractDelete
- ContractUserDelete
- ContractClawback
Ledger objects
- ContractSource
- Contract
- ContractData
- AccountRoot of the pseudo-account
- FeeSettings
Fields and flags
- ContractCode / ContractHash
- ContractAccount / ContractOwner
- Functions / FunctionName / Parameters
- InstanceParameters / InstanceParameterValues
- ReferenceCount / Data / ParentContractCallId
- tfImmutable / tfCodeImmutable / tfABIImmutable / tfUndeletable
- tfContractSubmittedTxn 0x20000000
API methods
- contract_info
- eventEmitted subscription
- event_history
Invariants
- No ContractSource object may remain with a zero ReferenceCount.
- Every Contract object must reference an existing ContractSource object.
- At most one of lsfImmutable, lsfCodeImmutable, and lsfABIImmutable may be set.
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?
SmartContracts has no amendment family with other members on this site, so there is no progression to show here.