Arbitrum's Security Council has kicked off a non-emergency governance action to patch a discrepancy in the Delegated Voting Power recorded on the ARB token contract. The gap totals roughly 51.17 million ARB — meaning the system was showing about 5.459 billion ARB in delegated voting power when the real figure should have been lower. The error traces back to estimates made during the contract's initial setup.
What went wrong with the voting numbers
The problem is a bookkeeping mismatch, not a loss of tokens. The council’s forum post explains that the initialization process used estimates that didn't perfectly align with actual delegation data. The result: the on-chain tally overstated the total delegated voting power by roughly 1% of the recorded amount. No individual ARB balances were affected, and delegation distributions remain exactly as users set them.
What the fix does — and doesn't do
This is purely a governance-accounting adjustment. It won't touch anyone's wallet or shift voting weight around. Users don't need to do a thing — no signature, no transaction, no claim. The correction just brings the contract's internal book of record into line with reality. The council stressed that the change is non-emergency, meaning it's not a response to an exploit or active threat.
Why the Security Council handled it
Arbitrum's Security Council exists specifically to manage protocol-level and governance actions, especially those that are technical or security-sensitive. Correcting a contract parameter that inflates voting power fits squarely in that mandate. The council can move faster than a full DAO vote on certain adjustments, but they still chose the non-emergency route, which means the fix gets a 14-day execution window rather than being applied overnight.
The clock is now running. The correction will take effect once the 14-day period elapses, assuming no further issues surface. For now, the DAO's voting dashboard should start reflecting accurate totals after the patch goes live.
