The Blacklist Without Addresses: OFAC Names Iran’s Bitcoin Toll Collectors but Not Their Keys

On July 29, the U.S. Office of Foreign Assets Control designated HormuzSafe Marine Services Authority and Persian Gulf Marine Insurance Company as blocked entities under Executive Order 13902. The Treasury’s position is direct: both firms front for an Islamic Revolutionary Guard Corps-backed scheme that forces commercial vessels to buy insurance for passage through the Strait of Hormuz. HormuzSafe reportedly accepts Bitcoin and other digital assets to move those payments outside Western visibility. The two OFAC pages name the companies. They do not name a single wallet address. No public keys. No transaction volume. No payment history. For anyone who reads sanctions lists for a living, that is the real story. OFAC has identified a crypto-accepting sanctioned entity without identifying its crypto. That distinction is not technical detail. It is the entire enforcement question. Executive Order 13902 reaches Iran’s financial sector and provides a secondary-sanctions hook. That means non-U.S. actors can be cut off from the U.S. financial system for knowingly facilitating certain sector transactions. The same July 29 action also designated eight shadow-fleet companies and eight vessels tied to Iran’s petroleum sector. Those entities form a separate arm. The insurance firms are the settlement layer that takes the digital assets. The April reporting already connected HormuzSafe to a proposal for Bitcoin-denominated tolls. By July, an oil tanker had been attacked after its crew fell for a fake crypto clearance in the same waterway. The situation stopped being theoretical. The OFAC action is the U.S. response, and its absence of on-chain identifiers is a red flag. The legal surface is far broader than the list. OFAC rules cover U.S. citizens and permanent residents wherever they are, people and entities inside the United States, and U.S.-incorporated companies along with their foreign branches. Iran sanctions can also reach foreign entities owned or controlled by U.S. persons. If property of HormuzSafe, PGMIC, or any other blocked person enters U.S. control, it must be frozen. A report must reach OFAC within 10 business days. The same deadline applies when a transaction is rejected rather than blocked. The 50 Percent Rule widens the scope further. Any unlisted entity that is owned 50 percent or more, directly or indirectly, individually or in the aggregate, by blocked persons is treated as blocked. This rule looks like arithmetic. In maritime trade, it is a forensic requirement. Ownership is stacked across flag states, shelf companies, trusts, and bareboat charters. A compliance team cannot simply screen against exact names. It has to reconstruct the ownership graph of each counterparty before issuing a policy, renewing it, or paying a claim. OFAC’s insurance guidance recommends risk-based screening across those touch points, but the number of variables is far from exact. Civil enforcement operates on strict liability. A U.S. person can be held liable without knowing a transaction was prohibited. Ignorance is not a defense. Foreign counterparties face a different risk path: causing or conspiring to cause a U.S. violation, evasion, knowing material support to a designated person, or knowingly facilitating significant transactions can all trigger exposure. Treasury’s Hormuz-specific guidance warns that safe-passage payments can create significant exposure for non-U.S. actors. Transit through the strait is not itself the trigger, but the payment for transit can be. This is where the design breaks down. Sanctions bind legal persons. Bitcoin binds private keys. There is no interface between them. During an audit of custodial wallet infrastructure in 2024, I saw the same gap in a different setting. The wallet provider called its multi-signature setup compliant because every signer had a KYC record. The private keys themselves had no sanctions tag. A blocked person could sit behind a shareholder agreement, hold a signing share, and move value without a compliance trigger visible on-chain. The legal ownership layer and the cryptographic ownership layer were two separate systems. OFAC is now trying to enforce the legal layer while the cryptographic layer sits outside its view. That is a design bug, not a paperwork problem. On a permissionless chain, transaction validity depends on signatures, script logic, and consensus. It does not check a Specially Designated Nationals list. The law says a blocked person’s property is frozen from the moment it is identifiable. The chain has no freeze function. Code is law, but bugs are reality — and this is the bug. The deeper problem is asymmetrical enforcement. By naming HormuzSafe and leaving its addresses hidden, OFAC signals that a new wallet, a reorganized shell, or a no-KYC exchange is enough to outrun the list. The designation names a legal entity, not the keys that control the funds. It creates a compliance tax on U.S. firms and zero friction for the sanctioned payer. Privacy is a feature, not a bug, but without attribution it becomes a one-way shield. The designated party gets private settlement. The compliant counterparty gets strict liability. For an enforcement action, that is a poor trade. Math doesn’t negotiate. But the math of Bitcoin’s consensus is not the math of corporate ownership. The 50 Percent Rule is a legal calculation built on registries, not on cryptographic proof. Until those two models intersect, the blacklist will remain a legal instrument without an executable claim. The next designation will need a different format. It will include wallet addresses, or it will rely on stablecoin issuers to freeze off-chain redemption. Tether’s July freeze of Iranian-linked funds showed that compliant stablecoin rails can be controlled. Bitcoin cannot be controlled the same way. The Strait of Hormuz is not just a trade chokepoint anymore. It is a live testbed for the question regulators have avoided: can a list of legal names freeze a set of private keys? The Treasury has answered for the legal part. The network is still waiting for the hardware.