/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

The decentralization of crypto services like Tornado Cash leaves authorities without an enforcement target, making them difficult if not impossible to shut down

People copied the platform's code before GitHub took it offline —People are pulling funds from sanctioned accounts —They're sending funds to random Americans https://www.wsj.com/...

Wall Street Journal

Context & Ripple Effects

Treasury's sanctions against Tornado Cash and 44 associated wallets gave compliance systems identifiable addresses to block, but copies of the service's code survived GitHub's repository removal. That separates action against listed accounts from removal of the underlying software.

The enforcement approach soon faced a legal challenge from six users and developers, while Treasury later offered a licensing route for lawful users seeking to withdraw funds. The arc exposes how account-level sanctions can entangle users even when the service itself lacks a single operator.

First-order effects

  • GitHub's takedown removes one distribution point, while copied or forked code leaves Tornado Cash's functionality available beyond that repository.
  • People receiving transfers from sanctioned addresses—including random Americans—are immediately exposed to funds linked to listed accounts, while users pull assets from those accounts.

Second-order effects

  • Treasury and compliant crypto businesses must distinguish sanctioned activity from lawful users of the service, a burden reflected in Treasury's later withdrawal-license guidance.
  • The sanctions turn into a dispute over the reach of wallet-based restrictions, giving affected users and developers grounds to challenge how the rules apply.

Third-order effects

  • If decentralized code routinely outlasts takedowns, crypto enforcement shifts from shutting services down to controlling the regulated access points around wallets, withdrawals, and recipients.
  • That shift would deepen the tension between programmable settlement and policy control: restrictions can constrain participation without eliminating the software's availability.

The trend: Crypto policy is moving toward enforcement at identifiable wallets and regulated access points when decentralized services cannot be removed at the source.

Discussion

  • @carnage4life Dare Obasanjo on x
    Despite complaints on Twitter, it's net positive for crypto if the tools that have enabled over $2B of hacks in the web3 space so far this year are banned or made harder to access. Crypto people should be celebrating moves that encourage more to FOMO in. https://www.wsj.com/...
  • @dnvolz Dustin Volz on x
    New: The U.S. sanctioning of Tornado Cash exposed gaps in the government's ability to prevent criminals from using decentralized services. “It is difficult, if not impossible, to shut down Tornado Cash entirely.” w/ @ceostroff https://www.wsj.com/...
  • @ceostroff Caitlin Ostroff on x
    New w/@dnvolz: U.S. officials sanctioned Tornado Cash this week but limits are already showing: —People copied the platform's code before GitHub took it offline —People are pulling funds from sanctioned accounts —They're sending funds to random Americans https://www.wsj.com/...