Skip to content
EnabledTier APayments

Escrow

XRPL escrows lock XRP until a specified time or cryptographic condition. Escrow is enabled on the XRP Ledger. xrpscan reports Mar 31, 2017 (UTC) as its activation date and rippled 0.60.0 as its first version.

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

Status
Enabled
XLS
No separate XLS
Enabled
Mar 31, 2017 (UTC)

What does this amendment change?

Why does this amendment exist?

XRP payments needed to be lockable by time or condition without a third-party custodian controlling the funds.

How does the mechanism work?

Escrow replaces SusPay and uses dedicated ledger entries and transactions to create, finish, and cancel escrows. Release can be time-based or tied to a supported crypto-condition.

What changes compared with the predecessor?

BeforeAfter
The older SusPay and CryptoConditions amendments did not provide the later escrow workflow as a permanently supported combination.EscrowCreate locks XRP in a ledger object. EscrowFinish or EscrowCancel releases the amount under the specified rules.

Who is this change relevant to?

XRP holders and users

Locked XRP remains unavailable until a valid release or cancellation.

Wallets and app developers

Apps must correctly represent ledger time, optional crypto-conditions, and both ways to end the escrow.

Exchanges and issuers

The original amendment locks only XRP. Token support is added by TokenEscrow.

What limitations and risks remain?

  • The base amendment supports XRP, not arbitrary trust line tokens or MPTs.
  • Timestamps use ledger time rather than the local device's clock.
Technical details: transactions, fields, codes and invariants

Transactions

  • EscrowCreate
  • EscrowFinish
  • EscrowCancel

Ledger objects

  • Escrow

Fields and flags

  • Condition
  • Fulfillment
  • FinishAfter
  • CancelAfter

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?

Escrow is enabled on the XRP Ledger. xrpscan reports Mar 31, 2017 (UTC) as its activation date and rippled 0.60.0 as its first version.

These rules are already part of Mainnet. Server operators need a compatible xrpld (formerly rippled) version; ordinary wallet users do not need to enable anything manually.

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