Compliance9 min read
MB
Editorial Team
·October 31, 2026

What Must an Issuer Report After Freezing Sanctioned Tokens?

An OFAC blocked property report is the filing a US person must make within 10 business days after property of a sanctioned person becomes blocked, and that includes tokenized securities frozen on-chain. Under 31 CFR Part 501, the holder then files an annual report by September 30 and keeps records for at least 10 years after unblocking. A smart-contract freeze starts the compliance work; it does not finish it.

TL;DR — Key Takeaways

  • ✓Initial report: Due within 10 business days of the property becoming blocked, filed through the OFAC Reporting System. It names the holder, the sanctions target, the property, the date blocked, the legal authority and a US dollar value, estimated if the actual value is unknown.
  • ✓Annual report: Every holder files a report of all blocked property held as of June 30 by September 30. Property kept in an omnibus account, such as a consolidated blocked wallet, must be listed asset by asset.
  • ✓Records: 31 CFR 501.601, as amended by a rule published September 13, 2024 and effective March 12, 2025, requires records of blocked property for as long as it stays blocked and for at least 10 years after it is unblocked.
  • ✓Token gap: Our analysis: a frozen ERC-3643 wallet can still be moved by an agent through forcedTransfer or burn. OFAC FAQ 646 requires that all parties be denied access, which reaches the agent keys, not only the investor.

Ready to get started?

Join others who are already using our platform.

What Must an Issuer Report After Freezing Sanctioned Tokens?

What does OFAC require once a token position is blocked?

An initial blocking report within 10 business days, an annual report of everything still blocked as of June 30 by September 30, and records kept for at least 10 years after unblocking. All three come from 31 CFR Part 501, subpart C.

The Office of Foreign Assets Control (OFAC) administers US sanctions. When a person on the Specially Designated Nationals (SDN) List, or another blocked person, has an interest in property held by a US person, that property is blocked. The holder may not transfer it, pay it out or let anyone deal in it. For a tokenized security, the property is the position: the token balance and the entitlement it represents on the register.

Section 501.603(b)(1) lists what the initial report must contain. The list is longer than most token teams expect:

  • Filer: name and address of the person holding the property, plus a contact name, telephone number and email address.
  • Transaction: any transaction associated with the blocking, the parties to it and their locations, and reference numbers or dates needed to identify it.
  • Target: the sanctions target whose property is blocked, its location if known, and a narrative of its interest in the property if that is not evident.
  • Property: a description and location, including account numbers and other identifiers. For a token, the contract address, chain and wallet address are the natural identifiers.
  • Date and value: the date blocked and the actual value in US dollars, or an estimated value if the actual value is unknown.
  • Action and authority: any action taken with the property, and the legal authority for the blocking. The rule says “SDN” alone is too generic to count as the authority.
  • Documents: a copy of any payment or transfer instructions or other documentation received with a related transaction.

Section 501.603(d) requires initial and annual reports to be filed electronically through the OFAC Reporting System (ORS), and the filer must keep a copy. The value field is where tokenized assets need preparation. A thinly traded security token may have no market price on the blocking date, so the issuer should decide in advance which valuation source it will cite, such as the latest net asset value for a fund token.

“Reports shall be filed within 10 business days from the date that property becomes blocked.”

31 CFR 501.603(b)(1)(i), eCFR

Who files when the issuer holds the freeze key and the investor holds the private key?

The rule puts the duty on every US person with “possession or control” of blocked property and puts primary responsibility on the actual holder. Which party that is for a self-custodied token is not settled; treat it as a question for counsel.

Section 501.603(a)(1) covers any US person, including a financial institution, holding, unblocking or transferring blocked property. Section 501.603(a)(2) lets an attorney or agent file on someone's behalf, but keeps primary responsibility with the actual holder, transferrer or releaser. Trust assets are the trustee's responsibility. The same paragraph closes one escape route: no one is excused from filing because another person filed, unless they have actual knowledge of that other report.

A permissioned token splits control in a way the rule did not anticipate. The following is our analysis, not OFAC guidance. In a typical ERC-3643 deployment, three parties have some claim to “control”:

  • The issuer or its token agent can freeze, force-transfer and burn through agent functions, so it controls whether the position moves.
  • The transfer agent keeps the master securityholder file, which records who legally owns the security.
  • A qualified custodian, where one is used, holds the private key for the investor's wallet.

If the investor self-custodies, no US person holds the key. The issuer still controls whether the token can move. Several parties may each have a filing duty, and the actual-knowledge rule means each one needs evidence of the others' filings before relying on them. A written allocation of who files, signed before the first freeze, removes the argument from the 10-day window.

“No person is excused from filing a report by reason of the fact that another person has submitted a report with regard to the same property, except upon actual knowledge of the report filed by such other person.”

31 CFR 501.603(a)(2), eCFR

How does each token action map to an OFAC duty?

A freeze is the blocking control, a forced transfer to a consolidated blocked wallet is a holding choice OFAC FAQ 646 accepts for virtual currency, and an unfreeze is a release that needs OFAC authorization or a delisting. Each action needs an off-chain record.

OFAC FAQ 646, released October 15, 2021, is OFAC's main statement on blocking digital assets. It allows a firm to block each wallet separately or to consolidate blocked holdings in one wallet, “similar to an omnibus account”. Either works if controls allow release “only pursuant to an OFAC authorization” or when the prohibition stops applying. The FAQ speaks of virtual currency. Applying it to tokenized securities is a reasonable reading, not a statement OFAC has made.

Token action (ERC-3643)OFAC duty it servesRecord to keep (our recommendation)
setAddressFrozen on the holder's walletDeny the holder access; starts the evidence trail for the initial reportScreening hit, match review, approver, transaction hash, block time
freezePartialTokensBlock only the amount in which the target has an interest, such as a shared or omnibus walletHow the blocked amount was calculated and who owns the rest
forcedTransfer to a consolidated blocked walletHolding option under FAQ 646; the annual report must still list each assetSub-ledger mapping each unit in the wallet to its target and original position
Coupon or dividend due on the positionNot addressed in FAQ 646; treatment to be set with counselAmount due, where it is held, and the decision behind it
burn or redemptionWould deal in blocked property; on our reading not permitted without OFAC authorizationLicense reference, if any
Unfreeze or unfreezePartialTokensUnblocking report within 10 business days, unless a delisting or license exemption appliesOFAC authorization or SDN removal notice, report reference, transaction hash

Two details from the ERC-3643 text matter here. First, a normal transfer reverts if the sender or the receiver wallet is frozen, which is the access denial OFAC needs. Second, the specification says mint and forcedTransfer only require the receiver to be whitelisted and verified in the Identity Registry, bypassing the compliance rules, and that burn bypasses all eligibility checks. A consolidated blocked wallet therefore has to be registered as a verified identity before an agent can move anything into it. It also means the agent key can still move a frozen position. FAQ 646 says “all parties” must be denied access, so the agent role needs its own controls, such as a multisig with a documented approval step, for any action touching a blocked wallet. Where agent keys fit in the wider control stack is covered in our guide to smart contract compliance versus Layer-0 governance.

“U.S. persons are not obligated to convert the blocked virtual currency into traditional fiat currency (e.g., U.S. dollars), and are not required to hold such blocked property in an interest-bearing account.”

OFAC FAQ 646, How do I block digital currency?

When is a rejected transfer reported instead of a blocked one?

When the transaction is not blocked but would still violate OFAC rules. Section 501.604 requires a rejected transaction report within 10 business days and lists “transactions related to securities” as covered transactions.

Blocking and rejecting are different outcomes. Blocking applies when a blocked person has an interest in the property: the holder keeps it frozen. Rejection applies when no blocked interest exists but processing the transaction would breach a sanctions program, for example under a program that prohibits dealings with a region without blocking the property. The firm declines the transaction and the property goes nowhere.

On-chain, both can look identical: a transfer reverts. That is the problem. An illustrative case, not a real one: a compliance module rejects a secondary-market purchase because the buyer's identity claim shows residence in a sanctioned jurisdiction. The revert message says only “Compliance failure”. Whether that event is a reportable rejected transaction, a blocking or neither depends on the program and the facts, and the smart contract cannot tell. The issuer needs a process that reviews sanctions-driven reverts and decides, within the same 10 business days, whether a 501.604 report is due.

The report itself follows the same pattern as a blocking report: the rejecting party and a contact, a description of the transaction and its participants, the target if any, the date rejected, the value in US dollars, the legal authority, and related documents. It is filed through ORS.

What records must survive the freeze, and for how long?

Records of blocked property must be available for as long as the property is blocked and for at least 10 years after it is unblocked. Transaction records must be kept for at least 10 years. An OFAC interim final rule published September 13, 2024 raised both periods from 5 to 10 years, effective March 12, 2025.

Section 501.601 applies to “every person holding property blocked” and requires a “full and accurate record”. For a tokenized security, the on-chain events are part of that record but not all of it. An AddressFrozen event proves a wallet was frozen at a given block. It does not prove why, who approved it, which sanctions target it relates to or what value was reported. Those facts live off-chain, and they must link to the on-chain event by transaction hash.

The annual report raises the stakes. Every holder must report all blocked property held as of June 30, by September 30, valued in US dollars as of June 30. Section 501.603(d)(1) adds that blocked funds held in an omnibus account must be shown in a disaggregated list of each blocked asset. A consolidated blocked wallet is the token equivalent of that omnibus account. Without a sub-ledger that ties each unit to its target and original position, the annual report cannot be completed from chain data alone. The design of tamper-evident logs that can carry this mapping is the subject of our guide to immutable audit trails for RWA compliance.

“Every person holding property blocked pursuant to the provisions of this chapter ... shall keep a full and accurate record of such property, and such record shall be available for examination for the period of time that such property is blocked and for at least 10 years after the date such property is unblocked.”

31 CFR 501.601, eCFR (as amended at 89 FR 74834)

What should an issuer set up before the first freeze?

A runbook that turns a confirmed sanctions match into a freeze, a filed report and a linked record inside 10 business days, with named owners for each step. These are our recommendations, not OFAC requirements.

Most of the 10-day window is consumed by questions that could have been answered earlier. The controls that remove them:

  • Filing allocation: a written agreement between issuer, token agent, transfer agent and custodian on who files the initial, annual and unblocking reports, and how each party gets proof of the others' filings.
  • ORS access: an OFAC Reporting System account set up before it is needed, since initial and annual reports must be filed through it.
  • Valuation source: a pre-agreed source for the US dollar value of each token, so the report does not wait on a pricing decision.
  • Agent key policy: no forcedTransfer, burn or unfreeze on a blocked wallet without a second approver and a recorded OFAC authorization or delisting reference.
  • Blocked-property sub-ledger: one entry per blocked position, with target, program, date blocked, value, wallet, transaction hashes and report references, kept for 10 years after unblocking.
  • Distribution rule: a documented treatment, agreed with counsel, for coupons, dividends and redemptions that fall due on a blocked position.
  • June 30 snapshot: a scheduled extract of all blocked positions and their values on June 30, feeding the report due September 30.

A protocol-level compliance layer can enforce the freeze and produce the on-chain half of the record: which wallet, which identity, which block. Screening decisions, legal analysis and the filings themselves remain with the US persons the rule names. None of this article is legal advice; sanctions programs differ, and the facts of each blocking decide which reports apply.

Sources: 31 CFR 501.603, Reports of blocked, unblocked, or transferred blocked property (eCFR); 31 CFR 501.604, Reports of rejected transactions (eCFR); 31 CFR 501.601, Records and recordkeeping requirements (eCFR); OFAC FAQ 646, How do I block digital currency?; OFAC interim final rule, Reporting, Procedures and Penalties, 89 FR 74832; ERC-3643 specification. Sources checked October 31, 2026. The mapping of token actions to OFAC duties, the analysis of who holds a self-custodied token, the illustrative rejected-transfer case and the recommended controls are editorial analysis, not OFAC statements. Not legal advice.

Frequently Asked Questions

Does freezing a wallet with setAddressFrozen satisfy OFAC's blocking requirement?

Not on its own. OFAC FAQ 646 says a US person holding blocked virtual currency must deny all parties access, comply with the holding and reporting rules, and keep controls that allow release only under OFAC authorization. A wallet freeze stops the holder's own transfers, but ERC-3643 agents can still call forcedTransfer and burn. The freeze also sits inside a 10-business-day window for the initial blocking report.

Is the 10-day OFAC reporting deadline in calendar days or business days?

Business days. Under 31 CFR 501.603(b)(1)(i), the initial blocking report is due within 10 business days from the date the property becomes blocked. The text ties the clock to the blocking, not to the date an agent sends the freeze transaction, so a slow screening cycle can use up part of the window. Initial and annual reports are filed through the OFAC Reporting System.

Must blocked tokens be converted to dollars or moved to an interest-bearing account?

For virtual currency, no. OFAC FAQ 646 states that US persons are not obligated to convert blocked virtual currency into fiat currency and are not required to hold it in an interest-bearing account. The FAQ speaks about virtual currency; it does not address tokenized securities by name. Coupons or dividends falling due on a blocked position need a documented treatment agreed with sanctions counsel.

Does unfreezing tokens after a sanctions delisting require a report to OFAC?

Not always. Section 501.603(b)(3) requires an unblocking report within 10 business days, but exempts unblocking that follows OFAC's removal of the person from the SDN List, and unblocking explicitly authorized by a general or specific license unless the license asks for a separate report. Recordkeeping continues either way: records must stay available for at least 10 years after the property is unblocked.

Ready to get started?

Join others who are already using our platform.