DHS Seizure of Mt. Gox Dwolla and Wells Fargo Accounts (May 2013)
BlockedLegal or institutional constraint prevented access — the authorized party could not move the funds.
On May 15, 2013, the US Department of Homeland Security, acting through Immigration and Customs Enforcement, seized approximately $2.9 million from Mt. Gox's Dwolla payment processor account and a further $2.1 million from its Wells Fargo account.
The seizure targeted Mt. Gox's US subsidiary, Mutum Sigillum LLC, on grounds that it was operating as an unlicensed money transmitter in violation of 18 U.S.C.
§1960. At that time, the Dwolla account served as the primary mechanism for US-based customers to deposit and withdraw US dollars. With both the Dwolla and Wells Fargo pathways frozen, American Mt. Gox account holders holding dollar balances faced a complete withdrawal impasse.
While Bitcoin withdrawals technically remained available, they were already experiencing severe delays that would worsen in subsequent months. The seizures demonstrated that US regulatory authorities could and would reach into the banking infrastructure of foreign-operated exchanges serving American customers, even when those exchanges held customer assets. The incident triggered widespread concern in the nascent Bitcoin community regarding regulatory jurisdiction and the vulnerability of dollar-denominated exchange balances to government action. CoinDesk and other news outlets covered the DHS action extensively, amplifying awareness of the regulatory and operational risks that custodial exchange models presented.
The account seizures marked the beginning of a permanent fiat withdrawal crisis at Mt. Gox that persisted until the exchange's full collapse in early 2014, after which customer recovery efforts would span years through bankruptcy proceedings.
| Stress condition | Legal or authority constraint |
| Custody system | Exchange custody |
| Outcome | Blocked |
| Documentation | Present and interpretable |
| Year observed | 2013 |
| Country | United States |
When legal authority exists but operational access does not
Traditional financial institutions bridge the legal system and the operational system. A bank transfers funds when presented with a probate order because the bank is regulated, operates within the legal system, and has processes for accepting legal authority. A Bitcoin blockchain has none of these properties. It validates cryptographic signatures. That is the entirety of its access model.
Cases in this archive involving legal authority constraints fall into two main categories: cases where the legally authorized party lacks the credentials to exercise authority (the executor has the court order but not the seed phrase), and cases where legal or regulatory structures have blocked access to an exchange or custodial platform (sanctions, court-ordered freezes, regulatory seizures). The first category often has no technical resolution. The second depends on the legal process that imposed the constraint.
The gap is most pronounced in estate and inheritance contexts, where the deceased owner's legal authority transferred to an executor who was not given — and could not compel — the operational credentials.
Legal authority constraint cases are resolved before the stress event, not during it. The resolution is ensuring that legal authority and operational access are aligned: the executor knows where the credentials are, or has been designated as a trusted holder of credentials, or is working with a professional who was given access in advance. Legal documents alone do not bridge the gap — only pre-arranged operational access does.
Translate