Where it stands

Smart Escrows get talked about as if they were already here. They are not. Here is where things stand on 2026-11-10.

There is a written plan. The specification is public. It is marked Draft, which means it can still change.

There is code in progress. xrpl.org lists the amendment, named SmartEscrow, as "In Development."

There is a practice network. xrpl.org lists a WASM Devnet where developers can try Smart Escrows with test funds. It is a separate network. Nothing on it touches real XRP.

There is no vote. A change to the XRP Ledger goes to validators only after its code ships in a server release. Then it needs more than 80% of trusted validators for two weeks. Smart Escrows have not reached the first of those steps on Mainnet. Ask a Mainnet server for its list of amendments and SmartEscrow is not there.

There is no date. Nobody can say when, or if, it will be enabled. A draft can be reworked or dropped.

So when you read "Smart Escrows are coming," the accurate version is shorter: a draft exists, and it is being built and tested.

This is also not the same as Hooks. Hooks run on Xahau, a separate network. Smart Escrows are a different design, proposed for the XRP Ledger itself.

Specification status.

XLS-102 states that the WASM engine is gated by the same SmartEscrow amendment.

Amendment status. xrpl.org's Known Amendments page lists SmartEscrow under Amendments in Development, with no target release. Its entry shows status In Development and a default vote of No.

Check Mainnet yourself. Call the feature method on a Mainnet server. On 2026-11-10 the response from xrplcluster.com lists no amendment named SmartEscrow. An amendment a server does not know cannot be voted for by that server.

The path from here, per xrpl.org's amendment process:

1. The code is built into an xrpld release.
2. Validators running that release can vote. Votes are counted at each flag ledger, every 256 ledgers.
3. The amendment must hold more than 80% of trusted validators for two weeks.
4. It is then enabled for all later ledgers.

Smart Escrows are before step 1 on Mainnet.

Test network. xrpl.org's faucet list includes "WASM Devnet," described as a preview of XLS-100 Smart Escrows and other WASM-based programmability. Its WebSocket endpoint is wss://wasm-devnet.dev.ripplex.io:51233. xrpl.org warns that devnets may be reset without warning. Test XRP has no real-world value.

What may still change. The draft marks some items as undecided, including the EscrowFinish fee and some size limits. Field names, costs and result codes quoted here come from the drafts as read on 2026-11-10.

Live status: Amendments page. Background: How amendments happen.