Mnamo Novemba 21, 2025, Cardano alikufa kwa saa 14 za kurekebisha mwenyewe. Huu ni uharibifu mkubwa zaidi wa huduma kwa Cardano katika miaka yake ya 8 ya kazi, na kama mwanzilishi muhimu katika mazingira ya Cardano, nilihisi kuwa ni fursa nzuri ya kutafakari juu ya kile kilichotokea vizuri, na kile tunachoweza kujifunza ili kuboresha ujasiri wa Cardano hata zaidi. Nimechagua kujenga kazi na kampuni kwenye Cardano. Wakati kitu kama hiki kinatokea, sitakuwa na ladha ya kushambulia chumba changu kwenye Twitter au kushiriki katika dunking ya pamoja. Majibu niliyopata yalikuwa ni ya kweli, kwa dhati, na baadhi ya kazi za nyumbani. **What happened \ A serialization bug caused a unidirectional soft-fork: one portion of the nodes rejected a transaction that the rest didn't. This was initially triggered in testnet, likely on accident, and a fix was identified and released quickly. Unfortunately, someone with deep familiarity with Cardano was able to reverse engineer how the transaction was constructed, and submitted it to mainnet. (You may see claims this was "vibe-coded"; that appears to refer to using AI to set firewall rules in an attempt to quarantine the transaction, not the attack itself.) Kwa bahati mbaya, hii ilikuwa kabla ya ufumbuzi ulipopata utambulisho mkubwa, na hivyo idadi kubwa ya nodes (wanao kwenye matoleo na makosa) walikubali, wakati miundombinu muhimu kama vile wallets, majaribio ya mstari, na kubadilishana, walikataa. Wakati wa waendeshaji wa node walitengeneza toleo la imara, mzunguko ambao ulikataa shughuli hiyo ulianza kukua kwa kasi zaidi kuliko mzunguko ambao ulikubali, na hatimaye ulichukua, kusababisha reorg ambayo iliboresha mzunguko. Kama sehemu ndogo ya kujivunia, zana za uchambuzi zilizoundwa kwa haraka ili kutatua tatizo lililotumika kutoka ), node mbadala kuandikwa katika Rust ambayo timu ya Sundae Labs ni mchango kwa. Hii ilikuwa uthibitisho mzuri wa mpango wetu wa kuleta utambulisho wa utekelezaji kwa Cardano. \ Real Impact \ In practice, the impact of this chain fork was severe, though not as severe as you might have assumed. The chain continued to produce blocks, and a majority of transactions made it into the surviving fork, though delayed. The monitoring infrastructure run by the CF detected a spike in transaction delays up to 5 minutes, but other users may have seen delays as long as 16-30 minutes, the longest gap between blocks. Some subset of users may also have been unable to submit transactions entirely, though this was due to faulty 3rd party infrastructure that was unable to follow either fork. Asilimia ndogo (3.3%, 479 kati ya 14401) ya biashara ilifanya katika mzunguko wa makosa, na hawakufanya katika mzunguko wa kuishi. **How I think about Blockchain Outages \ I've developed a personal taxonomy for categorizing large outages, from most serious to least: Ukiukwaji wa kiserikali, ambapo ahadi za msingi na uaminifu (kama vile saini za crypto) za blockchain zinaanguka 2. ledger bugs, ambapo kanuni za kiuchumi (kama vile sera ya fedha) ya blockchain ni kuvunjwa Ukiukwaji wa makubaliano yasiyoweza kurejeshwa, ambapo mtandao unaendelea kudumu Kurejeshwa ukiukwaji wa makubaliano, ambapo mtandao una fork iliyoishi kwa muda mrefu lakini hufufuliwa 5. mashambulizi makubwa ya mikataba ya smart, ambapo fedha za mtumiaji zinapoteza kutokana na makosa katika mikataba Kuondoka kwa makubaliano kamili, ambapo mzunguko unapaswa kusimamishwa na kuanza tena, kuunganishwa kupitia mamlaka ya kati Uharibifu wa huduma, ambapo shughuli zimetolewa kwa muda mrefu au taarifa isiyo sahihi inapatikana kwa watumiaji Matukio ya Cardano yanakabiliwa na mafanikio kama 4: makubwa, lakini inaweza kurejeshwa. Katika chapisho langu kamili la blogu, ninaonyesha mifano ya kila mmoja. **What went well \ This incident put Cardano's Ouroboros consensus through its paces: long forks like this are supposed to be exceedingly rare black swan events, but the design of the consensus protocol and networking stack anticipate and account for this. For example, the fact that it was able to self-heal is built into the protocol, and the way time is handled has a self-regulating lamport clock that gave the stake pool operators time to upgrade their nodes. Zaidi ya hayo, miundombinu ya ripoti na mawasiliano iliyohifadhiwa na mashirika ya waanzilishi kweli ilionekana, kwa sababu tumeweza haraka kupata macho kwenye tatizo na kuwasiliana kwa kiasi kikubwa. Hatimaye, ilikuwa uthibitisho mzuri wa chaguo la lugha ya Cardano. Makosa maalum yalikuwa yanahusiana na baadhi ya mipaka ya makosa ya kuangalia kwenye buffer ya ufungaji usioaminika. ya bug (kama sio hii moja kwa moja) inaweza kwa urahisi sana kusababisha ukiukwaji wa kiserikali kupitia utekelezaji wa msimbo wa mbali au sawa. **What broke down \ It became clear from the incident that we need better infrastructure around some wallets, dApps, and chain explorers. Many were unable to follow Katika baadhi ya kesi hii inaweza kuwa sababu ya usalama, lakini katika wengine ilikuwa tu ukosefu wa mipango ya ulinzi ambayo ilitangaza hali hii. Vivyo hivyo, hasa kama Cardano inaingia enzi ya utofauti wa wateja, ni wazi kwamba tunahitaji kuboresha vigezo vyetu vya majaribio ambavyo tayari ni kali. kwa sababu kiwango cha majaribio katika utekelezaji wa node ya sasa ni ya kipekee, lakini usahihi huo unahitaji kuboreshwa na standardized katika utekelezaji wote wa node. **Conclusion \ Blockchains are not immune to the Ni kawaida salama kudhani kwamba programu zote ni mfuko mmoja wa mtandao mbali na kuanguka kwa machafuko, kwa kudhani unaweza lakini kupata uchawi sahihi. Amani ya aina ya Hata hivyo Uharibifu wa Bias aina sawa ya bugs Kwa bahati nzuri, wengi (lakini sio wote) wa hizi hupatikana na watafiti wa usalama wenye dhamiri na kurekebishwa kabla ya kuwa na athari kubwa. Kesi hii ilikuwa kipimo na ilionyesha maeneo ambayo Cardano inaweza kuboresha wakati pia kuonyesha nguvu zake. Kwa Pi Lanningham, Mkurugenzi Mtendaji wa Teknolojia katika SundaeSwap Labs. Kwa Pi Lanningham, Mkurugenzi Mtendaji wa Teknolojia katika SundaeSwap Labs. Maelezo ya Labs
