Iron Fish Ends Network Support After Inflation Exploit
Iron Fish will end all support for its privacy blockchain after discovering an inflation bug that allowed an attacker to repeatedly spend the same assets and bridge newly created tokens to Base through ChainPort. The flaw stemmed from a 2019 Merkle tree implementation: a note could be presented at a different tree position and produce a different nullifier, evading duplicate-spend checks.
Base’s wIRON supply surged from about 3.93 million to more than 2.96 billion in under 16 hours—roughly 36 times the 76.97 million IRON in circulation. IRON fell about 77% in a week to roughly $0.017, leaving it with a market capitalisation of about $1.32 million.
Iron Fish merged a patch, but it changes the consensus Merkle root and is compatible only with a newly launched chain; there is no upgrade path for the existing mainnet. The team said it would archive the code repository and end network support. Because Iron Fish hides note positions, the amount created through the exploit cannot be reliably determined from on-chain data.
Bearish
The news is strongly bearish for IRON and negative for confidence in privacy-focused blockchain infrastructure. The reported exploit created severe uncertainty around wIRON’s backing: its supply rose to about 36 times the circulating IRON supply, while IRON lost roughly 77% in a week. Traders may continue to avoid IRON and wIRON, and liquidity could remain thin as holders reassess whether the bridged token has meaningful collateral or recovery prospects.
The team’s decision to end support, combined with the lack of an upgrade path for the existing mainnet, removes a clear technical route to restore confidence. This resembles other major bridge and protocol exploits, where uncertainty over losses and recovery plans has often driven rapid selling, reduced liquidity and heightened volatility. Here, privacy features also make it difficult to trace the exploit’s full scale, potentially prolonging uncertainty.
In the short term, expect elevated volatility, cautious trading and potential further pressure on IRON and wIRON. The longer-term impact is likely to be limited mainly to Iron Fish, but the incident may reinforce broader concerns about legacy code, audits and cross-chain bridge risk. A market-wide effect appears unlikely unless losses or contagion extend beyond the project.