Posts
avatar

A GitHub user typed four words and froze $150 million in Ethereum. "I accidentally killed it." Still frozen today. Nobody got it back. This is the story of devops199 and the Parity wallet bug. July 19, 2017 - Parity, built by Ethereum co-founder Gavin Wood, is one of crypto's most trusted wallets - a bug in its multisig wallets lets an attacker drain 153,037 ETH (~$30M) - Parity patches it the next day The patch hides a new problem. A shared "library" contract every new Parity wallet depends on. Nobody owns it and still has a kill switch. A dev warned about it in August. Parity filed it as a "convenience enhancement." November 6, 2017 - devops199 tells Parity's chat "I'm eth newbie..just learning" - says he's been sending kill() to random contracts - finds the unclaimed library - makes himself the owner - calls kill() The library self-destructs. 587 wallets now point to nothing. 513,774 ETH is frozen. He asks: "Will I get arrested for this?" Then opens GitHub issue #6995. Title: "anyone can kill your contract" Body: "I accidentally killed it." who got hit - Web3 Foundation, building Polkadot (Gavin Wood's own project): 306,276 ETH - ICONOMI: 114,939 ETH - hundreds more April 2018 - EIP-999 proposes bringing the dead library back - a coin vote: 330 no, 300 yes - the frozen Polkadot wallet votes yes - the proposal is withdrawn Today - the library address still holds no code - Polkadot's wallet still holds 306,276 ETH - at $2,267 per ETH, the full 513,774 ETH is worth $1.16 billion today - the account behind issue #6995 now shows up as "ghost" one account got $150M frozen in 2017 and now it has ~$1.16B

This content is for informational and educational purposes only. It may include third-party insights, sponsored content, or promotional material for which the creator may receive compensation. Nothing in this feed constitutes investment advice or a guarantee of returns. You are solely responsible for your own investment decisions. Always conduct your own research and exercise caution before trading. We do not guarantee the accuracy of third-party information and are not liable for any losses incurred. Past performance is not indicative of future results. Please refer to our Community Terms and Risk Disclosure Statement for details.

avatarPost your reply

Comment