Skip to content
EnabledTier APayments

TokenEscrow XLS-85

Escrows can lock trust line tokens and MPTs as well as XRP. TokenEscrow is enabled on the XRP Ledger. xrpscan reports Feb 12, 2026 (UTC) as its activation date and rippled 2.5.0 as its first version.

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

Status
Enabled
XLS
XLS-85
Enabled
Feb 12, 2026 (UTC)

What does this amendment change?

Why does this amendment exist?

Existing escrow locks XRP. Applications need the same time and condition workflows for fungible tokens too.

How does the mechanism work?

TokenEscrow extends existing escrow transactions to trust line tokens and MPTs. Creation deducts the amount from the sender and stores transfer-rate information; MPT escrows also increase LockedAmount on the holding and issuance. EscrowFinish checks the destination again before delivery. EscrowCancel returns expired escrow funds to the sender and still checks required authorization, but freeze or locking alone does not block cancellation.

What changes compared with the predecessor?

BeforeAfter
EscrowCreate could lock only XRP; issued tokens could not enter the same workflow.Appropriately enabled trust line tokens and MPTs can use the same time and crypto-condition escrow workflows.

Who is this change relevant to?

XRP holders and users

Users can voluntarily lock issued assets by time or condition. While locked, the amount is unavailable as an ordinary balance and is not automatically available to other protocols.

Wallets and app developers

Apps must distinguish XRP, IOU, and MPT amounts, track LockedAmount, and recheck destination authorization when funds are actually released.

Exchanges and issuers

IOU issuers must enable AllowTrustLineLocking; MPT issuers need CanEscrow and, where required, CanTransfer. Freeze, locking, and transfer fees continue to apply.

Node operators

Nodes account for locked amounts separately, store transfer-rate information at creation, and check both completion paths against the token's current state.

What limitations and risks remain?

  • IOUs support escrow only when the issuer has enabled AllowTrustLineLocking.
  • MPTs require CanEscrow. Transfers between nonissuers also require CanTransfer.
  • An issuer cannot place its own tokens in escrow as the sender.
  • At creation, the sender must already hold the token and be authorized.
  • When issuer authorization is required, both sender and destination must meet it at EscrowCreate, and the destination is checked again at EscrowFinish. These transactions do not grant issuer authorization themselves.
  • Deep Freeze or an applicable MPT lock can prevent release.
  • XLS-85 replaces the withdrawn XLS-34 and does not support payment channels.

What fee and performance figures does the specification provide?

  • The TransferRate applicable at creation is stored in the escrow and used during settlement.
  • LockedAmount tracks the total of open escrows for each MPToken or MPTokenIssuance.
Technical details: transactions, fields, codes and invariants

Transactions

  • EscrowCreate
  • EscrowFinish
  • EscrowCancel
  • AccountSet

Ledger objects

  • Escrow
  • RippleState
  • MPToken
  • MPTokenIssuance
  • AccountRoot

Fields and flags

  • Amount
  • TransferRate
  • IssuerNode
  • LockedAmount
  • lsfAllowTrustLineLocking 0x40000000
  • asfAllowTrustLineLocking 17
  • lsfMPTCanEscrow
  • lsfMPTCanTransfer

Result codes

  • tecNO_PERMISSION
  • tecNO_AUTH
  • tecNO_LINE
  • tecNO_ENTRY
  • tecOBJECT_NOT_FOUND
  • tecINSUFFICIENT_RESERVE
  • tecUNFUNDED
  • tecFROZEN

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?

TokenEscrow is enabled on the XRP Ledger. xrpscan reports Feb 12, 2026 (UTC) as its activation date and rippled 2.5.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?

Multi-Purpose Tokens: protocol progression

  1. DeletableAccountsEnabled · from rippled 1.4.0
  2. TicketBatchEnabled · from rippled 1.7.0
  3. DisallowIncomingEnabled · from rippled 1.10.0
  4. fixDisallowIncomingV1Enabled · from rippled 2.0.0
  5. MPTokensV1Enabled · from rippled 2.3.0
  6. PermissionedDEXEnabled · from rippled 2.5.0
  7. TokenEscrowEnabled · from rippled 2.5.0
  8. PermissionDelegationDeprecated · from rippled 2.5.0
  9. fixTokenEscrowV1Enabled · from rippled 3.0.0
  10. fixMPTDeliveredAmountEnabled · from rippled 3.0.0
  11. fixCleanup3_2_0Enabled · from xrpld 3.2.0
  12. DynamicMPTOpen for voting · from xrpld 3.3.0
  13. SponsorOpen for voting · from xrpld 3.3.0
  14. ConfidentialTransferOpen for voting · from xrpld 3.3.0
  15. PermissionDelegationV1_1Enabled · from xrpld 3.3.0
  16. fixCleanup3_4_0Enabled · from xrpld 3.4.0
  17. MPTokensV2In development

Which primary sources support this information?

← All XRPL amendments and XLS specifications