Arbitrum’s Security Council has initiated a non-emergency governance action to correct a discrepancy in Delegated Voting Power, or DVP, in the ARB token contract. The action would reduce the contract’s recorded total DVP by roughly 51.17 million ARB.

According to a proposal posted on the Arbitrum governance forum, the contract currently records total Delegated Voting Power of about 5.459 billion ARB. That figure is approximately 51.17 million ARB higher than it should be, representing less than one percent of the recorded total, with the mismatch attributed to estimates used during the initial initialization process.

The proposal is framed as a correction to an aggregate governance accounting figure rather than a change affecting tokenholder assets. The action does not change individual ARB balances, does not alter delegation distributions, and does not require users to take any action. Instead, it corrects the total recorded value used by the contract for Delegated Voting Power.

The non-emergency security action is described in the Arbitrum governance forum proposal: Non-Emergency Security Action to Correct Total DVP.

Delegated Voting Power and DAO Governance

Delegated Voting Power is a core component of DAO governance. Tokenholders do not necessarily vote directly on every governance proposal. In many cases, they delegate their voting power to representatives, delegates, or organizations they trust to participate in governance processes on their behalf. Arbitrum, one of the largest Ethereum Layer 2 scaling networks by total value locked, uses ARB token voting to govern protocol decisions through its DAO structure.

The total recorded amount of voting power is used by governance systems to track participation, quorum, proposal outcomes, and the overall integrity of governance procedures. If the aggregate figure is incorrect, even when individual balances and delegation assignments are not affected, the recorded total still needs to be corrected so the governance system reflects the proper amount.

In Arbitrum’s case, the reported discrepancy is not described as extra tokens being issued to any party. It is also not described as a reassignment of delegations or a wallet-draining vulnerability. The issue concerns an accounting mismatch in the recorded total Delegated Voting Power.

The correction is intended to bring the contract’s aggregate DVP figure in line with the amount that should have been recorded, reducing the overstatement by about 51.17 million ARB.

Non-Emergency Process

The action has been categorized as non-emergency. In DAO governance, technical or contract-related corrections can vary in urgency. Some require immediate intervention when user funds or protocol operations are at risk, while others can proceed through a slower and more transparent process.

According to the forum notes, execution of the correction takes approximately 14 days. That timeline gives the Arbitrum community time to review the proposed action, understand the source of the discrepancy, and assess the limited scope of the change before it is executed.

The description of the action emphasizes that the correction is narrowly focused on the recorded aggregate DVP value. It does not affect ARB balances held by users and does not modify how existing voting power has been delegated.

Security Council Role

Arbitrum’s Security Council is responsible for handling certain protocol and governance actions, particularly where technical execution or security-sensitive changes are involved. In DAO structures, such councils can play a role in implementing defined actions when full governance processes may be slower or less practical for technical fixes.

That role can raise governance questions because it places responsibility for specific actions in the hands of a smaller group. The governance process relies on transparency around the scope, rationale, and impact of actions taken by such bodies.

In this instance, the forum post identifies the discrepancy, states the size of the correction, and says user balances and delegation distributions remain unaffected. Those details define the action as a recorded-total correction rather than an alteration of economic rights or voting assignments.

Governance Record Maintenance

DAO governance systems require ongoing maintenance of records and contract parameters. Smart contracts are deployed, initialization values are set, delegation systems operate over time, token supply conditions may change, and upgrades can occur. In that environment, mismatches can appear between what a system records and what it should record.

Such discrepancies do not necessarily mean that malicious activity occurred. They may reflect technical or administrative issues that require correction through established governance procedures.

Traditional organizations maintain corporate records, shareholder registries, audits, and administrative correction processes. DAOs use smart contracts, governance forums, multisignature arrangements, token voting systems, and security councils. The mechanisms differ, but accurate records remain important for governance operations.

The Arbitrum DVP action fits into that category of governance maintenance. It is intended to correct an overstated aggregate voting-power figure while leaving individual user balances and delegation distributions unchanged.

For ARB holders, the proposal states that no user action is required. Holders’ ARB balances are not reduced by the correction, and delegated voting power allocations are not being redistributed. The recorded total is being adjusted to remove the overstatement created by the initial initialization estimates.

The scale of the adjustment, roughly 51.17 million ARB, may appear large when viewed in isolation. The relevant scope, however, is the aggregate Delegated Voting Power value recorded by the contract, not individual token balances or wallet holdings.

The action is being conducted through a disclosed, non-emergency process and is based on information released in the Arbitrum governance forum proposal for correcting total Delegated Voting Power.