Adam Dean, Prominent Cardano Developer; Testnet ‘Catastrophically’ Broken

• One of the most prominent Cardano developers Adam Dean informed the Cardano Community that Version 1.35.2 blockchain’s testnet is “catastrophically” broken.
• Version 1.35.2, contained a precarious bug as a result of stake pool operators’ hastiness to release the testnet.

Adam Dean, Cardano developers enlightened the Cardano circle through a tweet that  the recently released testnet is ‘catastrophically’ broken

🧵 (1/n) It's important to point out today that the #Cardano #Testnet is **catastrophically** broken due to a bug in Cardano Node v 1.35.2. This was the version that we had previously been told was "Tested and Ready" for the Vasil Hardfork. This bug was only discovered…

— Adam Dean (@adamKDean) August 18, 2022

Findings by stakepool and Pooltool recognized version Version 1.35.2 was broken Stakepool operators rushed to upgrade on the Mainnet leading to the version creating incompatible versions

A testnet is a sandbox environment running upgraded software, used to test the behavior of decentralized applications before the new software is deployed on the main blockchain or mainnet.

In readiness for the Vasil HFC event, many operators had upgraded to version 1.35.2 but the Testnet is already Broken. Version 1.35.3, released earlier this week, is now discordant and incapable of syncing the chain. The testnet is being tested on two other Testnets that have no record of block history.

Adam Dean is calling upon Input Output and CEO Charles Hoskinson to apply the necessary tooling stated int the Disaster Recovery Plan

I’m calling on @IOHK_Charle and@IOG_Eng to develop and deploy the tooling necessary to “Disaster Recovery” the #Testnet as described here

The Cardano community has not taken the matter lightly as they expressed their opinions. A tweeter user by the handle @Cardano_HRguy wrote; “This is unacceptable for a blockchain that has built its reputation on the robustness of its research and technology,”

The upgrade has been postponed several times due to technical matters. 75% of SPOs are required to upgrade to version node version 1.35.3, Unfortunately, only 14% have upgraded.