OFAC SDN refers to the US Treasury’s Office of Foreign Assets Control Specially Designated Nationals and Blocked Persons List. The primary US sanctions list, identifying individuals, entities, and (since 2018) cryptocurrency addresses subject to economic sanctions. US persons and US-touching financial activity are prohibited from transacting with SDN-listed parties; non-US parties face secondary-sanctions risk for transacting with primary-sanctioned targets.
What it means in practice
The cryptocurrency dimension expanded dramatically since 2018. OFAC began listing specific Bitcoin and Ethereum addresses tied to sanctioned actors, then named entire mixers and protocols. The 2022 Tornado Cash designation was the structural shift: OFAC sanctioned the protocol itself rather than specific addresses, prohibiting US persons from interacting with the smart contracts. The 2024 Fifth Circuit ruling (Van Loon v. Department of the Treasury) held that OFAC could not sanction immutable smart contracts as “property” under IEEPA, partially reversing the legal posture; OFAC subsequently issued narrower guidance. The pattern continues: sanctioned addresses appear regularly, sanctioned protocols face occasional designation, and the compliance burden falls on every exchange and DeFi front-end that wants to maintain US-market access.
Who it affects, and how
Affects: every US person and every US-touching financial transaction (broadly construed, reaching most major exchanges and most US-incorporated DeFi front-ends). The compliance reach extends to: cryptocurrency exchanges (Binance, Coinbase, Kraken all run continuous OFAC screening), DeFi front-ends operated by US entities (Uniswap Labs blocks SDN addresses at the front-end while the underlying protocol is permissionless), wallet providers (MetaMask, Phantom screen for high-risk addresses), and traditional financial institutions. The defenses for legitimate users: avoid mixers, avoid privacy coins for transactions with US-touching counterparties, and assume any address that has ever interacted with a sanctioned protocol may be flagged at exchange deposit time. For sanctions-compliance work in NGO, journalism, or humanitarian contexts crossing sanctioned jurisdictions: the complexity is real and counsel-driven.
What you can change today
If your work touches sanctioned jurisdictions or your wallet has interacted with potentially-flagged protocols, three actions. First, screen your wallet address against OFAC SDN tooling (Chainalysis Reactor, TRM Labs, sanctions.io provide consumer or low-cost screening) before depositing to a major exchange; addresses flagged as high-risk get frozen or rejected. Second, if you operate in NGO, humanitarian, or journalism contexts that legitimately need to engage with sanctioned-jurisdiction populations, work with sanctions counsel to obtain OFAC general or specific licenses where applicable; the licenses make legitimate work possible without sanctions exposure. Third, separate operational wallets from personal wallets at the address level so a single flagged transaction does not contaminate your entire on-chain history.