Input Output Hong Kong (IOHK), the blockchain company behind the Cardano network, says the long-awaited Vasil hard fork is “getting closer and closer” after revealing the status of three important signs that would trigger the mainnet update.
In a Twitter thread on Thursday, IOHK told its 265,800 followers about the “rollout progress” of the Vasil upgrade. This included updates on the “three crucial mass indicators” that will determine when the mainnet update will happen.
This includes 75% of mainnet blocks being made by nodes running 1.35.3, around 25 exchanges being updated (representing 80% of liquidity), and the top 10 most important decentralised apps (DApps) on the mainnet also being updated.
On Thursday, the blockchain startup said that Stake Pool Operators (SPOs) using the most recent node 1.35.3 now account for 42% of mainnet block generation in the current epoch, surpassing the 75% threshold.
According to IOHK, one of the world’s leading cryptocurrency exchanges, Binance, has apparently updated its Cardano nodes to the most recent version. The company plans to update its nodes on about 25 exchanges, which would make up about 80% of the total liquidity of its native coin.
Concerning its mainnet DApps, IOHK said it will continue to work closely with several of the DApp teams on Cardano. Four out of ten DApp teams said they are actively testing against node 1.35.3 on the pre-production testnet.
Also, IOHK said that no new flaws have been found. There are still nine small issues to fix, but none of them would cause an unexpected hard fork.
What is the status of Cardano’s testnet and the Vasil hard fork?
The long-awaited change to Vasil is meant to reduce the size of transactions, increase network traffic, and cut costs.
After IOHK released a roadmap on May 19 that said a hard fork would happen on June 29, the Vasil upgrade has been delayed while engineers make sure the network switch goes smoothly.
Recently, Charles Hoskinson, co-founder of Cardano, replied to accusations that the update was rushed. He suggested that the launch be put off for months so that the code, which has already been tested and is working, can be tested again. However, the DApp developers would not find this helpful, since they have already been waiting for so long.
