The Zano blockchain has been rolled back after the discovery of an inflation-related software bug, removing a full day of on-chain history. The incident affects more than the protocol code itself: it also raises questions about token-supply records, transaction continuity and the systems that rely on blockchain data for settlement and verification.
Inflation bug triggers Zano rollback
The rollback was driven by a software vulnerability linked to Zano's inflation mechanism. Available information indicates that the bug forced the project to revise the blockchain's history. The network ultimately removed an entire day's records rather than correcting a single transaction or a limited number of blocks.
Blockchain ledgers are generally built by appending blocks in chronological order. Removing a complete section of that history requires nodes to adopt a new chain state and prompts related software, block explorers, wallets and other infrastructure to resynchronize with the corrected record. Transactions that occurred during the removed period must be assessed according to their status on the rolled-back chain.
Token-supply calculations remain under scrutiny
The need for a network-level response stems from the possibility that the inflation bug affected the issuance or supply calculation of Zano tokens. Total supply, block rewards and related issuance rules are key reference points for exchanges, wallet providers and market participants checking asset balances. If the software's output diverges from the protocol's intended rules, changing a front-end display or adjusting individual account balances would not resolve the underlying issue.
The confirmed response so far is that Zano removed one day of history to address the incident. The available information does not specify whether the vulnerability affected issuance calculations, block rewards or another part of the inflation logic. It also does not provide a complete account of the number of tokens involved, the affected block range or the addresses impacted. Those details will determine how outside participants reconcile balances and transaction states before and after the fix.
Nodes and on-chain services face reconciliation work
A blockchain rollback typically requires node operators to upgrade their software, switch to the new chain state and revalidate block data. Exchanges, wallet providers, block explorers and other services that depend on Zano data must also check whether their internal records match the corrected main chain. Until the chain stabilizes, deposit, withdrawal and transaction-confirmation procedures may require additional verification. The available information does not indicate whether any specific platform has suspended these services.
For users, the immediate questions are whether transactions made during the deleted period remain recognized by the new chain and how account balances and token-supply data will be recalculated. Developers and node operators, meanwhile, need to confirm that all nodes are running a version containing the fix, reducing the risk that different nodes continue to maintain conflicting versions of the historical record.
Zano case highlights limits of ledger continuity
The Zano incident shows that blockchain immutability does not rule out a protocol-level rollback when a software vulnerability is discovered. Removing a day's history is not simply a matter of deleting data from a webpage; it requires network participants to adopt a different set of valid chain records. The practical consequences depend on the scope of the fix, the speed of node upgrades and whether exchanges and other service providers can update their systems in step with the network.
Zano disclosed the incident on September 25, 2026. Publicly confirmed facts currently include the inflation bug, the network rollback and the removal of one day's historical records. The technical cause of the vulnerability, the scale of the affected assets, the specific fix version and the handling of all external services have not yet been disclosed. Users and node operators will need to rely on the project's subsequent technical details and checks against on-chain data to verify the final status of balances and transactions.