People keep sending bitcoin to an address that says, in English, not to. Who owns it?
1BitcoinEaterAddressDontSendf59kuE is a valid address. Nobody has the private key. About 13.4 BTC have gone in anyway.
The appearance
The address is almost a sentence. Wallets accept it: the checksum at the end (f59kuE) is correct Base58Check, so it is not a typo. Thousands of transactions have credited it. Nothing has ever left. If addresses are identities, this one is a black hole with a warning label that people ignore.
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 How you make a named void
A Bitcoin address is a version byte, a 20-byte payload, and a 4-byte checksum, all in Base58. You do not need ECDSA to build one. Pick the payload that encodes the words you want, compute the checksum, and you have a string wallets will send to. The corresponding private key would have to hash to that exact payload. For a vanity this long, that key will not be found before the heat death of the sun.
-
02 Why coins still arrive
Some sends are jokes. Some are protocol burns (Omni and other coloured-coin systems used the eater as a destruction address). Some are people testing a wallet. A few are almost certainly mistakes by users who thought the visible words were a memo, not the destination. The chain cannot tell them apart.
Reconstruction
Nobody owns it. The eater is a deliberately unspendable sink — a vanity payload plus a real checksum. Sending to it is a one-way burn. The 13.4 BTC there are as gone as if they had been sent to OP_RETURN, with worse manners: full nodes must keep the UTXOs because, unlike OP_RETURN, a P2PKH output is not provably unspendable to the software, only to mathematics.