b14g: ~97M Staked CORE Withdrawn; Core Hard Fork Recovers 68.15M

Approximately 97,045,563 CORE affected; 68,146,177.22 CORE recovered by hard fork, not yet distributed; ~9M CORE frozen by exchanges as of 31 Oct, per b14g (claimed). No USD figure given.

Root cause: Not published. b14g says it will publish a technical post-mortem.

Timeline, as sourced: Per b14g: withdrawal 31 Oct 09:29 UTC; contracts paused on discovery; update 16:38 UTC; Core hard fork executed 2 Nov; Recovery Update #1 2 Nov 07:23 UTC.

Claimed (b14g) (security update (opens in a new tab)): at 09:29 UTC on 31 Oct, approximately 97M CORE staked through b14g was withdrawn without authorization and sent to attacker-controlled addresses; affected contracts were paused. About 68M CORE remained on Core and exchange partners had frozen about 9M CORE. BTC staked through b14g remained time-locked on Bitcoin and was not affected. Attacker addresses, per b14g: 0xc556ed208285406d71705927f92d4f4eaea579f1 and 0x27758c30f8e424fbd8ca605bf31e9496c26ce92c.

Claimed (Core) (post (opens in a new tab)): "The Core network is secure." Consensus, validators and staking contracts operated normally, and CORE staked directly with validators or through other protocols is unaffected.

Claimed (b14g) (Recovery Update #1 (opens in a new tab)): on 2 Nov the Core network executed a hard fork recovering 68,146,177.22 CORE from three attacker-controlled addresses via "a one-time state adjustment" to recovery address 0xb85095fE01C1d95da3B1df0998ff5eDDcC9ac064 (opens in a new tab), without reversing transactions, minting tokens or changing total supply. The incident affected approximately 97,045,563 CORE. Exchange-held funds have not yet been returned; there is no official claim process yet.

Unknown: root cause, the size of the remaining shortfall, and the distribution plan.