Iron Fish shuts down its network over a 2019 inflation bug. Key analysis. Privacy blockchain Iron Fish is ending all network support after finding an inflation bug from a 2019 Merkle tree commit that let attackers double-spend notes. 4m 50s audio AI narration. Useful for scanning on the move. Names and tickers may be mispronounced. Iron Fish, a privacy-focused layer-1 blockchain, is ending all remaining support for its network after confirming an inflation vulnerability in its own code. The team disclosed the flaw on October 30, 2026, warning holders not to buy wIRON, the wrapped version of its token, while it winds the network down. The disclosure first circulated through a post from the DeFi aggregator DeFiPrime and was reported by TokenPost. A 2019 Merkle tree commit that went unnoticed for years. The root cause sits in how Iron Fish built its Merkle tree, the structure a blockchain uses to track which coins exist and which have already been spent. According to TokenPost, the defect was introduced in a code commit from early 2019, around the time the team first implemented that tree. It centered on the nullifier, a one-time marker that is meant to stop a given note from being spent twice. The logic guarding that marker was flawed, so the guarantee it was supposed to enforce could break. That is a quiet kind of failure. The code compiled, the chain ran, and for years nothing looked wrong. The error only mattered once someone found the specific path to trigger it. Double-spends that moved out through the wIRON bridge. In practice, the bug let an attacker spend the same privacy note more than once and then route the proceeds off-chain through ChainPort, the bridge behind wIRON. That is why the first sign of trouble was abnormal activity around wIRON and the bridge rather than the base chain. After a joint investigation, the team traced the cause to Iron Fish's own blockchain and not the bridge, and concluded the integrity of the ledger itself could no longer be trusted. An inflation bug is one of the worst failures a chain can carry. It lets value appear from nothing, which quietly dilutes every honest holder. On a transparent chain, counterfeit coins can at least be spotted by anyone auditing total supply against what the rules allow. On a privacy chain, where balances and transfers are shielded by design, the same opacity that protects users also hides fabricated coins. That combination is what turned a single logic error into a reason to close the network rather than patch it and carry on. A chain that was already winding down. Iron Fish was not a high-traffic network when the flaw surfaced. Its mainnet launched in April 2023, and the project entered maintenance mode in April 2026, meaning active development had already slowed to basic upkeep. The inflation disclosure turned that slow decline into a full stop. The team has submitted a patch and published a post-mortem in the associated pull request, and the code repository is being closed and archived. Shutting down is a heavier decision than it sounds. Once support ends and the repository is archived, there is no maintainer left to ship fixes, coordinate an exit, or respond if the flaw is exploited further. The network does not pause. It ends. Audits that missed a flaw hiding since 2019. The uncomfortable detail is that the bug survived both internal and external audits. A review inspects the code as written and the threat models the reviewers think to test against. A subtle error in nullifier handling, buried inside a Merkle tree implementation from 2019, is exactly the kind of deep-protocol defect that can pass every check and still be live years later. For holders, the practical reading is narrow but real. An audit is a snapshot of what reviewers found at one point in time, not proof that no inflation path exists anywhere in the code. A clean report lowers the odds of a flaw; it does not take them to zero, and the longer a chain runs, the more time an undiscovered path has to be found by someone who is not on the audit team. For anyone still holding IRON or wIRON, the window to act is set by the shutdown, not by the market. Holding your own keys protects you from an exchange collapsing, but it offers nothing when the chain an asset lives on closes itself down. With the repository being archived and support ending, there is no team left to patch around a stuck position, and the project's own guidance was blunt: do not buy wIRON. Overview. Iron Fish, a privacy-focused layer-1, is shutting down its network after confirming an inflation vulnerability rooted in a Merkle tree code commit from early 2019. The flaw broke the nullifier that is supposed to prevent double-spends, letting an attacker spend the same shielded note more than once and move the proceeds out through the wIRON bridge on ChainPort. Abnormal activity around wIRON surfaced first, but the team traced the cause to Iron Fish's own blockchain. The bug had survived internal and external audits. The network launched its mainnet in April 2023 and entered maintenance mode in April 2026; it has now submitted a patch, published a post-mortem, and is closing and archiving its code repository. Holders were warned not to buy wIRON as support ends. Recommended reading. Sources. Disclaimer This article is provided for informational purposes only and does not constitute financial advice. All fee, limit, and reward data is based on issuer-published documentation as of the date of verification. Discuss this analysis with the community on X. Recommended cards. Search. Quick Filters. Country. Advanced Filters

Coinbase has acquired the Iron Fish team to enhance privacy on its Layer 2 network, Base. The Iron Fish blockchain and token will remain independent, managed by the Iron Fish Foundation. This acquisition aims to integrate privacy features into Base, benefiting developers and users by ensuring secure, private, and compliant on-chain applications. Coinbase emphasizes its commitment to privacy as a core component of its mission to advance the on-chain economy.