Core DAO plans emergency hard fork after validators drew excess rewards

Core DAO is preparing an emergency network hard fork to patch a vulnerability that allowed validators to siphon an overabundance of staking rewards from the system. According to disclosures from the Core development team, the exploit has been strictly contained, and the remediation will take the form of a "forward" network upgrade. Crucially for ecosystem participants, the patch will not involve rolling back the blockchain state or reversing previously finalized transactions—a deliberate choice aimed at preserving ledger integrity despite the financial anomaly. For developers building within Core’s EVM-compatible layer, the decision to avoid a state rollback prevents a potential technical nightmare. Network rollbacks often break smart contract states, disrupt decentralized finance primitives, and cause severe liquidation cascades across lending markets. By opting for a forward-facing hard fork, Core preserves the deterministic history of its blockchain, allowing decentralized applications to continue operating without re-entrancy risks or state desynchronization. The vulnerability itself appears rooted in the distribution logic governing Core’s Satoshi Plus consensus, which blends delegated Proof-of-Work from Bitcoin miners with Proof-of-Stake. Correcting this logic requires re-aligning validator reward curves without altering the block history already written to disk. From an investor and tokenomics standpoint, the incident introduces short-term headwinds regarding CORE token supply dynamics. While the total volume of over-issued rewards has not been fully quantified, any unmetered token emission risks temporary inflationary pressure. Investors are closely monitoring how the foundation intends to absorb or neutralize the excess tokens drawn by the malfunctioning validator set—whether through future reward reductions, treasury burning, or targeted slashing mechanics. Institutional stakers, meanwhile, face heightened scrutiny regarding the operational hygiene of their node infrastructure, as participating in unintended reward drains, even passively, risks reputational fallout and regulatory friction. This incident highlights the delicate balancing act faced by modern Layer-1 ecosystems attempting to merge complex, hybrid security models with high-throughput execution. Unlike earlier instances in crypto history where protocols resorted to controversial chain splits or ledger rewrites to undo exploits, Core’s approach signals a maturing paradigm in blockchain engineering: prioritize ledger immutability above all else, even if it means absorbing over-allocated rewards as a protocol loss. As the hard fork rolls out across validator nodes, the broader Web3 ecosystem will be watching whether Core can seamlessly restore reward equilibrium without fracturing its growing base of Bitcoin-focused builders.