Skip to content
In developmentTier APayments

SmartEscrow XLS-100

WebAssembly functions are intended to enable programmable escrow release rules. SmartEscrow is listed by xrpl.org as in development and is not yet listed for Mainnet voting. A stable xrpld (formerly rippled) release and validator voting are still required.

Sources reviewed Oct 5, 2026 · English page updated Oct 5, 2026 · Phil · CryptoTuts founder

Status
In development
XLS
XLS-100
Version
Not released
Enabled
Not enabled

What is the development status?

Why is this feature being developed?

Timestamps and standardized crypto-conditions do not cover every desired escrow release rule.

How is the mechanism intended to work?

EscrowCreate can immutably bind compiled WASM bytecode and local data storage to the escrow object. EscrowFinish runs the exported escrow_finish function under a gas limit and releases funds only if it returns a positive int32. Code may read ledger data but cannot modify ledger objects other than its own Data field or generate transactions.

What is still required before Mainnet?

After implementation and testing, the change must appear in a stable xrpld (formerly rippled) release before Mainnet voting can begin.

What changes compared with the predecessor?

BeforeAfter
Escrows could combine only time constraints and a PREIMAGE-SHA-256 crypto-condition as release rules.The proposed extension lets an escrow additionally check a bounded programmable condition, such as credential, notary, or oracle rules.

Who is this change relevant to?

XRP holders and users

Users could use more complex releases but must check code and expiration before locking funds. A faulty contract leaves funds locked until cancellation is permitted.

Wallets and app developers

Developers compile WASM against a precisely defined ABI, estimate gas, and handle traps, negative return values, and insufficient gas as failed releases.

Exchanges and issuers

Businesses could attach notary, compliance, or oracle conditions directly to escrows. Token support additionally depends on TokenEscrow.

Node operators

All validators execute the same bytecode deterministically. FeeSettings limits code size, gas, and pricing so the UNL can adjust resource consumption.

What limitations and risks remain?

  • This amendment is a draft, not a Mainnet feature.
  • WASM engine and API details are defined separately in XLS-102.
  • Bytecode and release conditions cannot be updated after EscrowCreate.
  • An ordinary transaction cannot change Data; only the escrow's own bytecode can do so.
  • Code cannot write to other ledger objects or generate transactions.
  • Every Smart Escrow requires CancelAfter as an exit path.
  • All nodes and validators must execute the bytecode.
  • SmartEscrow does not turn the XRPL into a general-purpose smart contract platform.
  • The specification has not finalized the exact EscrowFinish fee.

What fee and performance figures does the specification provide?

  • According to the draft, EscrowCreate with bytecode costs 100 drops plus 5 drops per byte of bytecode.
  • The first 500 bytes are covered by the first object reserve. Each additional 500 bytes requires another object reserve.
  • Draft initial values are 100,000 gas, a BytecodeSizeLimit of 100,000 bytes, and 1,000 micro-drops per gas. The UNL can change these values through fee voting.
Technical details: transactions, fields, codes and invariants

Transactions

  • EscrowCreate
  • EscrowFinish
  • SetFee

Ledger objects

  • Escrow (0x0075)
  • FeeSettings

Fields and flags

  • Bytecode
  • Data (at most 4 KB under the execution model)
  • Gas
  • GasUsed
  • VMReturnCode
  • GasLimit
  • BytecodeSizeLimit
  • GasPrice
  • CancelAfter

Result codes

  • temMALFORMED
  • temBAD_EXPIRATION
  • temINVALID_BYTECODE
  • temTEMP_DISABLED
  • tefNO_BYTECODE
  • tefBYTECODE_NOT_INCLUDED
  • tecBYTECODE_REJECTED

Invariants

  • Every escrow with bytecode must have CancelAfter.

What does a concrete workflow look like?

In the proposed workflow, an escrow contains a notary address in its bytecode. EscrowFinish reads the triggering transaction and returns a positive value only when the specified account initiates release.

How does this amendment relate to others?

Every direct relationship has a type, an explanation and a primary source.

What happens next for this amendment?

SmartEscrow is listed by xrpl.org as in development and is not yet listed for Mainnet voting. A stable xrpld (formerly rippled) release and validator voting are still required.

After implementation and testing, the change must appear in a stable xrpld release before Mainnet voting can begin.

Where does it sit within its amendment family?

Escrow and Payment Channels: protocol progression

  1. PayChanEnabled · from rippled 0.33.0
  2. CryptoConditionsEnabled · from rippled 0.50.0
  3. EscrowEnabled · from rippled 0.60.0
  4. fix1512Enabled · from rippled 0.80.0
  5. fix1523Enabled · from rippled 0.80.0
  6. fix1571Enabled · from rippled 1.0.0
  7. fixPayChanRecipientOwnerDirEnabled · from rippled 1.4.0
  8. PriceOracleEnabled · from rippled 2.2.0
  9. TokenEscrowEnabled · from rippled 2.5.0
  10. fixPayChanCancelAfterEnabled · from rippled 2.5.0
  11. fixIncludeKeyletFieldsEnabled · from rippled 3.0.0
  12. fixPriceOracleOrderEnabled · from rippled 3.0.0
  13. SmartEscrowIn development

Which primary sources support this information?

← All XRPL amendments and XLS specifications