-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
notes: describe Stone Man's 9k BTC loss
- Loading branch information
1 parent
e049a93
commit 4f05d8e
Showing
1 changed file
with
9 additions
and
0 deletions.
There are no files selected for viewing
9 changes: 9 additions & 0 deletions
9
notes/script/1c428e2d274683aa69b386cbdf254beac1c2875caab14943e0a3a17e03d83e86.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
### Stone Man's BTC | ||
|
||
In August 2010, bitcointalk user `Stone Man` posted[^1] seeking help recovering lost BTC. Unfortunately, the user had made a test transaction sending his 9000 BTC to a new address within his wallet, and then restored the wallet from a previou backup. | ||
|
||
At this point in Bitcoin History, each individual address in a wallet was backed by a private key completely unrelated to any other address in the wallet. As the wallet backup had been generated before the new address used to receive the coins had been created, the private key for the new address was not in the backup. | ||
|
||
This effectively turned that address, `167ZWTT8n6s4ya8cGjqNNQjDwDGY31vmHg`, into a Burn Address, forever sealing in the BTC. | ||
|
||
[^1]: https://bitcointalk.org/index.php?topic=782.0 |