b14g Reopens Staking After 97.05 Million CORE Exploit

By Elena Vasquez

b14g said a zero-amount withdrawal exploit linked to Oct. 31 drained 97.05 million CORE from 91 staking orders, after which the protocol paused affected contracts and deployed a fix. Deposits, withdrawals, staking and reward claims are available again, the protocol announced: “its contract is running again.”

What failed, and what remains unproven?

b14g previously said requests to withdraw zero CORE caused the loss across 91 orders. The protocol attributed the incident to an attacker using its standard withdrawal process and said the attacker did not obtain private keys or administrator access.

b14g stated that the attacker “exploited the protocol’s standard withdrawal process without gaining access to private keys or administrator accounts.” The announcement identifies no attacker, transaction hashes or postmortem, so it does not provide enough evidence for independent readers to test the sequence.

Takeaway: b14g describes a withdrawal-process exploit rather than a key compromise, but its announcement does not independently substantiate that distinction.

What has reopened for users?

Users can again deposit and withdraw funds through b14g’s website, stake through the protocol and claim rewards. The reopening follows the incident-related pause and the deployment of the zero-amount withdrawal fix, returning the affected contract to operation.

The announcement does not provide the first weekly claim date, a timetable for restoring individual balances or a statement on whether new funds remain separate from the repayment pool. It also does not quantify any claims already processed since the reopening, an omission that limits assessment of the recovery’s current pace.

Takeaway: The platform’s principal functions are open again, but the announcement leaves individual recovery timing unspecified.

How much does the repayment plan cover?

The repayment plan outlines a return of 68.15 million CORE, about 70.2% of the reported 97.05 million CORE loss. That leaves 28.90 million CORE, or 29.8%, to be addressed through further repayments if the full reported loss is to be recovered.

Initial allocations use verified order balances, and affected users can claim portions weekly. b14g did not publish a complete order-by-order schedule, a final claim deadline or a formula showing how its aggregate allocation translates into individual payments.

The weekly structure matters because the 68.15 million CORE figure is a pool for affected staking orders, not a promise that every affected user receives the same amount. b14g gives no minimum claim, maximum claim or eligibility cutoff beyond the stated reliance on verified balances.

Takeaway: The plan covers roughly seven in every ten reported tokens, while individual payment amounts remain tied to each verified order.

What funds the remaining recovery?

Further repayments are to come from half of future revenue from Core staking and any additional CORE recovered through exchange freezes. The arrangement therefore links the unresolved loss to two future cash or token flows rather than assigning the whole obligation to a disclosed reserve.

b14g did not identify the exchanges, specify any freeze deadline or report how much CORE has been frozen. It also did not define whether “future revenue” begins immediately after the incident or on a later date, and it supplied no enforcement timetable for exchange cooperation.

The absence of a final deadline means the 28.90 million CORE gap has no stated resolution date. Future staking performance and the willingness of exchanges to freeze assets will determine the pace, while weekly claims will test whether the initial allocation reaches users as described.

Takeaway: The remaining recovery depends on future staking revenue and exchange action, neither of which has a disclosed amount or completion date.

With no final repayment deadline, the next checkpoint is the first weekly claim: users will learn whether distributions under the 68.15 million CORE allocation begin as described, while the remaining loss still depends on future staking revenue and exchange freezes.