Zano rolls back to block 3,833,000 after Gateway Address exploit minted unauthorized ZANO and fUSD
The one-month rewind wipes illicit issuance but voids legitimate transactions and forces exchanges to resync to a pre–Hard Fork 6 chain.
Zano restarted its blockchain at block height 3,833,000, immediately before Hard Fork 6, after a Gateway Address vulnerability allowed unauthorized ZANO and Freedom Dollar (fUSD) to enter circulation. The rollback removes the unauthorized tokens but also discards roughly a month of legitimate on-chain history, creating operational and settlement risk until services converge on the recovered chain.
Key Takeaways
- Zano restarted the network at block 3,833,000, the last block before Hard Fork 6, after a Gateway Address vulnerability let unauthorized ZANO and fUSD enter circulation.
- The recovery deletes the unauthorized issuance but also invalidates about a month of legitimate transactions, removing them from the recovered chain.
- Exchanges, nodes, miners, stakers, and other services must adopt the update to follow the recovered chain, raising the odds of resync-related disruptions.
- A reimbursement and claims process is being prepared, but no post-mortem or figure for the unauthorized issuance had been released at publication time.
Zano Rewinds to Block 3,833,000 to Purge Unauthorized ZANO and fUSD
Zano executed a deep chain rollback and restarted its blockchain at block height 3,833,000, immediately before Hard Fork 6. The stated objective was to remove unauthorized ZANO and Freedom Dollar (fUSD) that entered circulation through a vulnerability tied to Gateway Addresses.
The rollback is not a cosmetic reindex. It discards roughly a month of blocks and makes the pre–Hard Fork 6 chain the canonical history again. Transactions confirmed during the discarded window no longer exist on the recovered chain.
Zano’s core team framed the decision as a supply-integrity response to an issuance event that could not be contained cleanly inside the existing history. Quinten van Welzen, Zano’s head of marketing and growth, said: “Doing nothing meant unauthorized ZANO and fUSD in circulation without limit, diluting every holder and breaking the most basic promise a currency makes: a fixed supply,” and added, “It would also tell every future attacker that exploited coins get to keep their value. No project survives that.”
Gateway Addresses Were Built for Integrations—Now They’re the Confirmed Fault Line
The confirmed fault line is Gateway Addresses, a feature introduced in Hard Fork 6 to make integrations easier for bridges, exchanges, and payment services. The design goal was operational simplicity: manage funds through a single account-style balance rather than tracking many discrete outputs.
That is a meaningful shift in how services interact with the chain. Before Gateway Addresses, Zano’s ordinary wallets tracked funds as separate transaction outputs, or UTXOs. For an exchange or payment processor, that meant scanning the chain to identify incoming payments, tracking outputs, and selecting which outputs to spend when processing withdrawals.
Gateway Addresses were meant to reduce that integration burden. The trade is that any bug in the “single balance” abstraction concentrates risk where infrastructure players cluster. Zano has confirmed the incident originated from Gateway Addresses, but it had not released a post-mortem at the time of publication.
That missing document is not a formality. Without it, the market does not know the exploit path, the timeline of compromise, or whether the vulnerability was a narrow implementation bug or a broader design edge case. The other missing number is the size of the unauthorized issuance. No quantity or value for the unauthorized ZANO and fUSD was disclosed.
A Month of Transactions Disappears: Trading, Deposits, and Settlement Risk After a Deep Reorg
The immediate trader-facing risk is not theoretical. A rollback that deep breaks the assumption that “confirmed” means final for the last month of activity. Zano explicitly said the rollback invalidates a month of legitimate transactions along with the unauthorized tokens, and that transactions made during that period will no longer appear on the recovered chain.
Operationally, the recovery only works if the ecosystem coordinates. Zano said participating nodes, miners, stakers, exchanges, and other services must adopt the update to follow the recovered chain. Until that convergence happens, the market can fragment into venues and services that are effectively looking at different histories.
That fragmentation is where microstructure gets messy. Deposits sent during the discarded period may vanish from the recovered chain. Withdrawals processed during that period may no longer have a corresponding on-chain record. Any venue that credits users based on the discarded history has to reconcile that credit against a chain that no longer recognizes the underlying transfer.
The catch is cross-chain settlement. Zano said the rollback cannot reverse payments already settled on other blockchains. That creates irreducible edge cases for users and services that bridged out, settled externally, or otherwise completed obligations on another chain during the invalidated window. The Zano side can be rewound. The external side cannot.
This is the part most traders underestimate. A deep reorg is not just “chain history changed.” It is “accounting systems built on that history now have to choose who eats the mismatch,” and the answer varies by venue, by integration, and by how quickly each operator resyncs and freezes flows.
What Traders Should Monitor Next: Post-Mortem, Claims Process, and Cross-Chain Mismatches
The next information that changes risk assessment is the post-mortem. Zano has confirmed Gateway Addresses as the origin point, but the market still lacks the exploit path, the timeline, and any mitigations specific to that feature. Until those details are public, it is hard to separate “patched incident” from “structural integration risk.”
Second is the reimbursement and claims process. Zano said it is working to account for losses and will publish a reimbursement and claims process, but it has not provided eligibility rules, calculation methodology, or payout timing. Those details decide whether losses are socialized, absorbed by specific counterparties, or left to bilateral dispute between users and services.
Third is exchange and service resync status. The recovery requires adoption by nodes, miners, stakers, exchanges, and other services. Traders should treat deposit and withdrawal availability, and any venue-specific crediting policies, as live risk variables until operators explicitly confirm they are synced to the recovered chain.
Finally, the missing number matters. Any disclosure quantifying how much unauthorized ZANO and fUSD entered circulation before the rollback will anchor the severity of the supply shock Zano chose to erase. Without it, the market is pricing the event with incomplete information.
Why Zano Chose Supply Integrity Over Finality—and the Trust Cost That Comes With It
The decision is a clean tradeoff. I read the restart at block 3,833,000 as Zano choosing supply integrity over transaction finality, and doing it in the most forceful way available. A one-month rollback is not a “bug fix.” It is a statement that the chain’s recent history was less valuable than restoring the intended supply.
Van Welzen made that logic explicit. “Doing nothing” meant unlimited unauthorized ZANO and fUSD in circulation, and the team viewed that as existential dilution. The second-order point is deterrence. “It would also tell every future attacker that exploited coins get to keep their value. No project survives that.” That is the team naming the counterparty: the attacker’s ability to monetize becomes the thing the rollback is designed to break.
The cost is equally explicit. “Restarting the chain from before Hard Fork 6 costs a month of history, and it costs trust, which we’ll have to earn back,” van Welzen said. Trust here is not vibes. It is the market’s willingness to treat confirmations as final, and the ecosystem’s willingness to build integrations that assume the ledger will not be rewritten.
There are two scenarios that matter.
If the post-mortem shows a narrow, well-bounded bug in Gateway Addresses, and the mitigations are specific and testable, the rollback can be framed as a one-off emergency action. In that case, the trust repair is mostly operational: exchanges resync, claims get processed, and the market moves on once the chain stops being a moving target.
If the post-mortem suggests the exploit was enabled by broader design assumptions around Gateway Addresses, the rollback becomes precedent. The market will price a higher probability of future exceptional interventions, and infrastructure players will demand more safeguards before they treat Gateway Address flows as low-risk.
The threshold that matters is coordination plus disclosure. The rollback only becomes stabilizing if services converge on the recovered chain and Zano publishes enough technical detail and claims mechanics to close the accounting loop. That combination is what would confirm the core thesis: Zano can restore supply integrity without leaving the ecosystem stuck in unresolved settlement mismatches.
