PANews, October 31: Privacy blockchain Iron Fish announced that it will terminate all remaining support for the Iron Fish network later today. The team stated that recent monitoring detected anomalous activity on the wIRON and ChainPort cross-chain bridge. After collaborating with ChainPort to investigate, they confirmed the root cause was an inflation vulnerability inherent to the Iron Fish blockchain itself. This vulnerability dates back to a commit in early 2019 in the implementation of the Merkle tree. At the time, the developer implemented a standard Merkle tree, but due to a subtle difference in how the note’s nullifier—the mechanism allowing users to spend their funds—was calculated, attackers were able to reuse the same note multiple times.
Privacy Blockchain Iron Fish Shuts Down Network Due to Critical Inflation Vulnerability
PANewsShare
Summary
The privacy-focused blockchain Iron Fish shut down its network on October 31 following the discovery of a critical inflation vulnerability. Abnormal activity was detected in wIRON and the ChainPort cross-chain bridge. The investigation confirmed that the flaw originated from a 2019 implementation error in the Merkle tree. This vulnerability allowed attackers to reuse nullifiers, generating false inflation data. The team announced a complete cessation of network support and stated that future network upgrades will no longer be pursued.
Source:Show original
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information.
Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.