On Thursday night, Cardano engineer Adam Dean tweeted that the Cardano testnet is in jeopardy since it is no longer compatible with the latest version of the blockchain client software.
Dean, a former member of the Cardano staking group and current lead ecosystem developer, revealed that the problem was identified when operators raced to update on the mainnet, resulting in incompatible forks that reduced chain density.
The developer also cautioned that Cardano’s development business, Input Output, could have jumped the gun in implementing Vasil on the mainnet. Not only did Dean voice his disapproval of the upgrading procedure, but so did many other well-known programmers.
Engineers Behind Cardano Issue a Safety Warning
At the time CryptoBriefing was picking up, Input-Output (IOG) had promised operators of decentralized participation groups that Cardano node version 1.34.2 had undergone extensive testing and was ready for deployment.
However, the ATADA and PoolTool operator communities found a severe issue in the client software that caused incompatible forks after most stake operators hurriedly upgraded to the version to imitate the Vasil hard fork event.
Following the discovery of the flaw, Cardano published updated client software (version 1.35.3), which, according to that media site, is presently operating on two separate test networks that lack any block history and cannot synchronize with the original test network. Charles Hoskinson, CEO of IOG and co-founder of Cardano, has requested that all operators update to version. To express their disapproval, Dean and influential community builder Andrew Westberg went public with their opposition to the proposal.
Westberg, another Cardano engineer, moved to Twitter to express similar sentiments to Dean’s, warning that version 1.35.3 was not ready and needed further testing. He tweeted that Hoskinson “is not on the same page with his DevOps and test teams,” and he urged the community to increase its testing efforts.
Dean went a step further, claiming that the whole Cardano network might have been put at risk by the next Vasil update, which would be implemented through a hardfork, or hard fork. As Bitcoinist highlighted, the developer also said in a podcast published today that the project narrowly avoided a catastrophic end.
Hoskinson’s response
The problems arise when users anticipate the Vasil update, which was set on June 29 but pushed back twice due to the need for more thorough testing.
The goal of the Vasil update to Cardano’s network is to make it more scalable. The transition to the new “Basho” era, which is defined as a stage of “optimization, improved scalability, and network interoperability,” has been anticipated as a result of this fork, making it one of the most significant developments in the cryptocurrency space since the September 2017 release of the Alonzo fork.
Hoskinson used Twitter to address the backlash he’d received. The creator disagreed with the developers and described their claims of a “rush” to deliver version 1.35.3 as “bizarre and alarming.”
Including SPO, everyone has spent months thoroughly testing the relevant code. The problematic code on the test network has been taken out.
“We, as a community, could, of course, wait a few months before releasing Vasil so that we may retest code that has already passed a dozen tests and is operational. Is it worthwhile for the DApp builders who have waited almost a year for this release? “And he went on to say.
In addition, Hoskinson complained that, despite the decentralized nature of the network, he was “weary of taking the blame” for the delays. Not me, but the network’s individuals have the last say on software revisions, he said.
Photo by Michael Förtsch on Unsplash.
© 2024 Cryptopress. For informational purposes only, not offered as advice of any kind.
