Defending Centralized Actions in Blockchain Governance
David Schwartz, former Chief Technology Officer of Ripple, has come to the defense of the recent actions taken by the Arbitrum Security Council in response to the KelpDAO exploit. This incident led the council to freeze a substantial 30,766 ETH linked to the malicious actors without disrupting the integrity of the overall network. However, these emergency measures have sparked significant debates regarding the potential risks of centralization in blockchain governance.
Criticism from the Community
Critics, including notable figures like Satoshi Nakamoto, voiced concerns that the Security Council’s authority enables them to impose changes on the network without obtaining consent from individual node operators, who would not be required to download any new software updates. Nakamoto highlighted a coercive aspect to the council’s power regarding smart contract upgrades at the layer one (L1).
Historical Precedents in Blockchain
In contrast, Schwartz argues that the Emergency Council’s intervention reflects a historical precedent in blockchain. He referenced a pivotal moment in Bitcoin’s history, often referred to as the “value overflow incident,” when an exploit allowed the minting of over 184 billion BTC indiscriminately. In that situation, the early Bitcoin developers, along with Satoshi Nakamoto, responded by releasing a corrective patch, which led to an agreement among node operators to effectively rewind the blockchain’s history.
“This is precisely what occurred in Bitcoin after the overflow incident.”
Schwartz emphasized that the Arbitrum community faced a network status they deemed unacceptable, thereby justifying the council’s actions to restore legitimacy. Ultimately, he asserts that decentralized governance encapsulates making necessary changes when the consensus appears flawed—a scenario that affirms the adaptive nature intrinsic to blockchain networks.
