Discover our report on the liveness vulnerability that led to the publication of Mumbai 2 on March 7th. Full report 👉 https://research-development.nomadic-labs.com/Mumbai2-incident-report.html Key Facts 👉 An “inconsistent hash” error was reported on Ghostnet test network at level #2,022,087. 👉 Tezos Networks were safe, but the issue could slow down or halt block production. 👉 Root cause was found to be an inconsistency in the Tezos protocol cache. 👉 A patched Mumbai proposal, Mumbai 2, was published, and the community was given the option to adopt the patched proposal by upgrading to #Octez v16.1 before activation. 👉 Following the user-activated protocol override, Mumbai 2 activated successfully. ✅ Our investigation found no evidence of the vulnerability having been triggered – or of attempts to trigger it – on Mainnet.