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

SmartEscrow covers specific release conditions but not general contract logic with persistent state. New DeFi protocols or complex bridge logic currently lack a native programmable execution layer.

How is the mechanism designed in the current draft?

ContractCreate creates a pseudo-account, a Contract object, and, for new bytecode, a reusable ContractSource object. ContractCall invokes a named WASM function with parameters; code may modify associated ContractData and process embedded XRPL transactions within ContractCall. ContractModify, ContractDelete, ContractUserDelete, and ContractClawback govern updates, deletion, user data, and issuer rights.

How settled is the proposal?

This is a proposal, not an active network feature. Whether any part of it will launch, and when, remains open.

What changes compared with the predecessor?

BeforeAfter
The XRPL provides specialized transaction types but no general stateful contract with freely defined functions.A contract could hold WASM code, instance parameters, and its own ledger state in a secured pseudo-account and initiate native XRPL transactions.

Who is this change relevant to?

XRP holders and users

Users could access new applications directly on the XRPL. Assets sent to a contract remain exposed to its code and possible fraud risks.

Wallets and app developers

Developers would need to understand WASM, the ABI, gas, ContractData, events, and embedded transaction results. Reusing ContractSource code reduces storage requirements but does not replace an audit.

Exchanges and issuers

Issuers could use programmable financial logic and enforce their token rights through ContractClawback. Compliance and contract review remain organizational responsibilities.

Node operators

All validators would need to execute bytecode, state changes, and initiated transactions deterministically within hard resource limits.

What limitations and risks remain?

  • XLS-101 is an early draft with explicit open questions, not a network feature.
  • The fee model has no final values yet. Treatment of gas fees is also unresolved.
  • How reserves for user-specific ContractData objects are allocated has not been decided.
  • The draft identifies reentrancy as an unresolved security area.
  • Contract code may be fraudulent or faulty. The ledger does not assess its economic safety.
  • ContractData and Contract block AccountDelete until the associated objects have been removed in an orderly way.
  • The intended placement of URI and several serialization details remain open issues.

What fee and performance figures does the specification provide?

  • ContractCreate is intended to cost at least approximately one object reserve as a nonrefundable fee, plus bytecode and init-execution costs.
  • Instruction pricing, the maximum instruction count, and memory limits are intended to be adjustable through UNL fee voting. The draft provides no specific initial values.
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?

In the proposed workflow, a DeFi contract is deployed once through ContractCreate. A user invokes a function through ContractCall; the contract updates ContractData and initiates a native Payment transaction within the same processing flow.

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 proposal, not an active network feature. Whether any part of it will launch, and when, remains open.

The draft needs further technical development and may still change fundamentally or be abandoned. Only a corresponding xrpld (formerly rippled) amendment would trigger a separate network vote.

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.

Which primary sources support this information?

← All XRPL amendments and XLS specifications