Bitcoin dual-staking layer b14g said the Core network has completed a hard fork recovery tied to an earlier security incident. According to the team, the event involved about 97.05 million CORE. After the fork, 68,146,177.22 CORE was recovered from three addresses controlled by the attackers.
b14g said the recovered funds were moved to a designated recovery address through a one-time state adjustment. The team added that the process did not roll back transactions, did not mint new tokens, and did not change the total supply of CORE.
The recovered assets have not yet been distributed to affected users. b14g said it is still working with exchanges and law enforcement agencies to recover the remaining frozen assets, and that it will prepare a transparent distribution plan.
Bitcoin dual-staking layer b14g said the Core network has completed a hard fork recovery following an earlier security incident.
According to the team, the incident involved about 97.05 million CORE. After the hard fork, 68,146,177.22 CORE was recovered from three attacker-controlled addresses. The funds were then moved to a designated recovery address through a one-time state adjustment.
b14g said the recovery process did not roll back transactions, did not mint new tokens, and did not alter CORE’s total supply.
The recovered funds have not yet been distributed to affected users. The team said it is coordinating with exchanges and law enforcement agencies to recover the remaining frozen assets and will set out a transparent distribution plan.
This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan. Disclaimer:
The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.
Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.
