Zano Executes Emergency Rollback to Address Critical Security Vulnerability

The Zano blockchain team has taken the drastic step of rolling back its network by approximately one month following the discovery of a significant security flaw. To address the resulting financial discrepancies and lost transactions, the core team has announced a recovery plan funded by developer reserves and personal contributions, though the specific logistics for user compensation are still being finalized.

The Breach and the Month-Long Reset

The emergency intervention was triggered by a "Gateway Address vulnerability" that allowed unauthorized amounts of ZANO and Freedom Dollar (fUSD) to enter circulation. To neutralize the threat, the team restarted the chain from block 3,833,000—a point dating back to August 26. This move effectively erased all transaction history recorded between late August and September 27. While the team emphasized that wallet spend keys and transaction privacy remained secure, the rollback created a significant gap for users who conducted trades or transfers during that period. Notably, the reset cannot undo settlements made in external assets like USDT or DAI on separate networks, complicating matters for those involved in cross-chain swaps.

Recovery Funding and User Guidelines

To support those impacted by the missing transactions, Zano's leadership has pledged to utilize the network’s developer fund, personal finances from team members, and committed contributor resources. Currently, this remains a funding strategy rather than a guaranteed full-loss coverage, as eligibility rules, payment amounts, and a formal claims timetable have not yet been published. The network is reportedly stable now, and the core team is working with exchange partners to verify activity and synchronize services with the recovered chain.

Instructions for Affected Participants

While a formal claims process is not yet live, Zano has advised users to take proactive steps to secure their records. Impacted individuals are encouraged to save transaction IDs, trade history, and exchange records as evidence for future claims. Furthermore, users must update their wallets to the latest version and verify the final status of any payments on the recovered chain before attempting to resend funds. The team has promised a full post-mortem of the vulnerability and further instructions once the verification process with third-party partners is complete.