David Schwartz is pushing back against criticism of Arbitrum’s recent emergency intervention, arguing that freezing funds tied to the KelpDAO exploit is not a betrayal of decentralization but part of a long‑established pattern in crypto – one that goes back to Bitcoin’s own early history.
The Ripple CTO drew a direct line between Arbitrum’s decision to lock more than 30,000 ETH and Bitcoin’s response to the infamous 2010 value overflow bug, when the network effectively agreed to roll back the chain after an attacker created an impossible number of coins.
Arbitrum’s freeze after the KelpDAO exploit
The controversy began when Arbitrum’s Security Council stepped in to freeze 30,766 ETH associated with the KelpDAO exploit. The move ring‑fenced the suspected stolen funds, preventing them from being moved or laundered further, while leaving the broader network state and user balances intact.
Supporters saw the intervention as a targeted safety measure: the Security Council used its upgrade authority to halt the exploiter’s assets before they could vanish across multiple chains. From their perspective, the decision protected honest users and reduced systemic risk without resorting to a full network fork.
But the action immediately reignited an old fault line in crypto: how much power should small governance bodies have, and where is the line between pragmatic security and creeping centralization?
Centralization fears surface
Critics argued that the freeze exposes the concentration of authority inside Arbitrum’s current governance model. The Security Council can modify core smart contracts at the Ethereum base layer without requiring every node operator to install new software or adopt a fork.
One detractor, using the name Nakamoto in the report, called that ability “a coercion mechanism that has absolutely nothing to do with decentralisation,” arguing that if a small group can unilaterally change contract logic and lock assets, the system’s decentralization exists more on paper than in practice.
This line of criticism focuses less on the specific exploit and more on the precedent: if a council can freeze these funds today, what else might it be able to do tomorrow? For some purists, any form of emergency override is indistinguishable from centralized control.
Schwartz: this is how Bitcoin handled a crisis
Schwartz countered that framing by putting Arbitrum’s actions in historical context. He highlighted Bitcoin’s 2010 overflow incident, when a bug allowed an attacker to mint more than 184 billion BTC – a number that plainly violated the protocol’s supply rules.
In response, Satoshi Nakamoto and early Bitcoin developers produced a patch that treated the offending transaction as invalid. Node operators adopted the updated software, effectively discarding the chain segment that included the exploit. The network “rolled back” to a prior state and continued as if the overflow had never happened.
In a post on X, Schwartz argued that Arbitrum’s freeze operates on the same principle. In both cases, participants look at a network state – one with billions of illegitimate BTC or tens of thousands of exploited ETH – and collectively decide they do not accept it as valid. They then coordinate to restore what they believe is the legitimate ledger.
“This is exactly what bitcoin did in response to the overflow incident,” he wrote, emphasizing that node operators in 2010 “rejected the database state produced by the existing rules and chose to change those rules.”
Voluntary coordination vs coercion
A key part of Schwartz’s defense is the idea that no one is literally forced to accept the new state. In Bitcoin’s overflow episode, any node operator could have refused to install the patch and continued following the chain with 184 billion invalid coins. In practice, the overwhelming majority switched to the patched version, and the minority chain with the bugged state became irrelevant.
Schwartz presented this as evidence of how decentralization actually functions in real networks: not as a rigid refusal to ever intervene, but as a process in which users, operators, and developers can collectively reject outcomes they regard as illegitimate.
Applied to Arbitrum, his argument is that the Security Council did not “override” decentralization so much as act as an execution arm for a community that did not want an exploit‑driven state to stand. The legitimacy, in this framing, comes from broad social consensus rather than from the absence of any special powers.
The governance dilemma on modern L2s
The Arbitrum episode underscores a structural reality for most modern layer‑2 networks and DeFi protocols: emergency powers do exist, often by design. Upgradeable contracts, multisig councils, and timelocked admin keys are built in to allow teams to patch severe vulnerabilities, stop ongoing thefts, or upgrade critical infrastructure.
Proponents say these mechanisms are a necessary compromise. Without them, protocols can be slow to react to exploits, with millions in user funds drained before any protective measure is enacted. With them, project teams and councils can respond in minutes or hours instead of days or weeks.
Yet, that same flexibility is exactly what unnerves decentralization maximalists. If an admin key can freeze assets, it could also be used – now or in the future – to censor users, selectively reverse transactions, or bend governance outcomes. The risk is not only malicious intent, but also regulatory pressure, legal mandates, or social capture.
Arbitrum’s Security Council occupies that contested space: powerful enough to act quickly, but therefore also powerful enough to alarm those who want protocol rules to be effectively unchangeable.
Is every emergency action a step away from decentralization?
Schwartz’s comments probe a deeper philosophical question: does decentralization mean “no one can ever change anything,” or does it mean “no one can be forced to accept changes they don’t agree with”?
Under the stricter view, any privileged mechanism – a council, an admin key, a governance multisig – is incompatible with true decentralization. The protocol should be ossified, and only voluntary adoption of new, separate software (a fork) should change the rules.
Under the more flexible view that Schwartz articulates, decentralization is preserved as long as participants are free to accept or reject the outcome. The fact that a coordinated group proposes or implements an emergency measure does not by itself violate decentralization; what matters is whether the wider community can credibly say “no” by refusing to follow it.
Bitcoin’s 2010 rollback is frequently cited as a canonical example of this softer, social conception of decentralization. Schwartz is now arguing that Arbitrum’s freeze sits within that same tradition, even if the mechanism – a council freezing funds via smart contract logic – looks more formalized and immediate.
KelpDAO exploit as a stress test for cross‑chain security
The KelpDAO exploit that triggered the freeze also highlights another growing challenge: how to handle stolen assets that move swiftly across different chains and protocols. In the current landscape, stolen funds can be bridged, swapped, and obfuscated in minutes, making traditional incident response playbooks far less effective.
Arbitrum’s rapid intervention shows one emerging model: use privileged governance mechanisms to halt suspect funds before they fully disperse. Other networks and protocols have experimented with temporary pauses, circuit breakers, or blacklisting features built into token contracts.
Each such incident forces a similar debate. On one hand, swift freezes can prevent cascading losses and protect end users who had no part in the exploit. On the other, every successful use of emergency controls makes it harder to argue that a system is governed solely by immutable code and open consensus.
The widening debate across blockchains
Arbitrum is not alone in facing these tensions. Every major blockchain ecosystem is wrestling with variations of the same question: how to balance safety, legal pressure, user expectations, and decentralization ideals.
Some communities are moving toward more formal, on‑chain governance frameworks, where emergency actions require quorum, timelocks, and transparent procedures. Others are gradually phasing out admin keys and upgradeable contracts, accepting slower or riskier responses to exploits in favor of removing centralized choke points.
Events like the KelpDAO exploit and Arbitrum’s subsequent freeze tend to harden views on both sides. Advocates of intervention point to users who would otherwise lose life‑changing sums due to protocol bugs or governance oversights. Opponents warn that once powers exist, they are rarely used just once, and external actors – including regulators and courts – may eventually demand their use.
How this shapes Arbitrum’s future
For Arbitrum, the fallout from the freeze will likely influence its governance roadmap. The Security Council’s ability to act decisively is now proven – but so are the anxieties that ability creates. Future design choices may focus on limiting when and how such powers can be invoked, increasing transparency, or shifting more control to broader tokenholder votes.
Questions that will likely surface include:
– Should emergency actions require multi‑stage approvals or community ratification after the fact?
– How narrowly should interventions be defined – for example, only affecting clearly illicit funds?
– At what maturity point should a network retire or significantly constrain its emergency levers?
Schwartz’s line of defense suggests that, at least in his view, these powers can coexist with decentralization if they are understood as expressions of community will rather than unilateral decrees.
A long‑running ideological split
In the end, Schwartz’s comparison to Bitcoin’s 2010 rollback situates Arbitrum’s decision within crypto’s longest‑running argument: is “code is law” an absolute rule, or a starting point that communities can override in extreme cases?
On one side stand those who prioritize survivability, user protection, and system integrity – even if that means occasionally intervening in ways that resemble traditional power structures. On the other side are those who see any such override as incompatible with the foundational promise of permissionless, uncontrollable networks.
By aligning Arbitrum’s actions with Bitcoin’s early history, Schwartz is making a clear statement: emergency interventions are not an aberration in crypto, but part of how decentralized systems have always dealt with existential flaws. Whether the broader community agrees – and how networks formalize or constrain these powers going forward – will shape the next phase of blockchain governance.