作者 | GaryMa，吴区块链相关链接：https://bitcointalk.org/index.php?topic=782.msg8620#msg86202010年5月22日，程序员Laszlo Hanyecz用10000个比特币换了两个披萨，创造了一年一度值得纪念的加密货币传奇“大手大脚”。然而，披萨事件发生后不到三个月，另一名绰号“石头人”的男子也“花掉”了近 9000 个比特币。不同的是，Laszlo 至少填饱了肚子，而这名男子得到的却是一次惨痛的教训——现在价值 11 亿美元——这是由于技术误解造成的。在那个代码就是法律的狂野时代，一次致命的备份疏忽导致他眼睁睁地看着自己的财富在记忆中蒸发。尽管在意识到结果不可逆转后，他平静地用笑脸回答并说“就这样吧”，但这个微笑成为了区块链历史上最昂贵、最令人心碎的脚注之一。历史场景：消失在记忆中的二十分钟 2010 年 8 月 10 日，Bitcointalk 论坛的技术支持版块中出现了一条标题为“丢失大量比特币”的求助帖。 发生了什么： 1．完整备份：用户Stone Man购买了9,000 BTC并已
ry 小心地将钱包文件 wallet.dat 备份到 USB 驱动器。2.极端环境：他正在运行Live CD系统（完全在内存中运行的操作系统；所有未保存的数据在关机时都会被擦除）。3。致命测试：他试图将 1 BTC 转给自己。4。破坏性重启：广播交易后，直接关闭并重启系统。 5．噩梦：重启恢复备份文件后，发现余额只剩下1个BTC——剩下的8999个BTC都消失了。 论坛“人间戏”：在那个只有几千人的小圈子里，石头人的经历引发了早期密码学老手的集体“咨询”。Gavin Andresen（中本聪的继任者）亲自回复。确认石头人重启后才确认a
Author | GaryMa, Wu Blockchain
Related link:
https://bitcointalk.org/index.php?topic=782.msg8620#msg8620
On May 22, 2010, programmer Laszlo Hanyecz exchanged 10,000 bitcoins for two pizzas, creating the annually commemorated crypto legend of a “lavish spend.” However, less than three months after the pizza incident, another man — known by the nickname Stone Man — also “spent” nearly 9,000 bitcoins.
The difference was that Laszlo at least filled his stomach, while what this man received in return was a painful lesson — now worth USD 1.1 billion — caused by a technical misunderstanding. In that wild era when code was law, a fatal backup oversight led him to watch his wealth evaporate in memory. Although, after realizing the outcome was irreversible, he calmly replied with a smiley face and said “so be it,” that smile became one of the most expensive — and most heartbreaking — footnotes in blockchain history.
I. The Historical Scene: Twenty Minutes That Vanished in Memory
On August 10, 2010, a plainly titled cry for help appeared in the technical support section of the Bitcointalk forum: “Lost large number of bitcoins.”
What happened:
1. Full backup: The user Stone Man bought 9,000 BTC and very carefully backed up his wallet file, wallet.dat, to a USB drive.
2. Extreme environment: He was running a Live CD system (an OS that runs entirely in memory; all unsaved data is wiped on shutdown).
3. Fatal test: He attempted to transfer 1 BTC to himself.
4. Destructive reboot: After broadcasting the transaction, he shut down and rebooted the system directly.
5. The nightmare: After rebooting and restoring the backup file, he found the balance was only 1 BTC — the remaining 8,999 BTC had vanished.
The forum’s “human drama”: In that small circle of only a few thousand people, Stone Man’s experience triggered a collective “consultation” by early cryptography veterans.
Gavin Andresen (Satoshi Nakamoto’s successor) personally replied. After confirming that Stone Man rebooted before confirmation and without creating a new backup, the technical leader could only sigh: “This is a very expensive lesson.”
Forum veteran Theymos delivered a cold technical verdict: if the memory had been overwritten and no new backup existed, those coins were gone forever.
An ironic consolation: A user replied at the time, “Don’t be too sad — this is only a few hundred dollars (9,000 BTC was worth about USD 400–600 back then). You can lose more than that in an hour at a casino.”
“After confirming that no technical means could recover the private keys, Stone Man did not rage or blame the system. He simply left this very hacker-style conclusion at the end of the thread: ‘I have accepted this fact. This has been an expensive learning process… so be it :)’”
II. Deep Analysis: Why Was the Money Lost Despite Backing Up the Wallet?
Stone Man’s tragedy collided with a core feature of Bitcoin’s underlying design: UTXO (Unspent Transaction Output) and the random change mechanism.
1. The ‘shatter and recast’ logic of UTXOs
There are no “balances” in the Bitcoin ledger — only “checks” (UTXOs). When you own 9,000 BTC and send out 1 BTC, the system shatters that 9,000-BTC check and remelts it into two new checks: one for 1 BTC sent to the recipient, and another for 8,999 BTC returned to yourself as “change.”
2. The deadly randomness of change
In early clients around 2010, for privacy reasons, this “change” was by default sent to a brand-new temporary address.
Logical break: The new private key was randomly generated in memory at the moment of the transaction, while Stone Man’s backup reflected the pre-transaction state.
Physical disappearance: He shut down before the in-memory data was written to the backup file. The electrical signals carrying what would later be worth USD 1.1 billion dissipated, and the key to the new address was never saved.
III. Technological Evolution: The Essential Differences of Mnemonics Across Models
Stone Man’s tuition ultimately helped drive the creation of BIP32 (HD wallets). Although both Bitcoin and Ethereum now use mnemonic phrases, their functional logic differs fundamentally:
1. Ethereum mnemonics: merely an ‘address manager’
a. In Ethereum’s account model, mnemonics are more about convenience in management. Fixed nature: Once address A is generated, assets are always added to or deducted from that same address.
b. Role: The mnemonic simply helps derive the private key of address A. Even without the mnemonic, as long as you have the private key of address A, you control all assets at that address.
2. Bitcoin mnemonics: an ‘asset safety lock’
a. In Bitcoin’s UTXO model, the mnemonic is the lifeline that preserves asset continuity. Dynamic nature: Bitcoin assets are fluid, constantly jumping from old addresses to new change addresses.
b. Core difference: A Bitcoin mnemonic not only generates the first address, it also locks in the private keys for an infinite number of future change addresses. With the mnemonic, mathematics can always calculate where that “jumped” change went; with only a single address’s private key, you simply cannot trace the assets that have jumped away.
IV. Warning: Why Can This Tragedy Still Happen Today?
Even today, if you operate Bitcoin with an “Ethereum mindset,” you can still fall into Stone Man’s trap.
A typical self-destructive operation: Some users generate addresses with an HD wallet but back up only the private key of the first address, not the recovery phrase, and then delete the wallet.
Consequence: When they send a small amount (e.g., holding 10 BTC and sending 1 BTC), the remaining 9 BTC is returned as change to a newly generated address.
Ending: Because they only possess the private key of the first address — and not the mnemonic that can derive subsequent addresses — the 9 BTC in change is lost forever, and they become the “new Stone Man” of 2025.
Follow us
Twitter: https://twitter.com/WuBlockchain
Telegram: https://t.me/wublockchainenglish