Arbitrum's latest governance thread matters because it moves the rsETH response from freeze mechanics to release mechanics. Radar reads that as a live protocol-ops question about how immobilized exploit proceeds are turned into actual recovery capital.
This is not a price story and not a generic post-mortem. It is a governance-routing story about whether the chain sends already-frozen ETH into the coordinated remediation path and on what terms.
What Happened
The official Arbitrum forum shows a Constitutional AIP published on April 25 asking governance to release 30,765.67 ETH frozen by the Security Council after the rsETH exploit into the coordinated recovery effort.
The proposal says the funds would move from the immobilized address to a designated 2-of-3 recovery safe with signers from Aave, KelpDAO and Certora, and frames the release as a one-time measure because the funds are already secured and the destination is the main remaining governance decision.
Why It Matters
For Radar, the signal is that governance is now deciding how frozen enforcement action becomes active remediation. That is a different stage of protocol response, and it matters because routing and indemnity design can determine whether secured funds actually reduce ecosystem damage in time.
The proposal also clarifies that Arbitrum is not being asked for a fresh treasury outlay. It is being asked to authorize the use of ETH already frozen onchain, which sharpens the real question to governance process, recipient controls and recovery coordination.
That makes this useful for protocol researchers following how chains handle seized or immobilized assets after a cross-protocol exploit, especially when multiple parties need to agree on destination, oversight and legal protection before release.
What To Watch Next
Watch how delegates respond to the release destination, the indemnity structure and the proposal's claim that sending the ETH into coordinated recovery is better than leaving it frozen.
The next useful checkpoint is whether a temperature check happens before onchain submission and whether the recovery path stays clearly bounded to rsETH remediation rather than becoming a broader governance precedent.
This stays on Radar because release design is where chain governance, recovery coordination and user-outcome logic all meet.
Continue this cluster
The response-and-chain-ops watch is most useful when governance routing, emergency coordination and live infrastructure changes are read as one connected operating surface.
