0:00 Over the weekend, we saw the Condona blockchain suffer a major outage. Downtime was hacked. Something happened here. But I do have all the details, and I was online when a lot of this was happening as well. So I'm going to break down the myths and what actually happened 0:19 on the Kadona ecosystem, Who did it, why it happened, how it happened, and the ramifications of all this. In this video, I'm Peter at fits your first time here. 0:29 I hit that thumbs up light subscribe notification bell. My other camera is having issues at the moment. It's so hard at editing with it, so I'm swapping to a webcam at the moment, so that's the best I can do. 0:40 But hopefully it's not about the video. It's all about the content. And this is where we're at. So this is the main announcement from Intersect. So for those that don't know, those people that aren't in the Condona ecosystem, 0:53 Intersect is a members based organization that is there to look after the community. So this is the future of governance and inter Sect is the founding body to help along with all of that, and this is their announcement here. 1:05 So Kadana experience a temporary chain partition today after a malephone transaction triggered a bug into underlying software library. Now this was on the twenty second my time here in Australia, six am twenty second, so Friday of last week. There 1:21 is a big breakdown article here that does talk about it, but I won't go through the article in it's a bit lengthy here. If you want to read the details, I'll put links down below. But essentially we had a chain partition, so not a chain shut down, not a 1:37 chain stoppage. It wasn't hacked. The chain split essentially forked. 1:42 But this is a different type of fork. If you've been in the blockchain space for a long time, you would have known that Ethereum, for example, forked in the very early days from etherum as we know now to a theorem classic. So there's two ethereums and the theorem classic. 1:58 And this will happened because of massive hack and a massive amount of money was lost, so they had to roll back transactions, invalidate a whole bunch of them and say that this is now the main chain. We're raising the history of that particular hat. So it's not that 2:12 type of fork. This type of fork actually happens within the Cadana ecosystem all the time. Every now and then, every few blocks a fork may happen, and I'll go into the details of a breakdown in the moment about that. 2:24 But this here was a chained partition. That's why it's worded in that way. The real cause, the malformed delegation transaction exploited a de serialization code resolution. Spos just need to upgrade to the latest version of the node to 2:38 get past this user impact. No funds have been compromised. 2:43 Most wallets required no user action status. The network converging as majority of nodes upgrade. So okay, So that's the main article. This is the current version of the node. 2:53 If you are that interested, you can go through the code. 2:56 You can have a look at yourself. If you're a stateboard operator, please upgrade to this version of the node. Fortunately, I myself was on a particular version, a very old version, probably about a year old, and that was running just fine. 3:09 That was pushing through the blocks and we didn't have to do anything with that. Fortunately, I checked and verified on that night when I saw the news coming out about the they could done a chain not producing blocks, and they said that my particular version, I think it 3:23 was ten point one point four was perfectly fine. It was still going through, and I could see online that my blocks were still going through, and I could see here this is a snapshot of one of my relays that the blocks the last propagation block where it was 3:39 twenty seconds ago, which is kind of normal, and the earl was propagating through the network. I end up okay, So there was definitely some sort of issue. You can see here on the tip difference here three hundred and ive difference from the reference tip. So this is the slots. 3:55 This is when the chain's going along, it progresses up a particular number that the reference there. That's what it should have been. But it was definitely slowing down, and we could see that all on chain. Now, if we've rolled back a little bit a couple of days, on 4:09 the twentieth of November, this was spotted on the preview chain, so this they could see that something happened on the test net. It was foked into two and only one block producer was producing blocks. Then that slowed down and 4:28 eventually that wasn't producing blocks anymore. So what happened from this point is that someone saw this particular transaction, or someone tried this transaction on test net and went, hey, let's see what will happen if we take this transaction 4:43 onto main net. Will it destroy Kadano as we know it? 4:48 So unfortunately, this is the person that had done this particular transaction and this is for I'll play another clip in a second, and this is a person that did the transactions Statewoo prior to here rites SBO takes blame 5:03 for cyber attack unverified. It has been verified now if true, next year they can win most Impactful SPO. Definitely had an impact and this is what Homer J writes his pool here. His ticket is AAA. Note that I'll talk a little bit more about that later. Sorry, I know 5:20 the word isn't enough given the impact of my actions Kadana folks, it was me who engaged the network with my careless action yesterday evening. It started off as a let's see if I can reproduce that bad transaction personal challenge, 5:35 and then I was dumb enough to release it on mainenet. 5:37 And there's a lot more to this as well. Now there's some really weird stuff in here. And I've interacted with the Homer over the years, way back when I first started my statepol as well. Homa is one of those ogs. He's been in the ecosystem for a very 5:53 long time. It was a staatepole operator in the incentivized test net days, so this is before launched on MAInet, and I have to say every person interacted with that was around on the Cadona ecosystem in those days really knows their stuff when it comes to coding, when it 6:13 comes to network administration, when it comes to running and operating on a Linux operating system, they really know their stuff. 6:22 And Homer here is one of the ones that actually contributes to various bits of code that many statepool operators use. 6:32 You can pull I'll just pull this up here. So this here is the topology or the pools that are operating on the Cadna ecosystem. So what you see here, let me zoom in. This is the topology setup for the peer to peer network. That's all the relays out 6:51 there or the block producers use, and it sets up essentially some bootstrapping peers. Every node will connect to Kadana Foundation amergos and iog's bootstrapping peers. Then you can set up your local roots. Every staatepool operator will then connect 7:09 their relay to their other relays, so we run multiple relays and a block producer, so this is where it lets you set that up. And then you have back up access points here so you could connect to any of these. And these are the contributors to this bit 7:23 of code that was written up to make this all happen. 7:26 We have some well known pools here you can see their tickers PSB under ahl Cleo. But the one here AAA, this is homeless Pool is a contributor to this. He's been working. 7:38 You know. 7:39 I've seen posts say and comment on the fact that you know this kid whoever it is, vibe coded using AI to hack the Cadana ecosystem, and I just have to put a comment on that. And I really don't think Homer would have used AI to have done all this. 7:58 Maybe to help with a cleanup code or something, I don't know, but he wouldn't have just vibe coded his way into hacking this, especially when he is a contributor and has worked in the Kadana ecosystem as a staatepoard operator for over five years at least five, maybe six years. 8:17 I don't know the timelines, but he is definitely very skilled in what he can do within the Cadina ecosystem. 8:24 So here to rely on AI instructions on how to block all traffic in and out of Linux server without properly testing it first on test first, and then watch it in horror as the last block time, and then 8:35 watch in horror as the last block time on Explorers froze. Okay, Homer, Homer, Homer. 8:41 For those that don't know, to block traffic on a Linux server is simply one command line. You're probably using UfW like ultra friendly firewall what's the stand for I can't remember now, uncomplicated firewall. So to get that up 8:59 and running is literally one command line. It's not hard. 9:02 So it's one of those really basic things that you first do on every single node that you set up. 9:08 You've got to block all the traffic, and just one command deny or would have done all that. So I don't buy that comment there that you vibe coded into any of this stuff here. Anyway. There's a lot of stuff here. I won't go too deep into it anymore. 9:25 I'll let you form your own opinions about this, and who knows. There may be legal proceedings behind all this as well. And this is what Charles had to say about all this. And I will play this clip so you can listen to it as well. It has a 9:38 little bit of extra commentary here too, So let me just play this clip. 9:41 If this was a normal proof of stake network with bonding and slashing and checkpoints, you would have catastrophic fun and loss in the network, and you would also have to manually reset the network and reset a checkpoint. This was done in a decentralized way where one group US 10:01 issued the patch and then Intersect and many other organizations helped propagate it. But the network never went down and remediations rather straightforward or bors survived. The worst possible thing that can happen to a proof of state protocol and 10:16 that the network is relatively unharmed from that. This bug existed since twenty twenty two, and it was in an obscure cryptographic library and somebody discovered it on the test net and they tested it on the test net, breaking 10:31 it the minute that happened, so it was a targeted attack, premeditated. 10:35 It probably took several hours to figure out how to do it. Because nobody was talking on the ITN, you didn't tell anybody who was going to do it, and then deployed that transaction on main net, knowing full well it would create a network partition. So it was a 10:49 malicious act. When we looked at the transaction, the ATA that he used to do it came from a retired pool. 10:56 We were able forensically to trace that pool back to his ITN days where he actually used his real life human identity to register the website associated with his it stakepool. 11:07 And then after I broadcasted that information, then he issued a public apology and said it was an accident, didn't know what he was doing. But if you look at his history, he was in the fake for a discord. 11:17 His post history is extremely critical of input output and me in particular. There seemed to be a personal vendetta there. 11:24 It's important to point out that Cardino has been running for twenty four hours a day, seven days a week, and it did not stop running. The network did not halt during this incident. There were two chains that became one, but the original chain is still unbroken and unedited. The 11:40 chain is still immutable. And no double spends occurred on that chain, and no editing of the transaction history occurred on that chain. So if you came from you took a week off, and you came back and recinked your node, you would notice no discrepancies inside the system. So it's 11:56 another lie that's being propagated right now. The Twitter space that credit hit manually. There was a manual intervention. This was nothing of the sort of a giant proof of stake system recovering from effectively a network split almost like 12:11 a fifty one percent attack, and doing so in less than twelve hours. It has never happened in the history of proof of steak that they were able to put all those pieces back together without centralizing the network. 12:24 Yeah, so other chains where something bad has happened. A version of software went out that crashed it. I'm sorry Solana guys, I have to mention it. But a lot of the times when the Solana chain does go down, the entire chain needs to be shut down, stopped, nodes upgrade, 12:41 and then RECYNCD. At that point, this or Kadano, the chain did not stop. The chain kept on going, All the transactions kept on going through while things were being fixed nodes were upgrading, and then the two forked chains 12:56 merged back together. So we had the partitioning, the forking, and then it merged back together. And I think that's absolutely amazing on how that happened. And then there's some more comments here and I'll go into more technical details 13:07 about this. So Jane here wrotes, is it safe to assume that for the five hundred or so transactions that ultimately were not accepted during the art fork the forking event, the transaction fees were ultimately refunded, which, if true, is 13:22 pretty cool and definitely not what happens on many other chains. 13:26 And Nicholas here responds, it is similar. On any chain that forks, you are charged for what happened on the fork that survives. It's different than being charged for failing transactions. 13:37 These transactions didn't fail, they just did not exist. And the hosty wrotes, yes, it never happens, advocates, Yep, Jane gets it now. I don't want to put aside a lot of people that were actually affected. So the people 13:50 that going through and trying to do perpetuals using strike finance, and they were trying to put their orders through because they had big opportunities or going to be liquidated, and you know at that point in time, they would have 14:02 wanted to get their orders through. Fortunately, for a lot of those people, with the price of Ada was essentially unaffected by any of this. It remained at that zero point four forty cent mark throughout this entire event, and now it's going up again. So a lot of these 14:17 people that were trying to get orders through and transactions through probably could have recovered quite easily in a couple of hours afterwards because the price didn't move that much. 14:26 But anyway, from the event, the patches going through, a lot of people got together made this work fantastic. All the bad nodes nearly instantly swapped chains, which is absolutely amazing, and the consensus network protocols worked. We have proven it. 14:41 So this is one of the designs within Kadano itself. 14:45 Within the network, it's the knackomotor consensus algorithm that is supposed to self heal itself. If there's forks and stuff, it will self heal and then the majority of the chain with the majority of the steak would be the winner at the end. I thought this is pretty cool. 14:59 This is a online meeting between a bunch of operators and contributors that we're working through to try and fix all this, watching the graphs live as the bad chain was up and golded up by the main chain, the green one here, and I'll pull up this tweet here 15:17 from Marcus who actually explains this a little bit better so we know exactly what's going on here. So here's a quick update. How the good fork ate up the bad one or nodes on the red had now been converted to green. No more delta as there is no 15:31 more bad fork. If we zoom in a little bit, we can see this here. But all of this red line here is that bad chain as it's going through minting blocks, but as a convergence is happening, it can being converted into the green line here and then at 15:45 this point if you can just see it there, that's when the bad chain no longer exists. This purple line here, this is a divergence of blocks. So let me just read Marcus's explanation here. These are delta blocks between the two forks the outer right ye access. This metric initially 16:03 grew with more steak producing blocks on the bad chain. 16:07 Then sbos patch their nodes and move their steak to the good chain, at which point the purple line started decline as more a steak was placed on the good fork than the bad one. Now here's some more contexts for you. This is a screenshot that I managed to 16:20 capture in the morning after I woke up altually. Like I said, for me, I didn't have to stay up all night helping with this or upgrading my pool. My pool was fortunately on a older version which wasn't affected. 16:33 And here we can see the hype battles between the multi or the different pools out there. It's that three hundred hype battles here going through and then slowly diverging down to almost zero. So on a healthy epoch you do see this go up and down as hype battles 16:52 and slot battles happened between different state pools as they minting the same block. But of course this one was very different because of that giant forked chain. And here you can see a little bit more clarity. Here this is my pool of winning a hight battle between multiple 17:07 different pools that are trying to mint at the same time, and this one of these would have been on the incorrect chain. Fortunately, mine managed to win this one here and keep the chain going. So you can see three of them in a row here having this particular hyph battle. 17:22 This one here, This one is between two state pools. 17:25 Now this normally you don't see this many hype battles one after another like this. When you see it something like this, the chain has definitely foughked and something's going on here, and you can see each one of these state pools being paired off, trying to fight over which 17:39 block is a correct one and add it to the chain and add it to the longest chain. If you're wondering what this all is, that's what is happening under the hood here. Now there is also this really cool recording from the from pool tool here going through and 17:54 actually watching this all happen live. Unfortunately someone let me just pause. So fortunately someone recorded this so we could actually see it. So let me just play a little bit of this. It goes on for about to almost three minutes. Let me just play a little bit for it, 18:10 a little bit of it, and if you want to watch it all links down below that saw. 18:14 This is the big chain, the good chain. It's going to be catching up to the bad chain, right here. 18:19 This is just happening in real time. The only one geek out. 18:22 On this definitely something to geek out on, So I'll just pass forward a little bit. 18:26 There you go. 18:26 You can see the chain catching up here, and we're going through and having a look at the various hype battles that are happening at the moment. 18:34 Three six zero block come in right now. I thinks LCP won this one because that's all the data has. 18:39 But then we'll see the new block come in and it won't probably won't immediately be shown to be the winner, but it will be the winner because it's on the longest chain there comes because it's six blocks. So again, the hypo stuff is all figured out about ten blocks 18:54 past the tip, so we got a little ways to go before it actually assigns the winner to be Paul. 19:00 That's kind of cool. 19:00 Good work. They're poor for upgrading your pool, and which just fast forward a little bit more for you guys. 19:04 But you can see here this big long line here that that bar is growing in size and progressing along there as well in those Wow, I've never seen that either. 19:16 I've never seen that many pools have a height battle. 19:19 So one two three four five. That's incredible. This really was history in the making. There we go, the chains caught up. 19:25 You're done with that stupid problem, aside from of course replaying whatever other contained. 19:29 Now, Yes, that stupid issue is done and contained. Awesome to see and recorded there in real time and sorted out, so amazing, amazing stuff. Thank you for recording that as well. 19:40 That was brilliant. That was really cool. Okay, so let's go into some of the details here. So Bury Ales Ales here, creator of space Buds, was big in the Cadona ecosysm started off the NFT phase for the chain. 19:55 But here let me read out what he writes here. 19:58 It's a bit of a long thread. A lot of this is really good stuff. What is fascinating about yesterday's event is how Kadanu recovered from a minority chain and got rid of the symptom while preserving most of the history in progress since the incident. Let me explain what 20:13 I mean by recovering from a minority chain. I don't know the exact numbers, but I assume thirty to forty percent ran node a no bug that was my pool that was part of that. Around sixty to seventy percent ran Node B that had the bug. Once the malform 20:29 transaction was submitted, node A rejected It formed a minority chain, slower progress because of the lower stake. Node B accepted it formed majority change, faster progress because of the higher stake. 20:43 Now what it means by highering lower stake is that all the pools in node A collectively had less staked delegation to it, whereas the node B pools had more delegation to it. Normally, in a Knakamoto consensus like Kadano, 20:58 nodes followed the longest chain, but nodes A didn't switch to it because it violated their Ledger rules. So for a while, minority fork A lagged. Then sbos upgrade their nodes to the correct version. Stake on forked A gradually grew, 21:13 which it reached. Once it reached its tipping point of fifty one percent, fork A could start catching up to B. 21:20 That was the whole event here that we saw in the video recording. Eventually A became the longest chain and fort B was resolved, Yet most of the history and progress was preserved and the malform transaction removed. The network 21:33 recovered and self healed. Now I'm wondering how b FT style consensus eg Solana would have performed in such a case. First, some explanations. In a BFT style consensus, you need at least sixty seven percent votes to produce a block and 21:51 make progress. With less than sixty seven percent of nodes can't reach an agreement. With that being said, we have two scenarios. Scenario one forty percent run a Node A no Bug, sixty percent run Node B bug chain holts. 22:06 No progression possible because nodes can't reach an agreement. Sounds bad, but this is the best. What can happen here? Why now the malform transaction doesn't make it onto the chain. 22:18 A huge coordination needed to restart, which is why it's not always easy. Scenario two thirty percent run Node A no Bug, seventy percent run Node B bug. Block is instantly finalized with the malform transaction. Minority A tries to 22:33 reject the block that has no other choice than to halt. Meanwhile, Node B keeps progressing the chain. So if this scenario happens with this amount of state delegation to Node B being higher, I would have had to wake up in the middle of night and upgrade all of my nodes 22:51 to the latest one so that I wouldn't be missing out on statepool rewards, and my delegates wouldn't have been missing out on their state rewards. So continuing here, the symptom is now permanent in the system and there's no 23:04 recovery possible. Only solution is to coordinate hard fork from the symptom, but all progress and history since then is lost. 23:13 Financial damage could be huge. No matter how much we strive for perfect code, humans always make mistakes. What really matters is how a network responds when things go wrong and how easily it can recover. And I think that's 23:27 where Kadana shines and I have to completely agree here. 23:31 We were very lucky here that we had the right amount of delegation between the different nodes, we had a diverse amount of node versions running, and there it was easy enough for us to switch back away from the symptom, away from the bad chain that had the bug, and 23:49 move over to the correct chains. So I thought that was absolutely amazing. Now, how did the wider crypto community react to all this. There's a couple of different reactions, some good and some not so good. But let me start off with the good ones. This here. This is 24:03 from Tolly. He is a co founder of Solana, and he writes this, I am going out on a limb and actually saying that this is pretty cool. Knakamotor style consensus without proof of work is extremely hard to build. 24:19 The protocol functioned as designed in the presence of bugs. 24:23 That's his comment to bury Al's explanation of how Kadana recovered itself in this situation. Now, was this with good intent? 24:32 I don't know. It seems like Tolly here and Mertz, another co founder of Solana, have a bit of beef and it seems like he's doing this despite Mert. So I don't know what's going on here, but I have to say the crypto space is very fickled. A lot 24:48 of people in the space are arguing on semantics saying that it did go down, the chain split and forked, that it did cause downtime, and in a way it kind of did because Exchange's wallets had to stop processing various transactions. You could see on coinbase even they had 25:04 in their status monitor that Kadano transactions were stored. You know, there was a lot of people on x saying how bad it was that they were trying to move the Aida off coinbase. We will move it to coinbase, and it just didn't work because of various things had to 25:19 be halted. Now, the ramifications of all this were huge in that there's are now a lot of misinformation and media coverage of this. Anytime something happens in the Kadana ecosystem, the media jumps on and starts trashing it, spreading half truth, misinformation, 25:37 and generally giving the chain bad PR. Some would argue any PR is good PR, but in this case I have to say it's bad PR because of the misinformation that went through on crypto Twitter. So this is a post coin Telegraph for those that don't know. Coin Telegraph 25:54 is probably the biggest media cryptomedia outlet out there. Kadano suffered a chain partition after abnormal transaction triggered a code bug. 26:03 Reported reporting the incident, one cheeky x user claimed kadana MAInet is down and nobody has noticed it yet because nobody uses it. So yes, cheeky ex user did say that, but also a cheeky response here or cheeky reporting, I 26:18 should say, for choosing that particular quote to add into their post, they could have chosen anything else, maybe something from intersect, a actual official statement, but no, they decided to choose the one that would get them the most 26:32 level of engagement. So a lot of these posts out there were community noted. Cadana was never down. Block production continued. 26:40 And then linking off to the official incident report, Patrick Topley here from ndmaker pulled up some interesting data and this was during the suppose of downtime on chain the platform en Maker actually still managed to mint quite a 26:54 few NFTs of nineteen different projects. Fd market is overall pretty flat at the moment, so foraging ten isn't that much. 27:02 But the fact that these projects still could mint during the petitioning of the chain meant that you could see by evidence here from minting, evidence here from minting that the chain was still going so awesome there to see those type of stats come through. Now, if you want 27:19 a really deep retrospective of this entire incident, Andrew Westberg did a brilliant video here. I haven't gone through it at all, but it goes for just under twenty five minutes where he goes through what actually happened or the 27:32 technical details there, or the takeaways at the end as well from this particular event. So if you want to go through that, I have encouraged you to watch that video. 27:42 Andrew is the CEO of Manetta, the usd M stable coin on the Kadana ecosystem and also one of the very first staatepool operators in the ITN stage in that era from a blue cheese steakhouse, So do check out his stuff and his statepoo. Well, now just a couple 28:01 more posts here for you guys. This is the second attack on the Kadana ecosystem. So the first one was that massive spam attack of smart contracts where they cramped in one hundred and eighty three. I think it was smart contract executions on chain really tried to push it 28:19 as much as possible to try and make it fail, and that didn't go too well. It became a laughing stock and became a meme as well. And this second time slowed down the network that actually helped clear out a bug quicker than it would have if it wasn't 28:35 put into place. So at what point do people realize that they're helping not attacking. Now this yere was a video that Child's posted up. I think it was at three am. His time when this finally all fixed itself up. 28:49 But let me just play this clip here for you. 28:51 All day, Jair and I were with Agalos actually because he was in town for the workshops in meetings with the Cardinal Foundation Intersect and Amergo, and I personally would like to thank the Cardinal Foundation Intersect in Amergo for 29:07 their professionalism and their attentiveness. Here we all work together, set our differences aside as one team, and you know what, everybody was exactly what they needed to be. So I'm proud of their work, proud of the time and effort that they put in, and there was prompt and a 29:22 sort of communication through and so I'm glad that the institutions were able to do that whatever has been said in the past. Hopefully this can lead to a new chapter of collaboration. We'll see. But it was a good day, and I'm proud of the people that showed up, like 29:37 Marcus and others from the CF to work with us. 29:41 So that was a bright area. 29:43 See, I have to say that was a really good outcome from this particular event. They've always the founding entities have always been fighting each other for I don't know what it is really the history goes back quite far, but it was really good to see that at this 29:58 point when it was needed, entities, Intersect, Emergo, IOG, the Cadano Foundation, and the community everyone came together all at the same time to fix this issue, to respond to the mammoth effect, that this malformed transaction had coordinated communication 30:20 and got the message out there to everyone to upgrade to fix the issue as quickly as possible. So that was absolutely amazing from the coordination that was done. And like I said, I went to bed knowing that the issue was there, but knowing that I didn't need to 30:35 do anything at that point in time to waking up early and then finding everything already fixed, so I thought the response time was absolutely amazing. And then reading through all the communication and comms afterwards was absolutely stunning. So 30:49 this was really good to see from all the founding entities and everyone in the community. Now this is where I'll probably leave you, guys, and this is the final statement from Intersect here about the myths and facts of 31:01 what actually happened and what is going around at the moment. 31:04 So let me just read this one for you guys. 31:07 So if you are listening to the I read this out because a lot of people listen to the audio podcast and I get almost as many listens as I do views on YouTube, So I read this out for everyone that isn't watching. Okay. Myth one, Kadana went down. 31:23 Fact no, while using experience some disruption. This was slowed down due to a temporary chain split. Caadana continued producing blocks and maintained its integrity two. Myth two, Kadana was hacked. 31:36 Fact the core protocol, consensus, and cryptography were not compromised. 31:41 This was an edge case in node implementation. At three. 31:44 Nobody uses Kadanu and nobody noticed fact sbo's engineers, exchanges, wallets, and explorers reacted in real time, which is why the issue was contained so quickly. Myth four an AI using teenager brought the network down that a technically skilled individual 32:02 crafted and submitted the transaction after it was observed on the preview test net relevant authorities and law enforcement and law enforcement are being notified Myth five. So one essentially rolled back the chain. Fact independent, SBOS exchanges and relay 32:19 voluntarily upgraded to the fixed node version, allowing the healthy chain to outweigh the invalid one through normal roboris consensus, not centralized control. That is very true. I still haven't upgraded my nodes and it's still working just fine, so 32:35 I wasn't forced to response. Security and next steps. Ecosystem teams formed a joint incident squad, shipped patch software within hours, and followed established disaster recovery practices. DARA operates active bug 32:48 bounty and responsible disclosure program, which were bypassed in this case, so the incident is treated as potentially malicious and referred to authorities. A thorough retrospective will A thorough retrospective will 33:02 examine the incident in exhaustive detail, and the recommendations that spring from that will only make us stronger. Still, then, thank you Intersect for clarifying that. So there was a lot to go through there, guys, and if you made it all the way to the end here, thank you 33:15 so much for sticking with me. There's lots of ways that you can support the channel with the buy me a coffee links, Patreon memberships down below, and YouTube memberships as well. And if you can't do any of that, that's totally fine. You don't need to, you don't have to, 33:29 but if you can just hear that thumbs up like subscribe notification bell on your way out. And if you got something out of this, if you learn something new, if you aren't bullish on Kadana already, hopefully you are. 33:40 There's a lot to take out of this video and to know that something as robust as Kadana can survive this type of attack is absolutely amazing to see. Okay with that, guys, I'll see in the next video.
Community discussion