BIP Dallas Digital News & Media Platform

collapse
Home / Daily News Analysis / Core DAO plans emergency hard fork after validators drew excess rewards

Core DAO plans emergency hard fork after validators drew excess rewards

Sep 02, 2026  Twila Rosenbaum 9 views
Core DAO plans emergency hard fork after validators drew excess rewards

Core DAO is preparing an emergency hard fork after a group of validators drew excess CORE rewards from the network's issuance system. The project said the issue has been contained and that the hard fork will act as a forward upgrade, which means it will not roll back the blockchain or reverse previously confirmed transactions.

The situation became public when Core issued a status note explaining that a small number of validators had accrued rewards significantly above the protocol's intended issuance. The project stressed that the problem involved reward issuance rather than the security of user assets. Core also said it would publish a technical postmortem after completing its investigation. The latest update goes one step further by confirming that malicious validators can no longer continue drawing excess rewards and that the network will be patched.

Why an emergency hard fork?

An emergency hard fork is one of the most consequential actions a blockchain network can take. Because a hard fork changes the fundamental consensus rules, it requires coordination among developers, node operators, validators, and often exchanges. In this case, Core is using the mechanism to close a vulnerability that allowed reward issuance to deviate from the underlying protocol. By moving to a new set of network rules, Core aims to ensure that no additional excess CORE can be claimed.

The decision not to roll back the network is considered particularly important. A rollback would involve restoring the blockchain to an earlier state and removing transactions that have already been confirmed. That approach can create serious problems for exchanges, wallets, and decentralized applications that have settled positions based on the existing ledger. A forward upgrade, in contrast, applies the fix from that point onward while preserving transaction history.

Hard forks are commonly used in digital assets when a security flaw or unintended economic behavior needs to be corrected. They are also used for planned feature upgrades. The distinction matters because an emergency fork is often executed under pressure, and the technical details can determine whether users retain confidence in the network.

How validator rewards normally work

Validators on blockchain networks are responsible for proposing new blocks, verifying transactions, and maintaining the integrity of the ledger. In exchange for these duties, they receive rewards, often in the network's native token. These rewards are intended to follow a predefined issuance schedule or protocol formula. If the formula is broken or the reward-handling logic is manipulated, validators may be paid amounts that were never authorized by the network's rules.

In Core's case, the excess rewards were not limited to a normal rounding error. A small set of validators reportedly obtained rewards far above what the protocol intended to emit. While the exact mechanism has not been disclosed, the incident underscores the importance of carefully audited reward code. It also raises governance questions about how blockchains should respond when issuance goes off track and whether the extra tokens should be clawed back.

Core has not said whether the excess CORE tokens entered general circulation. That detail is important because tokens that remain within validators' control could be sold, transferred, or used in decentralized finance applications. Since the hard fork will not reverse transactions, any extra rewards that were moved before the fix may stay where they were sent. Core has not publicly outlined a way to recover those funds and has instead framed the fork as a way to prevent the issue from getting worse.

Exchanges respond with temporary suspensions

Security incidents on a blockchain frequently trigger immediate action from cryptocurrency exchanges, and the Core network was no exception. Several platforms moved to limit CORE transfers while they assessed the situation.

Coinbase paused sends and receives on the Core network, a standard step when a chain is under review for suspicious activity. Bithumb and Coinone, both based in South Korea, suspended CORE deposits and withdrawals. They cited suspected or confirmed security concerns at the time of the suspension. Bitget also stopped CORE deposits and withdrawals, describing its decision as wallet maintenance. LBank suspended CORE deposits, saying the action was related to the project's requirements.

Exchange suspensions can be disruptive, but they are often intended to protect users from depositing tokens on a network that may be experiencing unexpected behavior. Without reliable information about how many extra tokens were issued, exchanges cannot be certain that incoming CORE transfers are legitimate or final. The fact that multiple venues paused activity suggests the incident triggered serious concern across the broader market.

Core has not yet explained the exact vulnerability that enabled the excess rewards. It also has not specified how much CORE was issued, how long the activity lasted, or whether any of the additional tokens were used to buy other assets. These unanswered details have left observers waiting for a more complete picture.

A broader pattern of network emergencies

The planned hard fork is not happening in isolation. Other blockchain networks have recently faced situations that demanded active intervention. BNB Chain activated the Pasteur hard fork to strengthen bridge security, a move that reflected the ongoing effort to make cross-chain infrastructure more resistant to attack. Cronos halted its network after an exploit involving the Tectonic protocol and an estimated $75 million. Polygon also disclosed security flaws that were fixed in recent hard forks. These events show that security and protocol-correctness issues can arise in many different forms, from bridge vulnerabilities to reward accounting defects.

For Core, the priority appears to be restoring trust in the network's issuance rules. The project's decision to keep user funds and transaction history intact is meant to limit collateral damage. Yet the lack of public data about the scale of excess rewards means there is an important gap in information. A transparent technical postmortem will be necessary to help users understand whether the network's monetary schedule has been permanently changed or whether the issue was isolated to specific validators.

The coming days are likely to provide more clarity. Core has committed to follow-up details and has asked the community to look out for further updates. In the meantime, the network will move forward with the planned fork while stakeholders remain focused on how many CORE tokens entered circulation and what that means for the asset's supply.


Source:Cointelegraph News


Share:

Your experience on this site will be improved by allowing cookies Cookie Policy