🧵 (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...
(2/n) because operators rushed to upgrade on #Mainnet and it was creating incompatible forks and causing a decrease to chain density. #Kudos to @ATADA_Stakepool and @PooltoolI for doing the research of on-chain data to identify 1.35.2 v. 1.34.1 as the culprit...
(3/n) however, Testnet is still broken, due to the majority of operators having upgraded to 1.35.2 on testnet to simulate a Vasil HFC event there, 1.35.3 is now incompatible and incapable of syncing the chain, legacy installations are still on one fork or another...
(4/n) We are now testing 1.35.3 on two "new" testnets that do not have a block history like testnet (having gone through all previous Cardano HFC events there) or a simulation of multi-node-version blocks on the chain...
(5/n) To say that this level of "rushing" gives me uneasy feelings is an understatement. If there were a "nuclear clock" for #Cardano we got perilously close to hitting "midnight"...
(6/n) I'm calling on @IOHK_Charles and @IOG_Eng to develop and deploy the tooling necessary to "Disaster Recovery" the #Testnet as described here iohk.io/en/research/li…
Issuing a correction here after having a conversation with @therealdisasm (who if you know is like the Testnet Guru of IOG) :) The testnet is currently invalid (@CardanoHumpback) due to a feature change between 35.2 and 35.3 and because it had already gone through the fork...
Is incompatible with the current testnet. Strategies for regenerating testnet are being worked on :)
• • •
Missing some Tweet in this thread? You can try to
force a refresh
