Zano's core team has restarted the network from block 3,833,000 — a point it dates to Aug. 26 at 15:50 UTC — after a Gateway Address vulnerability let unauthorized ZANO and Freedom Dollar tokens into circulation. The emergency release went out Sept. 27. Roughly a month of previously confirmed transactions is gone from the recovered chain.
Recovery will be financed from the network's developer fund, team members' personal money, and committed contributors. There's no funding figure and no timetable yet.
What actually got rolled back
Everything recorded on the old chain after that August snapshot is absent from the recovered one. That's the part users tend to underestimate: a rollback isn't a patch you apply on top of history, it's a decision to discard history. About a month of it.
The team says wallet spend keys were not compromised and ordinary transaction privacy held up. A full post-mortem of the Gateway Address flaw is still pending, so the mechanics of how unauthorized tokens entered circulation haven't been laid out publicly.
The payments the rollback can't reach
Here's the awkward bit. If someone settled a Zano-linked trade in USDT, DAI, or another asset on a separate network, the rollback does nothing about it. Those transfers happened on chains Zano doesn't control, and there's no mechanism in this fix to claw them back.
ZANO supply and emission are unchanged, which rules out the other obvious lever — inflating or burning to paper over the hole. The bill lands on the developer fund and the team's own balance sheets instead.
No claims window yet
The verified Zano forum account said plainly that no claims process is live right now. Eligibility rules haven't been drafted publicly, and no claim can be preapproved before those rules exist.
What users can do in the meantime: save transaction IDs, plus trade and exchange records. Support tickets can put a case on the record, but that's a log entry, not a claim. The team has said instructions will go out once it has worked through partners and counterparties, and that affected users need take no action yet.
Check before you resend
Zano is helping exchanges, wallets, and payment services migrate, but each operator has to make its own call and announce when it's ready. The team's advice is blunt: confirm a service has adopted the recovered chain before sending funds to or from it, update your wallet, and check whether a payment's final status shows on the recovered chain before resending anything.
Sending into a service that hasn't switched over yet is a good way to turn one problem into two.
The next concrete deliverable is a further update covering wallets, services, and exchanges, alongside the outstanding Gateway Address post-mortem. Neither has a date attached.
