0x3a82a6f03a82…3a82a6ed

ConfirmedSecurity533 vB102 sat/vB3 min decode

b14g Opens CORE Claims Portal With 151,127 CORE Recovery Pool

b14g opened a claims portal with a 151,127 CORE recovery pool, roughly 0.5% of the 28.9 million CORE outside its hard fork, under full-and-final settlement terms.

B14g Opens CORE Claims for Revenue-Funded Repayments
WitnessB14g Opens CORE Claims for Revenue-Funded Repaymentskaboompics / pixabay

Outputs

  1. b14g's claims portal held about 151,127 CORE as of Nov. 16.

  2. The pool covers roughly 0.5% of the 28.9 million CORE not covered by the hard fork.

  3. The Oct. 31 exploit used zero-amount withdrawal requests to drain staking-order balances.

  4. About 29,960 CORE remains in the original hard-fork recovery address on CoreScan.

  5. Claims act as a full and final settlement; full repayment is not guaranteed.

b14g has opened a claims portal for revenue-funded repayments to users affected by its Oct. 31 security incident, with a recovery pool holding about 151,127 CORE as of Nov. 16, according to an on-chain check of the portal-linked address.

That pool equals roughly 0.5% of the 28.9 million CORE not covered by b14g's earlier hard fork, based on calculations using the protocol's own figures. The pool balance does not measure total user entitlements or cumulative repayments, the protocol cautioned.

b14g matches Bitcoin holders with CORE stakers to share enhanced staking rewards. Its post-mortem attributed the Oct. 31 drain to zero-amount withdrawal requests that released entire staking-order balances. Bitcoin remained time-locked on the Bitcoin chain and was unaffected, the protocol said.

What remains from the hard fork?

CoreScan showed about 29,960 CORE still sitting in the original hard-fork recovery address as of the check. That residual balance alone does not establish whether those tokens remain owed to users. At the time of the earlier recovery, b14g said distribution was still pending; the new announcement states that recovered funds have been distributed.

The hard fork covered most of the affected CORE. The 28.9 million CORE outside its scope now anchors the new claims process, funded by protocol revenue rather than a one-time recovery.

What do claimants give up?

The portal's linked Recovery Plan Terms carry binding settlement conditions. Signing, clicking "Sign and accept," or interacting with b14g contracts—including claiming repayments—counts as acceptance of the plan as a "full and final settlement" of incident-related claims.

The terms include several releases and affirmations:

  • Claimants release claims against b14g and related parties to the fullest extent permitted by law, preserving only the limited obligations in the recovery plan and claims that cannot legally be waived.
  • Users must affirm they own the wallet or are authorized to act for it, have not transferred their claims, and are not subject to sanctions.
  • Users transfer recovery rights against the attacker and recipient services to b14g; further recoveries will be distributed after reasonable recovery costs.

The settlement structure shifts enforcement risk to the protocol. If b14g later recovers funds from the attacker or services that received drained assets, it will distribute proceeds net of recovery costs to accepting claimants.

What are the repayment terms?

Repayment has no fixed end date, and full repayment is not guaranteed, the portal and terms both warn. The 151,127 CORE pool represents a starting position funded by revenue, meaning repayment pace depends on the protocol's ongoing earnings rather than a fixed treasury.

The portal also carries anti-phishing warnings. b14g will never ask for seed phrases, private keys, or an upfront payment to receive repayment, it stated, and claims take place only on app.b14g.xyz.

Claimants now face a decision window without a stated deadline: accept the settlement terms and begin receiving revenue-funded repayments, or preserve legal claims while the 151,127 CORE pool accrues. The absence of a fixed end date leaves both options open indefinitely, and the protocol's guarantee-free framing means users must track repayment progress on-chain themselves.

via cryptonews.net (Source)

More from Tom Whitfield

Tom Whitfield

Show full bio

News editor covering technology and product news in crypto and web3 industry at Mempool Brief.

1,374 articles