b14g Sets 5-7 Day CORE Repayment After Protocol Exploit

b14g will return 68.15 million CORE to affected staking orders within five to seven days, covering roughly 70.2% of the 97.05 million CORE drained in an Oct. 31 exploit, according to the Bitcoin (BTC) dual-staking protocol’s repayment plan.

What does the repayment schedule mean?

The initial distribution will be based on each order’s verified balance, and b14g says it has verified balances for all affected staking orders. Users will be able to claim their shares weekly, giving holders recurring access to the recovery rather than a single settlement date.

Future repayments will draw on 50% of b14g’s revenue from Core staking. Any additional CORE recovered through exchange freezes will also go toward repayments, creating a second recovery channel alongside protocol revenue.

The structure leaves the remainder tied to future operating income and successful freezes rather than to recovered tokens alone. Weekly claims can continue at a pace set by Core staking revenue, while cooperation from exchanges determines whether more of the 97.05 million CORE can enter the repayment pool.

The announcement sets no fixed completion date for the balance left after the initial allocation. Instead, it creates two layers: a balance-based distribution from recovered CORE and continuing weekly claims tied to future protocol revenue and exchange recoveries.

What caused the Oct. 31 exploit?

b14g attributed the Oct. 31 loss to “zero-amount withdrawal requests” that its contracts accepted. The requests drained 97.05 million CORE from 91 staking orders, according to the protocol’s account of the incident.

The attacker used the protocol’s “regular withdrawal function,” b14g said, while the protocol reported no compromise to private keys or administrative accounts. The protocol’s account places the failure in contract validation: the contracts admitted withdrawal requests that should have carried no amount.

b14g described the issue as an accepted withdrawal path, not a key-management failure. Its contracts treated the zero-amount requests as eligible withdrawals, letting the attacker pull CORE from 91 orders through the standard withdrawal route.

How did the recovery reach Core users?

The plan follows a hard-fork recovery of 68.15 million CORE. On Nov. 2, the Core network moved the recovered tokens to a designated address. That recovery covered part of the 97.05 million CORE involved in the exploit, but affected users had not yet received the tokens.

The supply recovery and user reimbursement are separate steps. The hard-fork tokens had reached only a designated address, not the 91 affected orders, by the time b14g set out its plan. The verified-balance calculation determines each claim, while weekly access spreads the recovered tokens through the repayment program.

What changes after the exploit?

b14g plans to add checks that reject zero or invalid withdrawal amounts. It also plans automated alerts for unusual withdrawals and changes to its emergency-response system so affected contracts can be paused within minutes.

The withdrawal checks address the mechanism b14g identified; the alerts improve visibility, and the revised emergency process shortens the path to containment. b14g did not provide implementation dates or technical specifications for those three safeguards in the announcement.

The next concrete test falls within five to seven days, when b14g says affected holders can begin claiming from the 68.15 million CORE recovery while weekly repayments continue through Core staking revenue and any exchange freezes.