‘ADA Whale’ Explains What ‘A Bet on Cardano’ Means

‘ADA Whale’ Explains What ‘A Bet on Cardano’ Means

August 14, 2022

On Saturday (August 13), one highly popular pseudonymous $ADA whale (“@cardano_whale” on Twitter) explained what category of investors are Cardano’s target audience.

Yesterday, “ADA Whale” told his over 110K Twitter followers:

One of those that replied to him was the operator of the UK-based VEGAS ADA Pool:

On Friday (August 12), “ADA Whale” provided a summary of IOG’s mid-month development update on the progress toward the Vasil upgrade:

He went on to say:

  • Under hood changes that help with performance and stability of node, most important: changed the way of dealing with consensus protocol – gone from “transitional to full Praos” – Technical change that will lead to code simplication (maintainability + stability of code base)
  • New pre-production mainnet environment is being spun up to test – Hard fork go ahead indicator is whether 1. SPOs are ready (75% upgrades to node) 2. exchanges are ready (25 exchanges with 80% liquidity ready) 3. dapps are ready (top 10 dapps by TVL closely involved)
  • TLDR it’s coming, chill out lol


On August 1, Charles Hoskinson, Co-Founder and CEO of IOG, the company responsible for Cardano’s research and development, shared some important news about the upcoming Vasil hard fork, which recently got delayed by “a few more weeks.” The IOG CEO released a short video, in which he explained why the Vasil hard fork had been delayed for a second time and provided a status update regarding the testing of the Vasil protocol update.

Hoskinson said:

Originally, we planned to have the hard fork with 1.35, and that’s what we shipped to the testnet. The testnet was hard forked under it. And then a lot of testing, both internal and community, were underway. A collection of bugs were found: three separate bugs that resulted in three new versions of the software. And now, we have 1.35.3, which looks like it is going to be the version that will survive the hard fork and upgrade to Vasil.

There’s a big retrospective that will be done. The long short is that the ECDSA primitives and amongst a few other things are not quite where they need to be. And so, that feature has to be put aside, but all of the remaining features, CIP 31, 32, 33, 40 and other such things are pretty good.

So those are in advanced stages of testing, and then a lot of downstream components have to be tested, like DB Sync and the serialisation library, and these other things. And that’s currently underway. And a lot of testing is underway. As I mentioned before, this is the most complicated upgrade to Cardano in its history because it includes both changes to the programming language Plutus plus changes to the consensus protocol and a litany of other things, and was a very loaded release. It had a lot in it, and as a result, it’s one that everybody had a vested interest in thoroughly testing.

The problem is that every time something is discovered, you have to fix that, but then you have to verify the fix and go back through the entire testing pipeline. So you get to a situation where you’re feature-complete, but then you have to test and when you test, you may discover something, and then you have to repair that. And then you have to go back through the entire testing pipeline. So this is what causes release delays…

I was really hoping to get it out in July, but you can’t do it when you have a bug, especially one that is involved with consensus or serialisation or related to a particular issue with transactions. Just have to clear it, and that’s just the way it goes. All things considered though, things are moving in the right direction, steadily and systematically…

The set of things that could go wrong have gotten so small, and now we’re kind of in the final stages of of testing in that respect. So unless anything new is discovered, I don’t anticipate that we’ll have any further delays, and it’s just getting people upgraded…

And hopefully, we should have some positive news soon as we get deeper into August. And the other side of it is that no issues been discovered with pipelining, no issues of been discovered with CIP 31, 32, 33 or 40 throughout this entire process, which is very positive news as well, and given that they’ve been repeatedly tested internally and externally by developers QA firms and our engineers, that means there’s a pretty good probability that those features are bulletproof and tight. So just some edge cases to resolve, and hopefully we’ll be able to come with a mid-month update with more news.


Image Credit

Featured Image via Unsplash

Source: Read Full Article