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?
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
- 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?
How does this amendment relate to others?
Every direct relationship has a type, an explanation and a primary source.