After twelve years of silence, five old wallets sent 107 bitcoin to an address that cannot spend. Then they stopped. Why?
In May 2026 someone destroyed about $8.5 million in bitcoin they had held since 2014. A $1 million round-trip through a custodian happened first. Nobody has a good answer.
The appearance
Five addresses, funded on the same day in April 2014 when bitcoin was under $600, woke up in 2026 and sent their coins to an unspendable sink. Chainalysis flagged common ownership. Before the burn, one of them sent 20.00010537 BTC to a large custodian and got 20.00006037 BTC back three weeks later — a $3 difference. Then the fortune was destroyed.
Case file sealed
Investigation notes, the reconstruction, and sources sit behind this seal. Open it when you have sat with the raw transaction.
Open the case file
The investigation
-
01 They knew how to use an exchange
Between 2014 and the long sleep, the same cluster sent almost the same dollar amount — about $10,400 — to the same deposit address, 58 times out of 60, even as the bitcoin price moved. That is how a person pays a bill, not how a lost key behaves.
-
02 The round trip
Educator Bennet documented the March 2026 bounce: 20 BTC out, 20 BTC back, minus 4,500 satoshis. Custodians clip a little for fees or dust. The coins came home. Destroying them afterwards was a choice, not a lockout.
-
03 Theories that do not fit
A hacker who wanted the money would not burn it. An estate liquidating would sell it. A religious or artistic burn is possible and unfalsifiable. A proof-of-sacrifice for some off-chain deal would usually come with an OP_RETURN memo; this one did not, at least in the public write-ups. A fat-finger to a burn address is possible once, not for 107 BTC across five wallets.
Reconstruction
The chain proves intent more than motive. The coins were not lost: they were moved, custodied, returned, then sent to a sink. We can rule out a simple hack and a simple forgotten key. We cannot say whether this was protest, ritual, a private settlement, or a mistake we have not reconstructed. The file stays open.
Still open: Identity of the owner, the custodian, the burn address’s exact script, and any off-chain explanation they have not published.