Core DAO Readies a Hard Fork After Validators Drew Excess CORE

Core DAO is preparing an emergency hard fork after a group of validators drew more CORE than the protocol was built to issue. The project called the parties malicious and said on Tuesday that the incident had been contained. The fix is a forward upgrade, so no blocks come back and no confirmed transaction unwinds. Five exchanges restricted CORE transfers around the same window. What Core has not published is the size of the hole.

What the fork does and does not do

Core runs a consensus design it calls Satoshi Plus, which blends delegated Bitcoin mining with delegated staking and pays newly minted CORE to validators by a scoring formula. Crypto Briefing, alone among the accounts reviewed for this piece, puts the validator share of new issuance at up to 90% and the token's hard cap at 2.1 billion. The flaw sat in that payout path. Core's position throughout is that user balances were never in play and the problem was limited to reward issuance.

"No transactions will be reversed, no blocks will be rolled back, and the network's existing state stays intact," Core said of the planned upgrade.

Cointelegraph, publishing early Wednesday, rendered the same commitment in different words. The approach follows MANTRA, which restarted without a rollback and watched the market sell the news. Cronos went the other way last week.

Where the transfers stopped

Coinbase paused CORE sends and receives while leaving trading open. Bithumb and Coinone suspended deposits and withdrawals and cited security. Bitget called it wallet maintenance. LBank said it acted at the project's request, the only one of the five explanations that points back at Core itself. The dates do not line up. Crypto Briefing puts the Coinbase pause on 31 August and CryptoTicker times it to 4:41 UTC that morning, while CoinMarketCap's summary places the exchange halts on 1 and 2 September and says the incident was contained by the 1st. Three of the five accounts give no date at all, and we could not establish which reading supersedes which.

The number nobody has published

Every account agrees on the gap. Core has not said how much excess CORE was issued, how long the validators were able to draw it, or whether any of it reached circulation. Nor has it described the underlying bug. A technical postmortem was promised and had not appeared at the time of writing, which leaves holders and exchanges with no way to read the token's supply. The precedent is fresh enough to sting: Syscoin halted its bridge after an exploit minted 5 billion SYS, and the minted figure became the whole story within a day.

What the chain appears to show

CryptoTicker published the only on-chain reconstruction located for this piece, and it stands unverified. On its reading, Core's active validator set went from 21 to 23 on 28 August and back to 21 on the 31st, with two addresses producing blocks between 00:11 UTC on the 28th and 05:50 UTC three days later. It counts 181 blocks missing from the expected cadence across a four-hour window. The chain never stopped. The longest block interval it found was five seconds against a normal three, which is a slowdown rather than an outage. No other outlet carries any of this.

Two price readings, and a wait

The Crypto Basic quoted CORE at $0.0205 when it published on Wednesday, down 4.1% on the day and 19.5% over seven days. CoinMarketCap's page showed $0.02029 on Thursday morning, up 1.45% over 24 hours. The two are hours apart and measure different windows, and they do not reconcile into a single move. Neither Cointelegraph nor Crypto Briefing gives a price at all. Nothing published so far names an activation height or a date for the fork, and each exchange will decide on its own when to reopen transfers. Self-custodied CORE is untouched either way. The postmortem is the document that settles the rest.