well more in the name of testing out things.
With the yesterdays big news of 200 BTC stolen from Luke Dashjr (one of the Bitcoin core developers) i decided to do a test. Because if it can happen (if it happened) to a bitcoin core developer, there is a good chance it will happen to me or you.
Most that are in crypto for some time heard and know all about the keys safety. Store offline, use hardware wallets, keep multiple copies of seeds in different secure locations... Question is how many do all of that, and how good and secure was the execution of all of it.
I do know a lot about recovery account, possibility to change keys and all of that Hive good stuff but i never had the need to use it to try and save my account. So i decided to do this test and see what is the process and how complicated it is.
To make it a bit more interesting i transferred 50HBD to the account. As i didn't see the news about the 200 BTC hack for almost 24 hours i will not be doing anything whit the account for the next 2 days. And i will not move funds for the wallet for 30 days.
There is a chance you will not notice that your keys are compromised right away (there is a way to set up phone notification for some actions like powerdown, transfer... i think through a discord bot. But that is also something i need to learn about).
I think i will learn stuff and if i lose 50$ it will be a valuable lesson.
If there are Bitcoin Maxies reading this you can transfer that 50HBD easy through V4V and get aprox. 50$ of BTC on the lightning network in few seconds.
account/wallet: leaked.key
Private Keys:
Posting Key used for "social transactions": 5JsQKGdJPRwLaXyPbk5b1bwq9jYghT24r8gzBGLgXYQXdmJr4X2
Active Key used for "value transfers": 5JB24uqagMfLLXSN612iS2JwX5V9eWVVSjZyn4fZXo1K6EHbLAZ
By clicking the publish button i realized that Peakd added this check to warn you before you publish your keys on chain. Nice.
Good luck to you and me :)
And Happy New Year