Morning Edition · Monday, September 28, 2026Published at 1:43 AM EDT · New York
The privacy network restarted at block 3,833,000, the last block before the August hard fork that activated the broken feature, and says it will compensate users from team and large-holder funds rather than new issuance.

Zano, a privacy-focused chain with its own stablecoin, restarted its blockchain at block 3,833,000 after a defect in its Gateway Address feature allowed an attacker to create ZANO and Freedom Dollar (fUSD) tokens that the protocol never authorized. The chosen block sits immediately before Hard Fork 6, the August upgrade that activated the feature, so the restart erases roughly one month of transaction history.
The root cause was not a stolen key. According to the project, wallet keys were never compromised, and the flaw sat in the supply-creation path opened by the new gateway logic, which is the most serious class of failure for any chain whose value depends on a verifiable cap. Zano has not published a figure for the unauthorized supply created.
The limits of the remedy matter as much as the remedy. A chain restart cannot claw back value that already left the network, so any proceeds converted into Tether (USDT), Dai (DAI) or other assets on other chains stay with whoever holds them. MEXC suspended ZANO and fUSD deposits and withdrawals while it migrates to the recovered chain. Zano says reimbursement will draw on developer, team and large-holder funds, with no additional ZANO issued.
The incident sits alongside the recurring unauthorized-mint failures tracked by Rekt News, where the loss comes from a privileged path working exactly as coded rather than from a reentrancy bug.
Zano's team and large holders, who preserve the fixed-supply promise that gives ZANO and fUSD their value, and exchanges that avoid honoring balances created out of nothing, at the cost of users whose legitimate transactions inside the erased month disappeared.
The rollback, the block height and the compensation plan are , but the load-bearing detail is unpublished: no party has stated how much unauthorized ZANO and fUSD was actually created, and , so "attacker" is the project's characterization rather than a verified finding, and the MEXC suspension rests on the project's and the exchange's own notices.
Part of a tracked trend
Bridge and Mint Exploits Sustain Heavy DeFi Losses
Over 3-6 months, recurring bridge proof-validation and unauthorized-mint exploits keep monthly DeFi losses elevated, including drains of deprecated contracts.
Start a discussion in Townsquare.
More from this edition
An open-source-intelligence read of how likely this story is true with its real nuance, not a judgment of any outlet. It assesses the claim, weighing independent and adversarial reporting. How we label confidence.
What this means
The exposed parties are ZANO and fUSD holders, the exchanges that must reconcile balances across a reorganized ledger, and anyone who assumed a small privacy chain's supply is auditable in practice. The mechanism is supply integrity: once unauthorized units enter circulation on a chain where amounts are shielded, the only detection channel is the developers' own accounting, and the only cheap remedy is a coordinated rewrite of history. The precedent is Ethereum's 2016 DAO fork and Bitcoin's 2018 CVE-2018-17144 inflation bug, where the remedy was patch-and-social-consensus and the reputational cost persisted well beyond the technical fix. The likelier outcome over the coming weeks is that exchanges reopen ZANO markets after reconciliation while liquidity stays thin and the reimbursement pool is disputed by holders who transacted inside the erased month. That read would be wrong if Zano publishes a full accounting of the unauthorized supply and funds reimbursement without drawing on team balances, which would indicate the damage was small enough to absorb.
What to watch
Observations to monitor, not financial advice.
Synthesized from: crypto.news · Rekt News
Comments
0No comments yet.