According to Charles Hoskinson, the Vasil upgrade won’t affect the way Cardano’s smart contracts work. Hoskinson asserted on Twitter that the blockchain’s smart contracts will continue to work after the adoption of the eagerly anticipated upgrade, dispelling fear, uncertainty, and doubt (“FUD”) about the impending Vasil hard fork.
On Wednesday, numerous Twitter users claimed that Cardano’s smart contracts needed to be rewritten because they were incompatible with the Vasil hard fork. Vice-president of community and ecosystem at Input Output, Tim Harrison, was quick to refute these rumors. He clarified that upon the Vasil upgrade, existing decentralized applications (dApps) that utilize the Plutus smart contract platform’s initial release will still function properly. The Plutus V2 innovations must be used and implemented in apps by developers if they want to benefit from all of them. A new audit can be necessary because of significant code changes.
During the September distribution of the Alonzo hard fork, Cardano finally introduced smart contracts. The occasion led to fresh record highs for the native ADA cryptocurrency.
The inclusion of reference inputs, inline datums, and reference scrips in the Vasil hard fork is anticipated to further enhance the Plutus script.
The Vasil upgrade was activated on the Cardano testnet in early June. The launch of Vasil’s mainnet is now anticipated for this month’s end.
Cardano’s next wave
Input Output CEO Charles Hoskinson took to Twitter to tease Cardano’s “next wave.” The American businessman is undoubtedly referring to the impending Vasil hard fork, which is anticipated to go live later this month.
Sebastien Guillemot, CTO and co-founder of blockchain-based product startup dcSpark, outlined how the execution of the much-awaited upgrade will make it possible to transfer new varieties of tokens from Ethereum to Cardano. Stablecoins, non-custodial tokens, and stateful tokens were particularly mentioned by Guillemot in his tweet.
The aforementioned token types will be supported at the protocol level; however, it will take “some time” for the tooling to be developed.
