Iron Fish ends support. Its patch is not a repair of the existing chain.

Iron Fish has announced the end of its remaining network support after an inflation-bug investigation. Its published technical findings make an important distinction: the released fix is intended for a new chain, not a compatible upgrade to the existing mainnet's history.

Reports of the team's 30 October statement describe abnormal activity involving wrapped IRON and the ChainPort bridge. The team attributed the underlying fault to Iron Fish itself. That attribution should not be turned into an allegation that the bridge introduced the vulnerability.

The official postmortem explains how one owned note could be spent again without the duplicate-spend check recognising it. It traces the problematic tree-padding design to a February 2019 prototype. The finding concerns repeated spending of an attacker's own note; it does not establish an ability to spend any other user's note.

The document labels its conclusions draft technical findings and says historical transaction attribution remains open. Reproducing a code flaw does not, by itself, identify every affected transaction or quantify the loss. We are not attaching a speculative loss total to it.

Because the correction changes the chain's consensus roots, the document says it requires a new genesis. Existing balances are not thereby migrated or restored. Ending the team's support also does not prove that every independently operated node has stopped.