Some Brief Comments on Vasil

hi everyone this is Charles hoskinson broadcasting live from warm sunny Colorado always warm Always Sunny sometimes Colorado so today is August 1st 2022 and I wanted to make a video now that I'm back here in Colorado as some of I was in Mongolia Italy Greece and Spain over the last two weeks a variety of different things some business developments some internal strategy workshops and then some external vendors that we had a chance to meet up with all while running around we've also had to deal with fossil so where are we at what's going on so originally we planned to have the hard fork with 1.35 and that's what we shipped to the test net the test net 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 135.3 which looks it is going to be the version that will survive the hard fork and upgrade to Fossil there's a big retrospective that will be done but 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 sip 31s 32 33 sip 40 and other such things are pretty good so those are in advanced stages of testing and that a lot of Downstream components have to be tested like dbsync and the serialization librarian 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 as well as changes to the consensus protocol and a Litany of other things and it 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 and the problem is that every time something is discovered you have to fix it but then you have to verify the fix and go back through the entire testing pipeline so you get to a situation where your 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 so originally the net was no earlier than late June and we were able to Fork the test net and once we had that people were deploying and building and a lot of things work very well the new plutus features for example many apps have already upgraded and tested that and we gained an enormous amount of insight Knowledge from that other things that were new new bugs discovered and that's anticipated and expected but in the process of fixing those you have to then deploy a new node version which is 135.