Core DAO Prepares Emergency Hard Fork After Validators Drew Excess CORE Rewards

Core DAO has begun coordinating an emergency hard fork after a group of validators managed to claim significantly more CORE rewards than the blockchain’s protocol intended to issue, forcing several major exchanges to suspend token transfers while the network prepares its fix.

The Bitcoin-adjacent EVM chain confirmed the incident had been contained and that the offending validators could no longer draw excess rewards, but the episode has already disrupted CORE trading across at least four exchanges and raised fresh questions about reward-distribution security on proof-of-stake networks.

## What happened on Core

In a status update published on Monday, Core DAO said a small number of validators had accrued rewards “significantly above” the protocol’s intended issuance. The project stressed that the incident was limited to reward issuance and that user assets remained safe throughout.

A follow-up update confirmed that the malicious validators had been contained and outlined the response plan: an emergency hard fork described as a forward upgrade. Critically, the fork will not roll back the network or reverse any previously confirmed transactions, meaning all on-chain activity remains final.

Core has not yet disclosed how much CORE was actually issued in excess, how long the activity continued, or whether any of the additional tokens entered open circulation. The project also has not explained the specific vulnerability that allowed the validators to obtain the rewards in the first place. A technical postmortem has been promised.

## Exchanges move quickly to suspend CORE

The incident triggered an immediate operational response from centralized exchanges that list CORE.

Coinbase paused both sends and receives on the Core network, according to the exchange’s status page. Korean exchanges Bithumb and Coinone suspended CORE deposits and withdrawals, citing suspected and confirmed security concerns respectively.

Bitget also halted CORE deposits and withdrawals, attributing the suspension to wallet maintenance, while LBank suspended deposits due to what it described as requirements from the project itself.

The pattern is familiar from previous chain-level incidents: when uncertainty around a network’s token issuance or integrity emerges, exchanges move first and ask questions later. For CORE holders, that means reduced liquidity and withdrawal friction until the fork ships and platforms confirm normal operations.

## Forward fork, no rollback

Core’s decision to frame the emergency hard fork as a forward upgrade rather than a rollback is significant. Rollbacks, which reverse confirmed transactions, are among the most controversial moves a blockchain can make, and they typically inflict lasting damage on a network’s credibility.

By patching the reward issuance mechanism going forward and leaving historical transactions untouched, Core is betting that a clean surgical fix preserves more trust than a deep rewrite. The trade-off is that if excess CORE already entered circulation and cannot be reversed, the supply overhang question will linger until the postmortem clarifies the numbers.

## A recurring lesson for proof-of-stake chains

The Core incident is the latest reminder that reward distribution logic is attack surface. While the project has labelled the actors “malicious validators,” the fact that validators could exceed intended issuance points to a protocol-level flaw rather than a simple key compromise.

For other EVM-compatible chains running delegated staking models, the checklist that follows such incidents is standard: audit reward calculation paths, cap per-validator issuance, add anomaly detection on reward claims, and prepare a tested emergency-fork procedure that can ship within days rather than weeks.

Core, which markets itself as a Bitcoin-aligned network combining proof-of-work delegation with proof-of-stake validation, now faces the added burden of demonstrating that its dual-consensus design did not contribute to the failure.

## What comes next

Three things will determine how quickly Core puts the episode behind it. First, the speed of the emergency fork and the resumption of full CORE services on Coinbase, Bithumb, Coinone, Bitget and LBank. Second, the technical postmortem, which will need to quantify the excess issuance and explain the root cause in credible detail. Third, market reaction once deposits and withdrawals reopen, which will reveal whether holders absorbed the news or used the disruption to exit.

Cointelegraph reported that it contacted Core for further information but had not received a response by publication time.

For now, user assets remain safe according to the project’s own statements, the network continues to confirm transactions, and the fix is being prepared as a forward-compatible upgrade. But until the postmortem lands with real numbers, the Core community is being asked to take a lot on faith — and the exchange suspensions are a visible reminder of how quickly confidence can tighten when issuance goes wrong.