Arbitrum DAO has opened a constitutional vote on whether to approve the release of 30,766 ETH that was frozen in the aftermath of an attack involving Kelp’s rsETH liquid restaking token. The proposal, now live for delegate voting, represents one of the largest single-asset governance decisions in Arbitrum’s history.
What the proposal asks delegates to approve
The constitutional AIP posted on the Arbitrum governance forum requests that the DAO approve the release of 30,766 ETH that was frozen following the Kelp-related incident. Because this is a constitutional proposal, it carries a higher approval threshold than standard governance votes.
The vote is currently listed on Arbitrum’s Tally governance page, where delegates can cast their ballots. The proposal has not yet been approved; it is an active vote, and the outcome remains undetermined.
The distinction matters. No ETH has been released. The DAO is being asked to authorize the transfer, not ratify one that already happened.
How the Kelp rsETH incident led to frozen funds
The frozen ETH traces back to an incident involving Kelp’s rsETH, a liquid restaking token. An rsETH incident report filed on the Aave governance forum on April 18, 2026, documented the event that triggered the freeze.
The attack’s aftermath left a significant amount of ETH locked in a state that required DAO-level governance action to unlock. The proposal frames the release as a necessary step to resolve the situation for affected parties within the Arbitrum ecosystem.
Kelp operates as a liquid restaking protocol, and its rsETH token is used across multiple DeFi platforms. When the incident occurred, it created downstream effects that reached into Arbitrum-based protocols, similar to how recent key leak incidents have forced emergency bridge transfers across ecosystems.
Why 30,766 ETH makes this vote significant
The scale of the proposed release is substantial. At current market prices, 30,766 ETH represents a significant portion of ecosystem value, making this one of the larger disbursement decisions any Layer 2 DAO has faced.
Constitutional proposals on Arbitrum require a higher quorum and approval threshold than standard votes. This procedural elevation reflects the magnitude of the decision and its potential to set precedent for how the DAO handles attack-related fund releases in the future.
The governance debate touches on a core tension in DAO treasury management: whether ecosystem support after security incidents should take priority over conservative treasury stewardship. The outcome could influence how other DAOs approach similar situations, particularly as DeFi protocols become more interconnected across Layer 2 networks.
This decision arrives during a period of broader market activity, with recent ETF outflows showing 41,275 ETH leaving Ethereum ETFs, adding context to the scale of capital movements in the Ethereum ecosystem.
What delegates and token holders should watch
The vote is live on Tally, and delegates can currently cast their ballots. Token holders who have delegated their voting power should verify their delegate’s position on the proposal.
If the proposal passes, additional execution steps may be required before any ETH is actually transferred. Constitutional AIPs on Arbitrum typically include a timelock period between approval and execution, giving the community a final window to raise objections.
If it fails, the frozen ETH remains locked, and proponents would need to draft a revised proposal addressing delegate concerns before resubmitting. The governance process on Arbitrum allows for proposal iteration, but each attempt requires meeting the same constitutional thresholds.
Delegates weighing their vote may also consider the broader DeFi security landscape, where incidents like the growing investment in Solana’s DeFi infrastructure reflect how ecosystem resilience is becoming a competitive differentiator across chains.
FAQ: Arbitrum DAO vote and Kelp attack aftermath
What is the Arbitrum DAO voting on?
The DAO is voting on a constitutional AIP to approve the release of 30,766 ETH that was frozen after the Kelp rsETH incident. The proposal is live on Tally for delegate voting.
Why is 30,766 ETH being discussed?
That amount was frozen as a result of the Kelp rsETH attack and its aftermath. Releasing it requires explicit DAO approval through a constitutional governance vote.
Has the ETH release already been approved?
No. The vote is currently active. No ETH has been released. The proposal must pass the constitutional approval threshold before any funds can move, and execution typically includes an additional timelock period.
How could the Kelp attack aftermath affect Arbitrum users or builders?
The immediate impact centers on whether affected parties receive the frozen ETH. The longer-term effect is precedential: the vote’s outcome will shape expectations for how Arbitrum’s DAO handles future security incidents involving cross-protocol assets on its network.
Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.








