Topic: Accidental Ethereum Wallet Freeze Was Actually Deliberate (Read 220 times)
it was deliberate in so far as he sent the kill instruction. did he mean to lock in all that eth? that's the salient point and from what he said online most people believe it wasn't intentional. he wasnt trying to steal the eth at all. just mucking about with code. the blame lays squarely with parity on this one.
Frozen funds are problem, as such things lower trust in to crypto. For such cases there must be reasonable consensus between resonable solution (Anybody, who lost money, is definitely not happy) on other hand we must preserve decentralisation. A kind of consensus should be the key for future solutions to avoid such situations. And bugs are here and will always be. But upgrading the program is not the same as upgrading smart contract...just it is there as it is, unchangeable...
News of over $300 million in ETH going frozen thanks to a flaw took the industry by a storm earlier this week. A user named Devops199 had claimed responsibility for triggering a critical security vulnerability in a Parity multi-sig wallet paralyzing all wallets that were created after July 20th. While Devops199 had said that they had triggered this bug accidentally, at least one company has suggested that it was no accident.
The problem stems from another bug that was discovered in July and during its fix a new flaw was left in the code. “Following the fix for the original multi-sig issue that had been exploited on 19th of July (function visibility), a new version of the Parity Wallet library contract was deployed on 20th of July,” Parity wrote in its advisory. “However that code still contained another issue – it was possible to turn the Parity Wallet library contract into a regular multi-sig wallet and become an owner of it by calling the initWallet function.”
Around 584 wallets have been affected, however, their total amount is unknown. Private researchers have put the affected amount in ETH anywhere from $150 million to over $300 million, but Parity has called this figure speculative. It is expected that most of the affected wallets belong to companies as multi signature wallets are predominantly used in the corporate world as they add extra security of only confirming transactions after multiple verifications.
After the news broke, Devops199 came forward suggesting that they accidentally triggered the bug. Following the reports, the user was even worried on GitHub if there would be any involvement of law enforcement.
In an email to Wccftech, Cappasity – a platform for 3D/AR/VR content production and exchange – says that Devops199’s actions may not be accidental. The company’s wallet was one of the affected as it was frozen due to the multi-sig vulnerability. “Our internal investigation has demonstrated that the actions on the part of devops199 were deliberate,” the company writes, mentioning the number of calls executed by the user.
“When you are tracking all their transactions, you realize that they were deliberate,” the statement says. “Therefore, we tend to think that it was not an accident.”
It is too early to suggest if these actions were indeed deliberate since Parity is yet to comment on this development. However, Cappasity added that contacting law enforcement agencies will be the right next step “if the situation is not successfully resolved in the nearest future”. Devops199’s account has since been deleted.
Source: https://wccftech.com/frozen-300-million-eth-was-no-accident/
What do you think about this? Is there something fishy about the frozen $300 Million ETH?
The problem stems from another bug that was discovered in July and during its fix a new flaw was left in the code. “Following the fix for the original multi-sig issue that had been exploited on 19th of July (function visibility), a new version of the Parity Wallet library contract was deployed on 20th of July,” Parity wrote in its advisory. “However that code still contained another issue – it was possible to turn the Parity Wallet library contract into a regular multi-sig wallet and become an owner of it by calling the initWallet function.”
Around 584 wallets have been affected, however, their total amount is unknown. Private researchers have put the affected amount in ETH anywhere from $150 million to over $300 million, but Parity has called this figure speculative. It is expected that most of the affected wallets belong to companies as multi signature wallets are predominantly used in the corporate world as they add extra security of only confirming transactions after multiple verifications.
After the news broke, Devops199 came forward suggesting that they accidentally triggered the bug. Following the reports, the user was even worried on GitHub if there would be any involvement of law enforcement.
In an email to Wccftech, Cappasity – a platform for 3D/AR/VR content production and exchange – says that Devops199’s actions may not be accidental. The company’s wallet was one of the affected as it was frozen due to the multi-sig vulnerability. “Our internal investigation has demonstrated that the actions on the part of devops199 were deliberate,” the company writes, mentioning the number of calls executed by the user.
“When you are tracking all their transactions, you realize that they were deliberate,” the statement says. “Therefore, we tend to think that it was not an accident.”
It is too early to suggest if these actions were indeed deliberate since Parity is yet to comment on this development. However, Cappasity added that contacting law enforcement agencies will be the right next step “if the situation is not successfully resolved in the nearest future”. Devops199’s account has since been deleted.
Source: https://wccftech.com/frozen-300-million-eth-was-no-accident/
What do you think about this? Is there something fishy about the frozen $300 Million ETH?
Jump to: