I just read about a very controversial proposal that former Mt. Gox CEO, Mark Karpelès, is raising within the Bitcoin community. Basically, he is suggesting a network hard fork to recover those 80,000 bitcoins that were stolen in the 2011 attack. We're talking about something in the range of $5.2 billion at current prices, which is absolutely huge.



The interesting detail is that these funds have remained locked in that address since the attack, completely immobile for over 15 years. According to normal Bitcoin rules, there's no way to access this money without the corresponding private key. But Karpelès' proposal aims to change that, allowing Mt. Gox to recover these outputs through a specific signature from the address.

The idea is to incorporate these recovered bitcoins into the ongoing compensation process supervised by the courts, to reimburse Mt. Gox creditors who were harmed at the time. He makes it clear that this is just a starting point for discussion, with nothing finalized yet. The plan would be to limit rule changes only to this specific address and activate it at a predetermined block height.

But here comes the big caveat: any such change requires coordination across the entire network. If a significant portion of the community does not support it, we risk splitting the blockchain. It’s basically a fork against the will of some nodes, which is always delicate.

Another important point: these 80,000 bitcoins are not currently under the control of the bankruptcy administrator, nor are they part of the assets to be distributed to creditors. So technically, Mt. Gox’s proposal would have to convince the entire network to accept this rule change. It will be interesting to see how the community reacts to this.
BTC-2.01%
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • Comment
  • Repost
  • Share
Comment
Add a comment
Add a comment
No comments
  • Pin