Iron Fish Ends Network Support After 2019 Bug Minted 2.98B wIRON on Base
By Node Zero
October 31, 2026
Iron Fish said it is ending all remaining support for its privacy Layer-1 network after tracing abnormal wrapped-IRON activity to an inflation bug in the chain itself — not in the ChainPort bridge that carried the exit. In an October 30 statement, the team said it would shut down remaining foundation support and archive the ironfish repository after committing a patch and postmortem. The disclosure follows an October 28 warning that told users not to buy wIRON on Base or use the bridge until further notice because full 1:1 backing could not be assured. This Dev & Protocol Pulse file is an unused protocol-shutdown chapter, separate from this desk’s Initia restart calendar and from Binance’s still-open hot-wallet trail.
The root cause, per Iron Fish, sits in early-2019 Merkle-tree code that interacts badly with how a shielded note’s nullifier is calculated. Nullifiers are the public markers that should stop the same note from being spent twice. The team said nuances in that calculation let an attacker spend one note more than once, compound the resulting notes, and exit through ChainPort. Iron Fish said the affected path was inside both internal and external audit scopes, but reviewers did not catch the flaw. Treat that as the project’s own postmortem framing — not as an independent auditor’s signed finding.
On-chain color for the Base-side print comes from Bitquery, which reported that ChainPort minted about 2,977,027,045 wIRON — roughly 2.98 billion tokens — on Base on October 27 across 14 mint transactions that passed the bridge’s signature and maintainer checks. Bitquery put that mint total at about 38.7× the roughly 76.9 million IRON supply and said only about 2.93 million wIRON sat on Base before the attack. Two newly active wallets sold the minted tokens for about $197,400 in USDC and ETH; Bitquery traced about 53.90 ETH toward FixedFloat and a separate path that returned about 0.865 BTC through THORChain. That dollar figure is the sale proceeds Bitquery attributed to those two wallets — not a reconciled total loss for every holder or liquidity provider.
A bridge run followed the cheap mint. Bitquery counted 212 addresses burning about 192 million wIRON to claim native IRON, and said on-chain data alone cannot show whether ChainPort honored those claims. Iron Fish’s earlier warning already told users that full backing for wIRON could not be guaranteed. Protocol desks should keep the buckets separate: the Iron Fish statement owns the inflation-bug / network-support end; Bitquery owns the Base mint, sale, and burn tallies; neither source, on the public wraps reviewed here, publishes a final redeemed-IRON ledger for every burn request.
The patch Iron Fish committed — described in secondary wraps as fixing a “copied-empty-branch” rule in the note commitment tree — replaces copied empty branches with a distinguished empty-subtree value. Because that change alters consensus roots, reporting on the pull request says existing mainnet and testnet histories are incompatible with the fix; it is intended for a new chain started from a new genesis, not as a soft upgrade for the live history. That is the hard protocol beat: a privacy L1 that cannot hot-patch consensus roots after a multi-year nullifier alias has no clean mainnet rescue path once the bug is proven in the wild.
Context without rewriting closed stories. Iron Fish launched mainnet on April 20, 2023, after a $27.7 million Series A led by a16z in November 2021. In March 2025, Coinbase acquired the development team — including founder Elena Nadolinski — to build privacy tools for Base while stating it was not acquiring the network, token, or technology. On April 20, 2026, the Iron Fish Foundation moved the network into maintenance mode, ending grants and active development while still running bootstrap nodes, an explorer, and the site. Ending “all remaining support” withdraws that last foundation infrastructure commitment; it does not, by itself, prove every independently operated node has stopped.
Adjacent Orange County files stay separate. Initia’s audited MoveVM restart calendar, Binance’s EIP-7702 withdrawal rebuild, and Solana’s RWA ATH print are different desks. What this piece will not invent: a total IRON-holder loss beyond Bitquery’s wallet-sale print, a confirmed ChainPort payout schedule for the 192 million burned wIRON, or a claim that Coinbase’s Base product stack absorbed Iron Fish’s token liabilities.
Next protocol beat: Watch for the archived repository and postmortem PR to stay public as the technical record, any ChainPort notice on burn-claim handling for the Base run, and whether residual explorer or bootstrap endpoints actually go dark after the foundation’s support end — the patch itself does not revive the existing mainnet history.
Bottom line: Iron Fish is ending remaining network support after a 2019 nullifier/Merkle inflation bug let repeated shielded spends exit through ChainPort, while Bitquery’s Base tape shows about 2.98 billion wIRON minted against a ~76.9 million IRON supply — a privacy L1 with no soft-upgrade path for the live history.
Disclaimer: This article is provided for informational and educational purposes only. It does not constitute financial, investment, legal, or trading advice. The NFT market is highly volatile, and past performance is not indicative of future results. Readers should conduct their own research and consult qualified professionals before making any decisions related to digital assets. The cover image for this article may have been created using artificial intelligence (AI).
