Arbitrum’s on‑chain Security Council emptied a wallet tied to Binance’s recent hot‑wallet breach on Oct. 30, moving 74,559,805.2 ARB and roughly 8,426 ETH. The council acted without the address’s private key, invoking powers granted by the ArbitrumDAO governance framework, according to a detailed walkthrough posted by user Zephylx on the Ethereum Magicians forum and reported by Unchained.

ETH / USD
Source: CoinGecko. Prices are indicative.

How the freeze was executed

The council’s Safe, which currently requires nine of its twelve signers, called Arbitrum’s UpgradeExecutor in a single Ethereum transaction (block 26301886). The executor temporarily ran override code that logged the target address as the message sender before restoring the original code. Two subsequent type‑0x65 transactions on Arbitrum One, each with zeroed signature fields, transferred the ARB first and the ETH second to a holding address ending in 0DA0. The on‑chain data matches Zephylx’s analysis, showing the moves occurred 9 minutes 45 seconds after the Ethereum transaction.

Governance context and prior precedent

Offchain Labs co‑founder and CEO Steven Goldfeder explained in a July interview with Unchained that the council’s authority to act in emergencies is by design, describing it as an “external entity” broadly elected by the DAO. The same council performed a similar freeze in April, moving more than 30,765 ETH from a KelpDAO‑related address on Arbitrum One. In both cases, the council’s notice emphasized that the funds could only be moved by an ArbitrumDAO governance vote coordinated with relevant parties, and that no other users’ assets were affected.

Implications for developers and users

Zephylx warned that on chains where upgrade paths are controllable, promises that only a private key can move a wallet may not hold. The incident underscores the power of DAO‑granted emergency mechanisms, which can supersede traditional key‑based security. While the council published both actions within an hour and a half and reported no bugs, the freeze has reignited debate over the balance between decentralised governance and user sovereignty on layer‑2 solutions.

What to watch next

Stakeholders will monitor any formal response from Binance regarding the frozen assets and whether the exchange seeks restitution through Arbitrum’s governance process. Offchain Labs may face pressure to clarify the scope of the Security Council’s powers and to outline safeguards against potential misuse. Finally, developers building on Arbitrum and other rollups are likely to reassess contract designs that assume immutable key‑only control, potentially prompting broader discussions on upgradeability and emergency governance across the ecosystem.