Vasil Upgrade (Node Version 1.35.3)

hi everyone this is charles hoskinson broadcasting live from warm sunny colorado very brief very quick video i wanted to make to get ahead of a lot of the fun that's been floating around so there seems to be a strange series of dialogues that are occurring as it relates to node 135.3 and the current upgrade for fossil so here's what happened note version 135 was what we forked the test net with many people tested it many people used it but it turned out that there was a very subtle extremely strange bug in the implementation of the ec dsa implementation that we had which enabled support for bitcoin style cryptography which was necessary for a lot of bridge protocols that were coming fossil when the transactions were constructed in a certain way on the test net it would cause a soft fork on the test net so this caused obviously serious problem and because the test had already been forked and this bug was already there as a final stage of testing it basically broke the test net this has been known for quite some time and the response to it is just simply to roll back that feature and disable it so that it can be improved and corrected for the next hard fork post fossil two other bugs were discovered during additional testing some of those bugs on our side and some of those bugs independently replicated by the spf who chose to take an intermediate version 135.2 and actually deploy it on the mainnet all of these things have been resolved and the code in question that we're talking about for the vossel hard fork has been heavily heavily heavily tested survived the hard fork lived in a mixed node environment and it's even demonstrating that today on the main net because 17 of the sbos are running 135.3 i and we're in a situation where we have high confidence that the code we're looking at is pretty good now sbos can demand different testing regimes and they're free to do so and as stated and until 75 of the sbos upgrade we're not going to do a hard fork so they're in charge of the process of when and how fossil ships and there's been a great dialogue i believe there was a call yesterday or this morning where over 300 of the sbos attended that's what i was told and there was a strategy and plan for the types of testing scenarios that make them comfortable this is a normal process it's done on a regular basis again and again and again and again through all the hard forks we've been through together some of the sbos chose then to go and do interviews and it resulted in the creation of sensationless videos that basically implied that there's a lurking catastrophic potential bug and that the current cardinal code is not tested at all which is just not true yes a new test net could be completely respond and it may be worthwhile pursuing that short time or it could be worthwhile being a little bit more careful and spending a more capable test net that has more disaster recovery inside of it these things are being discussed at the moment post-mortem and retrospective is also being written up which will be quite exhaustive about how did this bug slip through with 135 which was released into the test net and forked on the testnet back and i believe in june and that will come but we have to deal with the problems of today which is getting fossil out and we have high confidence on our end that the engineering behind 135.3 is solid again sbos are independently able to verify that and test it themselves and have been working with our people to set up test environments that make them feel comfortable for the release somehow this was not good enough for certain sbos and then they decided to take to twitter reddit and their channels and now it's created a narrative that there's some sort of conflict or quality issue that we currently do not have we all get egg in our face when something is pushed to test that that shouldn't have been and the post boredom will be done a retrospective will be done but it's important to always take a look at things in the bounds of of where we're at at the moment the code in 135.

3 the vast majority of it is unchanged since 135. that code has already survived a hard fork that code has been extensively tested by dap developers that code has been tested again and again and that code is running on mainnet with some of the stake pool operators more than 10 it's running in a mixed note environment at the moment additional testing can and should be done okay but then it has to be made clear what are the goals in the specific test scenarios that people are interested in testing this was discussed in the call with the sbos a plan was reached and our people are working with them to accommodate what is unproductive is for this to spill out into youtube reddit and twitter it provides no value and all it's done is weapon weaponized and used to attack and degrade the project and imply that we're significantly far away from fossil forking we're significantly far away there's massive bugs or quality issues in cardinal that there's somehow a crisis in the cardinal ecosystem there is no crisis there is no issue things are for the most part working the very fact that the bug was discovered on the test net and that the testnet fell over is a good indication that the testing processes are working now it's not good that it's discovered very at the end because it slows things down it causes a loss of confidence you have to respond a lot of things that's fine but let's be clear here this was not a mainnet bug as for the discovery of 135.2 the issues was having in a mixed node environment we had yet to spin up an official release and that was one of the things to test in that release which would have been done so it was independently confirmed by people watching the mainnet who decided to upgrade to 135.2 that's great and we're happy that sbos are finding bugs that's a good thing it's a very good thing but again to infer that no testing has been done to infer that now we have to go back to the beginning and retest the code that's already been extensively and exhaustively tested again and again and again will not produce a different outcome all it will do is introduce months of delays for no additional value now if there are new test scenarios new test environments new test outcomes new types of tests that have not been run before then the time for that discussion is now in the dialogue between sam and our other people and the spos and we can certainly figure out scenarios that are reasonable and run those scenarios that's the point of the calls that's the point of the discord that's the point of these types of things it is not productive though to go to youtube reddit twitter and use that as the channel for a debate it's not informed it has no value as a medium and the best case scenario is people ignore the debate the worst case scenario is it gets weaponized to harm the branded reputation of the project it's that simple so i don't make these decisions cardano truly is decentralized and again no hard fork will occur until the sbos have upgraded at least 75 of them so it's actually in their hands about what they feel comfortable about and what they'd like to see and they'll make that decision not me all i can do is tell you where our confidence lies and our confidence does lie with 135.