What happened with Arbitrum and the $71 million ETH freeze?

Arbitrum intervened after the KelpDAO exploit by freezing over 30,000 ETH linked to the attacker. The funds were moved into a controlled wallet to prevent laundering. The action was taken by the network’s Security Council as an emergency response.

What is Arbitrum’s Security Council and what does it do?

The Security Council is a group of 12 members elected by token holders every six months. It has special powers to act quickly during emergencies, including moving or locking funds. This structure is designed to protect the network during critical incidents.

How did the “freeze” of ETH actually work?

The freeze was not passive—it involved actively transferring funds from the attacker’s wallet into a wallet with no owner. This made the funds immobile and inaccessible. It required privileged permissions not available to regular users.

Why is this causing a debate about decentralisation?

Critics argue that if a small group can override transactions, the system is not fully decentralised. True decentralisation implies no one can interfere once transactions are executed. This event challenges the idea of “code is law” in blockchain systems.

What is the main argument in favour of Arbitrum’s decision?

Supporters say the intervention prevented tens of millions of dollars from being laundered and protected users. Without action, the funds could have been lost permanently. They see it as a necessary tradeoff between security and decentralisation.

What are the main concerns raised by critics?

Critics worry about precedent—if funds can be frozen in one case, the same power could be used in other situations. This could include regulatory pressure or political influence. The concern is about where the line is drawn and who decides.

Why didn’t Arbitrum use full DAO governance for this decision?

According to Steven Goldfeder, consulting the DAO would have slowed the process and potentially alerted attackers. Speed was critical to prevent further fund movement. He argued that delay would have made intervention ineffective.

How does this reflect on Layer 2 blockchain design?

Layer 2 networks like Arbitrum often balance scalability and security with some level of governance control. This incident shows that decentralisation on L2s can involve delegated authority rather than full autonomy. It highlights design tradeoffs in scaling Ethereum.

Arbitrum freeze sparks decentralisation debate after hack

Written by Isaac FrancisPublished Apr. 24 2026Last Updated Apr. 24 2026

The Arbitrum Security Council intervened to freeze more than 30,000 ETH, worth about $71 million, linked to the KelpDAO exploit.

The emergency action prevented the attacker from moving funds but raised concerns over whether a small elected group can override transactions in a supposedly decentralised system.

“The default was do nothing,”

Said Steven Goldfeder.

The intervention involved transferring funds from the attacker’s address into a wallet with no owner, effectively locking them and buying time for further governance decisions.

Supporters argued the move demonstrated a necessary security mechanism, while critics said it undermines the principle that blockchain transactions should be immutable and beyond human intervention.

Patrick McCorry said the Security Council is transparent and elected by token holders, positioning it as a community-mandated safeguard rather than a central authority.

The incident has intensified debate over the balance between decentralisation and security on Layer 2 networks, with questions growing around governance, precedent and who ultimately controls blockchain systems.

At the time of reporting, Ethereum price was $2,323.50.