Core hard fork recovery returns 68.15 million CORE tokens

A Bitcoin-adjacent staking protocol is clawing coins back the hard way. A Core hard fork recovery on November 2 moved 68,146,177.22 CORE from three attacker-controlled addresses after the October 31 b14g exploit, restoring roughly 70% of the affected tokens without rolling back history or minting new supply.

What happened

PANews, citing a b14g recovery update, said the Core network executed a hard fork that used a one-time on-chain state adjustment to transfer those 68,146,177.22 CORE tokens, about 70.2% of the 97,045,563 CORE affected in the October 31 incident. The operation did not roll back transactions, mint tokens or change total CORE supply.

TokenPost reported the same recovery figure and stressed that funds have not yet been distributed to affected users. b14g is coordinating with exchanges and law enforcement on remaining frozen assets and plans a transparent distribution process; PANews said there is currently no official claims process while balances are verified.

The Defiant's headline framing matched the roughly 70% recovery and unpaid-user point, underscoring that a successful chain-level clawback is not the same as making depositors whole.

Why it matters

Socializing losses via a state edit is always contentious in proof-of-stake communities, but here the Core hard fork recovery was scoped as a one-time adjustment rather than a blanket reorg, which may limit precedent arguments even as it still overrides attacker balances.

Leaving nearly 30% unrecovered keeps exchange freezes and law-enforcement seizures central. Until those coins return, any distribution plan will be partial, and users will judge b14g on both the speed and the fairness of the eventual payout queue.

The episode sits in a week already crowded with security failures. Our pieces on the Aave market freeze and the name.com DeFi hijack showed different defensive instincts -- risk-parameter locks versus domain compromise -- while Core chose consensus-level restitution.

For dual-staking designs that bridge Bitcoin security assumptions into alt-L1 collateral, governance willingness to rewrite state after a hack is now part of the risk disclosure, not an edge case.

That sequencing matters for any later forensic timeline. By moving balances through a declared state adjustment rather than reverse-engineering each exploit transaction, Core avoided rewriting unrelated ledger history, but it also concentrated trust in the fork coordinators who chose which three addresses to empty and where the recovered CORE would sit until claims open.

Comparisons to last week's exchange freezes are inevitable. Centralised venues can blacklist deposit addresses; an L1 that edits state is making a different social contract with token holders, and that contract will be cited the next time a DeFi protocol on Core asks whether socialised recovery is available.

b14g's dual-staking users, meanwhile, still need a published schedule for verifying balances and for handling any shortfall if exchange-held remnants never return in full.

What's next

The next milestones are an official claims process and any return of exchange-held or frozen remainder funds. TokenPost's recovery report restates the 68.15 million CORE figure and the unpaid status.

How Core hard fork recovery coins are allocated among victims will decide whether the 70% headline reads as restitution or as governance theatre.

Watch for b14g's verification timeline; PANews said distribution planning is still under way.