The privacy-focused layer-1 blockchain Zano has taken the drastic step of rolling back approximately a month of its network history following a severe vulnerability. According to the project’s core team, the security flaw involved a newly introduced feature known as Gateway Addresses, which allowed unauthorized amounts of native ZANO tokens and Freedom Dollar (fUSD) assets to enter circulation unchecked.
To counteract the exploit and preserve the economic integrity of the ecosystem, the Zano blockchain was officially restarted at block 3,833,000. This specific block height places the network immediately prior to Hard Fork 6, the network upgrade that originally deployed the compromised Gateway Address feature. The recovery effort requires widespread cooperation across the network, meaning participating nodes, miners, stakers, cryptocurrency exchanges, and various infrastructure services must manually adopt the critical software update to align with the recovered chain.
Quinten van Welzen, Zano’s head of marketing and growth, emphasized the severity of the incident in statements provided to Cointelegraph. He noted that the volume of unbacked tokens generated during the exploitation window was considerable. The decision to execute a rollback of this magnitude is exceptionally rare and contentious in the blockchain industry, as it inevitably disrupts regular network operations, but the core team deemed it necessary to prevent catastrophic economic dilution.
The sweeping network rewind comes with significant consequences for regular users and ecosystem participants. The rollback effectively invalidates an entire month of legitimate on-chain transactions alongside the fraudulent token generation. Consequently, any genuine transfers, trades, or network interactions executed during that one-month window will no longer appear on the newly recovered blockchain. Furthermore, the rollback cannot retroactively reverse or alter financial settlements or transactions that have already been finalized and cleared on external blockchains or centralized platforms. Recognizing the disruption caused to innocent users, the Zano team announced that it is actively working on a comprehensive plan to account for user losses and will soon publish details regarding a structured reimbursement and claims process.
Addressing the rationale behind the difficult decision, van Welzen took to social media to explain the existential threat the exploit posed to the project. Allowing the unauthorized tokens to remain in circulation would have permanently undermined the asset’s foundational economics.
"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," van Welzen wrote in a public post on X. "It would also tell every future attacker that exploited coins get to keep their value. No project survives that."
Zano Identifies Gateway Address Exploit

While the Zano core team has not yet published an exhaustive post-mortem analysis detailing the precise mechanics of the attack at the time of publication, they have confirmed the root cause of the vulnerability. The security breach originated within the Gateway Addresses feature. This architectural addition was originally designed to streamline and simplify the integration process for external bridges, centralized cryptocurrency exchanges, and payment processing services. By allowing these platforms to manage user funds through a single, account-style balance similar to accounting models found on Ethereum and other popular blockchains, the feature aimed to lower technical adoption barriers.
Before the introduction of Gateway Addresses, Zano’s standard architecture utilized unspent transaction outputs, commonly referred to as UTXOs, to track funds across its network. Unlike account-based systems, Zano’s ordinary wallets historically tracked every individual transaction output separately. For centralized exchanges and third-party payment services, this meant developers had to build infrastructure capable of continuously scanning the blockchain to identify incoming user payments, meticulously track those discrete outputs, and correctly select which specific outputs to spend whenever a user requested a withdrawal. Gateway Addresses were meant to alleviate this friction by abstracting the UTXO model into a more familiar balance framework.
Providing further clarity on the network’s operational status, van Welzen confirmed to Cointelegraph that all Gateway Addresses have been temporarily deactivated on the updated chain. These addresses will not be brought back online until the Gateway Address code undergoes rigorous internal review, comprehensive independent security audits, and extensive testing to ensure no residual vulnerabilities remain.
Launched originally in May 2019, Zano was engineered from the ground up as a layer-1 blockchain explicitly focused on private financial transactions and enhanced data confidentiality. The network’s standard private transactions are built to completely conceal senders, receivers, transferred transaction amounts, and the specific asset types changing hands. Beyond its native cryptocurrency token, ZANO, the blockchain’s flexible protocol architecture allows users and developers to deploy, issue, and mint custom digital assets directly on the network. Freedom Dollar, commonly referred to as fUSD, is one such prominent custom token that operates natively within the Zano ecosystem.
The decision to rewrite a month of history was not taken lightly by the developers who have dedicated years to building the privacy-centric protocol. Acknowledging the heavy toll the incident takes on user confidence, van Welzen reflected on the difficult path ahead for the project’s community and development team.
"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.
"But it restores the supply everyone signed up for, and it leaves a path to rebuild. Which is better than 7 years of hard work left to die. We know it hurts. But not doing it would have hurt more."






