Zano faces 24-hour rollback after asset issuance flaw

HACK OR EXPLOITZano faces 24-hour rollbackafter asset issuance flaw49IMPORTANCECLOSED6NEWS MEDIA8PIECESSep 27, 2026 16:40blockboard.net
In Layer 1 Privacy

Zano restarted its blockchain from block 3,833,000 after a Gateway Address flaw let unauthorized ZANO and Freedom Dollar enter circulation. The recovery sits just before Hard Fork 6 and removes about one month of chain history, with service providers required to upgrade before transfers resume.

Share on X Share on Telegram Share on Reddit Share on WhatsApp

What this rests on

Claim by claim, with its source
✓
The emergency update disabled Gateway Addresses and excluded roughly one month of transactions from the recovered chain.
Zano Restarts Blockchain at Block 3,833,000 After Vulnerability
✓
Service providers must upgrade before resuming transfers.
Zano Restarts Blockchain at Block 3,833,000 After Vulnerability
✓
Zano restarted its blockchain from block 3,833,000 after a Gateway Address vulnerability let unauthorized ZANO and Freedom Dollar tokens enter circulation.
Zano restarts chain at block 3,833,000 after exploit Zano restarted from block 3
✓
The recovery point is immediately before Hard Fork 6, which activated Gateway Addresses in August.
Zano restarts chain at block 3,833,000 after exploit Zano restarted from block 3
✓
The unauthorized coins were indistinguishable from legitimate ZANO, and the team said it could not remove them without rolling back the blockchain.
Zano exploiter created 36.9M unauthorized ZANO before blockchain rollback
✓
The attacker first minted about 18.4 million ZANO on August 29, repeated the exploit on September 25, and then created a larger fUSD supply.
Zano Attacker Minted 36.9M ZANO, 1.8 Quadrillion fUSD Before Rollback

What it means

Who it affects, what changes and what is still unconfirmed

Each sentence links inside to the piece that supports it.

Users and service providers on Zano notice the change through the restored chain and the required software upgrade before transfers resume. That means the network is not simply continuing on the same history; the recovered chain starts from block 3,833,000 and leaves out about one month of transactions.

Before this recovery, unauthorized coins could enter circulation through Gateway Addresses, and the response now disables that feature on the recovered chain. What stays in place is the recovery point at block 3,833,000, which sits just before Hard Fork 6 and marks the boundary of the rewritten history.

Market reaction

ZA Zano it is the asset of the company or protocol in the event from 2 h before to 4 h after the line marks the first headline
published
-3.64 % before publication
-0.47 % after
$6price at publication
12series points

The move was larger before the first headline than after. That is an observation, not an explanation: the market also moves on things nobody publishes.

How the story was built

Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.

first
Sep 26 08:18
CR Cryptopolitan scoop
Breaks the event
+1 d 16 h
Sep 28 01:09
Cointelegraph context
Its angle: introduced, height, came
+1 d 20 h
Sep 28 04:49
crypto.news echo
No new facts: erasing
+2 d 5 h
Sep 28 13:34
Crypto Economy context
Its angle: investigation, participants, blockchains; with quotes
+4 d 20 h
Oct 1 04:20
+5 d 20 h
Oct 2 05:02
Cointelegraph echo
No new facts: indistinguishable, exploiter, leaving
+6 d 8 h
Oct 2 16:51
Crypto Economy context
Its angle: approximately, contributions, coordination; with quotes
+6 d 17 h
Oct 3 02:00

Thefts of a similar size

WhenWhat happenedFigure
1.7 years ago LIBRA incident $250M
8.5 years ago Gate · Private key compromised incident $235M
2.2 years ago WazirX: India · Signer Phishing incident $234.9M
1.4 years ago Cetus incident $230M
2.2 years ago WazirX incident $230M

4200 incidents stored · 30 were as large as this one or larger ($250M)