Cardano developer reveals bug in node version 1.35.2

Please fol­low and like us:
Pin Share

Car­dano (ADA) devel­op­er Adam Dean in an August 18 Twit­ter thread, revealed a bug in Car­dano node ver­sion 1.35.2 that caused the col­lapse of Car­dano Testnet.

Accord­ing to Dean, the bug was dis­cov­ered in a node pre­vi­ous­ly said to be “test­ed and ready.”

Dean con­tin­ued that the bug cre­at­ed incom­pat­i­ble forks and reduced chain den­si­ty. The bug was dis­cov­ered by an on-chain inves­ti­ga­tion by Car­dano Oper­a­tor sup­port­ers’ pool, ATADA Stake­pool, and Pooltooll.

The inves­ti­ga­tion led to the dis­cov­ery of ver­sion 1.35.2 and ver­sion 1.34.1 as the issue.

Dean high­light­ed how most of the oper­a­tors had upgrad­ed “to 1.35.2 on test­net to sim­u­late a Vasil HFC event,” lead­ing to ver­sion 1.35.3 not being in sync with the chain.

Accord­ing to Dean, ver­sion 1.35.3 is now being test­ed on “two ‘new’ test­nets that do not have a block his­to­ry like test­net (hav­ing gone through all pre­vi­ous Car­dano HFC events there) or a sim­u­la­tion of mul­ti-node-ver­sion blocks on the chain.”

Dean men­tioned that the “rush­ing” of the Vasil hard fork makes him uneasy. He added that the Car­dano net­work was close to hit­ting a “nuclear rock.”

He is request­ing Input Out­put engi­neer­ing depart­ment and Charles Hoskin­son to deploy the appro­pri­ate Dis­as­ter Recov­er­ing tools as dis­closed dur­ing the test­net launch.

The Car­dano Dis­as­ter Recov­ery plan has the mit­i­ga­tion process for long-lived net­work-wide par­ti­tions or long-lived glob­al outages.

Hosinkson responds

Charles Hoskin­son has respond­ed to the community’s reac­tion to news of the bug in the test­net ver­sion 1.35.2.

Accord­ing to Hoskin­son, the noise sur­round­ing the stake pool oper­a­tors’ upgrade is bizarre, adding that “the code that was an issue on the test­net has been removed.”

Hoskin­son said the com­mu­ni­ty could still decide to delay the launch of the Vasil hard fork but won­dered if that deci­sion would be worth it for Dapp developers.

Mean­while, some Car­dano com­mu­ni­ty mem­bers have not tak­en Hoskinson’s com­ment prop­er­ly, but Hoskin­son urged them to upgrade their nodes to ver­sion 1.35.3.

Cardano’s Vasil upgrade has been delayed twice. Hoskin­son had revealed that the test­ing had uncov­ered three sep­a­rate bugs, with the devel­op­ment of three new soft­ware versions.



Source link

Please fol­low and like us:
Pin Share

Leave a Reply

Your email address will not be published. Required fields are marked *