Community debate erupts over Arbitrum Security Council’s emergency powers after recent freezes

- Arbitrum’s Security Council used emergency powers on April 21, 2026 to freeze 30,765.67 ETH after the KelpDAO exploit, triggering a governance debate. - The most cited figure was 30,765.6675 ETH, moved to Arbitrum’s intermediary frozen wallet after an atomic inbox-contract upgrade, forum records show. - Arbitrum governance must approve any release of the frozen ETH through a constitutional AIP now on the forum.

Arbitrum’s Security Council froze 30,765.6675 ETH on April 21, 2026 after the KelpDAO exploit, according to an official post on the Arbitrum governance forum. The funds were moved to Arbitrum’s intermediary frozen wallet at `0x0000000000000000000000000000000000000DA0`, and the forum post said a later governance action would be required to release them. The move has since become the focus of a broader argument across X, governance threads and security discussions over how much emergency power a decentralized network should delegate to a small elected body. April 21 forum comments captured both sides of that argument almost immediately. One commenter said the Security Council was “a feature WE ALL KNOW ABOUT” and welcomed the intervention after a theft, while another said the action “created a precedent” because ETH was moved on Arbitrum without the user’s consent and asked for clearer rules on when such powers can be used. (forum.arbitrum.foundation) ### How did the Security Council actually freeze the ETH? The April 21 announcement said the Security Council executed “an emergency action” at 11:26 p.m. ET to freeze ETH held by the KelpDAO exploiter on Arbitrum One. The post said the council used an atomic action to upgrade the inbox contract on Ethereum, impersonate the exploiter address through a new function, transfer the funds, and then restore the contract to its original implementation. (forum.arbitrum.foundation) Arbiscan records show the transfer into the frozen wallet was completed on April 21, 2026 at 03:35:08 UTC. The explorer lists the value at 30,765.667401709008927568 ETH and tags the destination as “Arbitrum: Intermediary Frozen Wallet.” ### Why are people arguing about decentralization now? Arbitrum’s own governance design gives the Security Council unusual emergency authority. (forum.arbitrum.foundation) The governance docs describe the council as a 12-member body elected by the DAO to manage risk through “selective application of emergency actions,” and the docs say any 9 of 12 members can make an upgrade with no delay in an emergency. (arbiscan.io) That structure is central to the current dispute. Critics in the forum did not dispute that the council exists; they questioned the threshold for intervention, the role of outside authorities, and what safeguards prevent abuse after a body with emergency powers demonstrates it can move funds. Supporters, in the same thread, said the mechanism worked as designed and reduced losses after an exploit. (docs.arbitrum.foundation) ### What was the underlying incident tied to KelpDAO? A constitutional proposal filed on April 25 said Aave Labs, KelpDAO, LayerZero, EtherFi and Compound were working on a coordinated recovery effort for affected rsETH holders. The proposal cited LlamaRisk’s April 20 incident report, which said the KelpDAO rsETH Unichain-to-Ethereum route released 116,500 rsETH on Ethereum without a corresponding burn on the source side, creating an estimated backing shortfall of about 76,127 rsETH. (forum.arbitrum.foundation) The same proposal said the frozen ETH represented a “material contribution” toward restoring rsETH backing. It also said the release destination, not the freeze itself, had become the remaining governance question because the assets were already immobilized. ### What happens to the frozen ETH now? Arbitrum’s April 21 announcement said any release would require a subsequent governance action. (forum.arbitrum.foundation) On April 25, a constitutional AIP asked the DAO to approve sending the frozen ETH into a 2-of-3 Gnosis Safe for the recovery effort, with signers from Aave, KelpDAO and Certora. The proposal remains the next concrete milestone in the story. (forum.arbitrum.foundation) Arbitrum’s forum says the Security Council emergency-action post was published on April 21, and the release proposal was posted four days later by Aave Labs with KelpDAO, LayerZero, EtherFi and Compound named as participants in the remediation effort. (forum.arbitrum.foundation)

Get your own daily briefing

Scout delivers personalized news, insights, and conversations tailored to your role and industry.

Download on the App Store

Shared from Scout - Be the smartest in the room.