David Schwartz defends Arbitrum’s suspension by citing the 2010 Bitcoin reversal
Ripple CTO David Schwartz has defended Arbitrum’s decision to freeze more than 30,000 ETH linked to the recent KelpDAO exploit.
Summary
- David Schwartz said that Arbitrum’s emergency ETH freeze followed the same logic as Bitcoin in 2010.
- The freeze secured 30,766 ETH linked to the KelpDAO exploit without changing the state of the wider Arbitrum network.
- Critics say the Security Council’s intervention has raised new concerns about governance and emergency powers.
He said the move is comparable to Bitcoin’s response to the 2010 value overflow bug, where the network accepted a refund after an attacker created billions of coins.
The comments came after the Arbitrum Security Council intervened to stop the 30,766 ETH tied to the exploiter. The move protected funds without changing the broader nature of the network, but it also reignited the debate over decentralization and emergency management.
Schwartz links the Arbitrum act to the history of Bitcoin
Schwartz said Arbitrum’s response should not be seen as a break in the terms of the separation. He pointed out that communities can reject the state of the network that they see as wrong and take steps to correct it.
He pointed to the Bitcoin overflow incident of 2010, where an attacker made more than 184 billion BTC due to a bug. Satoshi Nakamoto and the original developers released a patch, and the node operators took it, which led to a backlash on the chain.
In an article on X, Schwartz said, “This is what bitcoin did in response to the overflow event.” He said the node operators at that time rejected the database situation produced by the existing laws and chose to change those laws.
Schwartz added that no one was forced to accept that blockchain precedent. He said that process shows how fragmented networks work when users no longer accept the result produced by consensus.
The Arbitrum freeze has drawn criticism for being centralized
The Arbitrum Security Council froze 30,766 ETH after the KelpDAO exploit. Supporters say the move helped protect the stolen funds quickly and avoided major damage to the ecosystem.
Critics say the move raised concerns because the council could develop smart contracts on Ethereum’s base layer without requiring every node operator to download a fork of the new software. That power has led some users to question how the network is still being used.
Another critic, identified as Nakamoto in the report, said, “The Security Council has the ability to develop a smart contract on L1, which is a binding mechanism that has nothing to do with decentralization.”
That criticism centered on whether minority-controlled emergency powers could fit into a decentralized model. The issue has become a point of debate across blockchain networks after massive exploitation.
The exploitation of KelpDAO pushed governance questions into focus
The KelpDAO exploit started a wider discussion about how networks should respond when stolen funds move rapidly across chains. In the case of Arbitrum, the council acted by suspending ETH without waiting for a comprehensive governance process.
Schwartz said the Arbitrum community was confronted with what it considered an illegal domain, and the council responded to restore peace. He said this action shows the choice of the community rather than rejecting the expansion of people.
His defense placed Arbitrum’s decision at the center of the long-running crypto debate. On the other hand, there are those who support urgent intervention to recover the funds. On the other side are those who argue that such power weakens the core concept of partition control.
