Testnet Is Catastrophically Broken Due To A Bug: Cardano Developer

<div> Testnet is catastrophically broken due to a bug, according to Cardano developer Adam Dean, who Dean stated that a severe problem is affecting the network’s testnet. The foundation is still scrambling to discover this catastrophe recovery mechanism in time for the forthcoming Vasil hard fork. <h4>Testnet Is Catastrophically Broken, Cardano Developer Says</h4> Adam Dean, a famous Cardano engineer, recently warned on Twitter that the blockchain’s testnet is “catastrophically” damaged owing to a newly found fault. 🧵 (1/n) It's important to point out today that the <a href="https://twitter.com/hashtag/Cardano?src=hash&ref_src=twsrc%5Etfw">#Cardano</a> <a href="https://twitter.com/hashtag/Testnet?src=hash&ref_src=twsrc%5Etfw">#Testnet</a> 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) <a href="https://twitter.com/adamKDean/status/1560295448333520896?ref_src=twsrc%5Etfw">August 18, 2022</a> The flaw was discovered in Cardano Node v1.35.2, the foundation for the impending Vasil hard fork. This was allegedly caused by the pool operators hurrying to update the mainnet, resulting in incompatible forks and a decrease in chain density. “This was the version that we had previously been told was “Tested and Ready” for the Vasil Hardfork. This bug was only discovered…” he said. <h4>Will It Set Back The Vasil Hard Fork?</h4> Adam pointed out that, because the bulk of operators on testnet have updated to 1.35.2, 1.35.3 is now unable and incompatible with synchronization. He added that 1.35.3 is now being tested on two fresh testnets with no block history. <a href="https://twitter.com/cardano_updates/status/1559568124781154304?ref_src=twsrc%5Etfw%7Ctwcamp%5Etweetembed%7Ctwterm%5E1559568124781154304%7Ctwgr%5Ee9a0cb3470322d4439c60b2c184f95728cf3027c%7Ctwcon%5Es1_&ref_url=https%3A%2F%2Fu.today%2Fcardano-vasil-release-of-latest-specification-to-speed-up-integration">According to recent ADA team updates</a>, the team has released Cardano Rosetta 1.8.0, which allows for the inclusion of the Vasil hard fork. The news was made on Twitter via the Cardano Updates account. Cardano Rosetta is a collection of features and technology meant to facilitate Cardano integration. Rosetta will primarily act as an integration tool, facilitating and hastening the integration of Cardano’s Vasil hard fork. It is unclear whether the Vasil hard fork update will be delayed further now that the devs have uncovered the flaw. Cardano’s hard fork was set to launch on the network in July. It has been postponed due to delays, and the community should expect future updates when new information becomes available. As expected, the delays and mounting problems with the promised improvement have irritated a large segment of the population. “This is unacceptable for a blockchain that has built its reputation on the robustness of its research and technology,” said a Cardano enthusiast. “Communication around Vasil is not really what I’m expecting… many people are claiming 1.35.3 as final version and pushing for upgrade but I haven’t seen yet a clear confirmation and announcement. Something weird to me here is happening… doesn’t give me full confidence.” wrote another member or the community. Read the <a href="https://www.dcforecasts.com">latest crypto news.</a>

                            <p>DC Forecasts is a leader in many crypto news categories, striving for the highest journalistic standards and abiding by a strict set of editorial policies. If you are interested to offer your expertise or contribute to our news website, feel free to contact us at <a href="https://www.dcforecasts.com/cdn-cgi/l/email-protection#acc9c8c5d8c3deecc8cfcac3dec9cfcddfd8df82cfc3c1"><span data-cfemail="a2c7c6cbd6cdd0e2c6c1c4cdd0c7c1c3d1d6d18cc1cdcf">[email&nbsp;protected]</span></a></p>
                                                                
                                                        </div>