0x62096afe6209…62096b01

ConfirmedSecurity702 vB160 sat/vB4 min decode

Zano Rolls Back a Month of Transactions, Plans Personal Funds for Recovery

Zano restarted its chain from block 3,833,000, erasing a month of confirmed transactions after a Gateway Address flaw minted unauthorized ZANO and fUSD.

Zano rolls back a month of transactions as team plans to use personal funds for recovery
WitnessZano rolls back a month of transactions as team plans to use personal funds for recoveryAI-generated

Outputs

  1. Zano's Sept. 27 emergency release restarted the chain from block 3,833,000, dated Aug. 26 at 15:50 UTC, removing roughly a month of confirmed transactions.

  2. A Gateway Address vulnerability allowed unauthorized ZANO and Freedom Dollar (fUSD) into circulation; wallet spend keys and transaction privacy were not compromised.

  3. Recovery funding will come from the developer fund, team members' personal funds and committed contributors, with no stated amount, timetable, eligibility rules or claims process yet published.

The Zano team said it will draw on the network's developer fund, team members' personal funds and committed contributors to finance recovery from an emergency rollback that removed roughly a month of previously confirmed transactions from the chain. The update, posted on the official Zano forum, gives no funding amount and no timetable for payments.

The rollback stems from an emergency software release published on Sept. 27, which restarted the chain from block 3,833,000 — a block the release dates to Aug. 26 at 15:50 UTC. Any transaction recorded on the previous chain after that point is absent from the recovered chain. The team says the network is now stable and that it is working with partners to verify affected activity. ZANO supply and emission will remain unchanged, according to the update.

The core team attributed the incident to a Gateway Address vulnerability that allowed unauthorized ZANO and Freedom Dollar (fUSD) to enter circulation. It reported no compromise of wallet spend keys or of ordinary transaction privacy. A full post-mortem of the flaw remains pending.

The funding plan carries important caveats. The named sources of capital constitute a stated intention, not a published guarantee that every loss will be covered. Eligibility rules and a claims process have yet to be released, leaving affected users without a defined standard for what records will count or whether the committed funding can absorb the total losses.

Irreversible external settlements

One structural limitation of the rollback could prove the most consequential for users. The team said the rollback cannot undo payments already settled in USDT, DAI or other assets on separate networks. That distinction matters directly for anyone who executed a swap or trade with a Zano transaction on one side and an external payment on the other: the Zano leg may have vanished from the recovered chain while the counterparty's transfer on another network remains final.

This asymmetry creates a class of losses the rollback itself cannot reach, and it explains why the recovery fund — rather than the chain restart alone — has to carry the burden of making users whole.

What affected users should do now

Zano says affected users need take no claims action yet. The team will publish instructions after it finishes working with partners and counterparties. Zano's verified forum account confirmed in a recent reply that no claims process is live, and advised users to save transaction IDs along with trade and exchange records.

Users can open a support ticket to put a case on record, but the forum account stated plainly that nobody can preapprove a claim before the rules are published. Any service or intermediary promising advance approval is doing so outside the official process.

The core team has also told users to update their wallets and to check a payment's final status on the recovered chain before resending it. Zano is supporting exchanges, wallets and payment services as they migrate to the recovered chain, but each operator must complete its own update and announce readiness independently. Users should confirm that a given service has adopted the recovered chain before sending funds to or from it — otherwise a transfer could land on the wrong chain version and compound the loss.

Open questions

Zano has promised a further update covering wallets, services and exchanges, plus a post-mortem of the Gateway Address flaw. Two gaps remain material for affected parties: the claims instructions, which will determine what documentation counts and how eligibility is assessed, and clarity on whether the stated funding sources — developer fund, personal funds and committed contributors — suffice to cover verified losses in full.

Until those terms land, users who lost funds in the rollback window hold an unquantified claim against an unfunded, unstructured commitment. The situation underscores the operational reality of rollback-based recoveries on privacy-oriented chains: reverting state can restore on-chain balances, but it cannot rebook settlements on external networks, and compensation depends entirely on the solvency and good faith of the recovery fund behind it.

Watch for the claims-process publication and the Gateway Address post-mortem as the next milestones: both will determine whether Zano's recovery commitment translates into an executable, rules-based compensation program.

via forum.zano.org (Original)

More from Elena Vasquez

Elena Vasquez

Show full bio

Staff writer covering marketplaces and e-commerce at Mempool Brief.

439 articles