Skip to content
EnabledTier ATokens

DeepFreeze XLS-77

Issuers can block third-party sending and receiving on a trust line. DeepFreeze is enabled on the XRP Ledger. xrpscan reports May 4, 2025 (UTC) as its activation date and rippled 2.4.0 as its first version.

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

Status
Enabled
XLS
XLS-77
Enabled
May 4, 2025 (UTC)

What does this amendment change?

Why does this amendment exist?

An ordinary freeze blocks outgoing transfers to third parties but still allows incoming tokens. Deep Freeze blocks both directions with third parties while retaining direct issuer-holder payments.

How does the mechanism work?

Deep Freeze extends ordinary trust line freezing by preventing balance changes through third-party payments and trading. Ordinary freeze must be enabled first or in the same TrustSet transaction. Direct payments between the holder and issuer remain possible; payment paths, offers, and affected AMM withdrawals are otherwise blocked.

What changes compared with the predecessor?

BeforeAfter
An ordinarily frozen trust line could still receive tokens from others and send them directly back to the issuer.A deeply frozen trust line cannot send to or receive from third parties and is excluded from related DEX and AMM workflows. Direct payments between the holder and issuer remain possible.

Who is this change relevant to?

XRP holders and users

An issuer can block transfers to and from third parties and related trading on a token position. Direct issuer-holder payments remain possible; XRP and other assets in the same account remain unaffected.

Wallets and app developers

Wallets and DEX clients must distinguish ordinary freeze from Deep Freeze, reject third-party receipts and purchases on deeply frozen trust lines, and retain the exception for direct issuer-holder payments.

Exchanges and issuers

Issuers gain a stronger compliance state. Ordinary freeze must be enabled first or at the same time; an account with NoFreeze cannot enable Deep Freeze.

Node operators

Nodes enforce the linked flags in TrustSet and prevent balance increases through rippling, the order book, and AMMs.

What limitations and risks remain?

  • Deep Freeze affects trust line tokens, not XRP.
  • Ordinary freeze must already be set or be enabled in the same TrustSet transaction as Deep Freeze.
  • Removing ordinary freeze must also remove Deep Freeze.
  • An issuer with NoFreeze cannot use Deep Freeze.
  • Deep Freeze does not return tokens to the issuer. That requires clawback.
Technical details: transactions, fields, codes and invariants

Transactions

  • TrustSet
  • OfferCreate
  • AMMWithdraw
  • Payment

Ledger objects

  • RippleState
  • Offer
  • AMM

Fields and flags

  • lsfLowDeepFreeze 0x02000000 / lsfHighDeepFreeze 0x04000000
  • lsfLowFreeze / lsfHighFreeze
  • tfSetDeepFreeze 0x00400000 / tfClearDeepFreeze 0x00800000
  • tfClearFreeze

Result codes

  • tecFROZEN

Invariants

  • lsfLowDeepFreeze may exist only together with lsfLowFreeze. The same relationship applies to the High side.

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?

DeepFreeze is enabled on the XRP Ledger. xrpscan reports May 4, 2025 (UTC) as its activation date and rippled 2.4.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?

AMM and Clawback: protocol progression

  1. DeletableAccountsEnabled · from rippled 1.4.0
  2. TicketBatchEnabled · from rippled 1.7.0
  3. DisallowIncomingEnabled · from rippled 1.10.0
  4. AMMEnabled · from rippled 1.12.0
  5. ClawbackEnabled · from rippled 1.12.0
  6. fixDisallowIncomingV1Enabled · from rippled 2.0.0
  7. fixInnerObjTemplateEnabled · from rippled 2.1.0
  8. fixAMMOverflowOfferEnabled · from rippled 2.1.1
  9. fixAMMv1_1Enabled · from rippled 2.2.0
  10. fixPreviousTxnIDEnabled · from rippled 2.2.0
  11. AMMClawbackEnabled · from rippled 2.3.0
  12. fixAMMv1_2Enabled · from rippled 2.3.0
  13. fixInnerObjTemplate2Enabled · from rippled 2.3.0
  14. fixFrozenLPTokenTransferEnabled · from rippled 2.4.0
  15. DeepFreezeEnabled · from rippled 2.4.0
  16. PermissionedDEXEnabled · from rippled 2.5.0
  17. fixAMMv1_3Enabled · from rippled 2.5.0
  18. PermissionDelegationDeprecated · from rippled 2.5.0
  19. fixAMMClawbackRoundingEnabled · from rippled 3.0.0
  20. SponsorOpen for voting · from xrpld 3.3.0
  21. PermissionDelegationV1_1Enabled · from xrpld 3.3.0
  22. fixCleanup3_3_0Enabled · from xrpld 3.3.0
  23. fixCleanup3_4_0Enabled · from xrpld 3.4.0
  24. MPTokensV2In development

Which primary sources support this information?

← All XRPL amendments and XLS specifications