On Nov. 21, Cardano’s mainnet bifurcated into two competing histories after a single malformed staking-delegation transaction exploited a dormant bug in newer node software program.
For roughly 14 and a half hours, stake pool operators and infrastructure suppliers watched as blocks piled up on two separate chains: one “poisoned” department that accepted the invalid transaction and one “wholesome” department that rejected it.
Exchanges paused ADA flows, wallets confirmed conflicting balances, and builders raced to ship patched node variations that may reunify the ledger underneath a single canonical historical past.
No funds vanished, and the community by no means absolutely halted. Nonetheless, for half a day, Cardano lived the situation Ethereum’s client-diversity advocates warn about: a consensus break up triggered by software program disagreement moderately than an intentional fork.
Cardano co-founder Charles Hoskinson mentioned he alerted the FBI and “related authorities” after a former stake-pool operator admitted broadcasting the malformed delegation transaction.
Legislation enforcement’s function right here is to analyze attainable felony interference with a protected pc community, underneath statutes just like the U.S. Laptop Fraud and Abuse Act, since intentionally (or recklessly) pushing an exploit to a stay, interstate monetary infrastructure can represent unauthorized disruption, even when framed as “testing.”
The incident presents a uncommon pure experiment in how layer-1 blockchains deal with validation failures.
Cardano preserved liveness, blocks saved coming, however sacrificed momentary uniqueness, creating two legitimate-looking chains that needed to be merged again collectively.
Solana, against this, has repeatedly chosen the other trade-off: when its single consumer hits a deadly bug, the community halts outright and restarts underneath coordinated human intervention.
Ethereum goals to sit down between these extremes by working a number of unbiased consumer implementations, betting that no single codebase can drag all the validator set onto an invalid chain.
Cardano’s break up and the velocity with which it resolved take a look at whether or not a monolithic structure with model skew can approximate the protection properties of real multi-client redundancy, or whether or not it merely obtained fortunate.
The bug and the partition
Intersect, Cardano’s ecosystem governance physique, traced the failure to a legacy deserialization bug in hash-handling code for delegation certificates.
The flaw entered the codebase in 2022 however remained dormant till new execution paths uncovered it in node variations 10.3.x by way of 10.5.1.
When a malformed delegation transaction carrying an outsized hash hit the mempool round 08:00 UTC on Nov. 21, newer nodes accepted it as legitimate and constructed blocks on high of it.
Older nodes and tooling that had not migrated to the affected code path accurately rejected the transaction as malformed.
That single disagreement over validation break up the community. Stake pool operators working buggy variations prolonged the poisoned chain, whereas operators on older software program prolonged the wholesome one.
Ouroboros, Cardano’s proof-of-stake protocol, instructs every validator to comply with the heaviest legitimate chain it observes, however “legitimate” had two totally different definitions relying on which node model processed the transaction.
The outcome was a stay partition: each branches continued producing blocks underneath regular consensus guidelines, however they diverged from a standard ancestor and couldn’t reconcile with out handbook intervention.
The sample had appeared on Cardano’s Preview testnet the day earlier than, triggered by practically an identical delegation logic.
That testnet incident alerted engineers to the bug in a low-stakes surroundings. Nonetheless, the repair had not but propagated to mainnet when a former stake-pool operator, who later claimed he adopted AI-generated directions, submitted the identical malformed transaction to the manufacturing community.
Inside hours, the chain had break up, and infrastructure suppliers confronted the query of which fork to deal with as canonical.
Secure failure with out a kill change
Cardano’s partition resolved itself by way of voluntary upgrades moderately than emergency coordination. Intersect and core builders shipped patched variations of node, 10.5.2 and 10.5.3, which accurately rejected the malformed transaction and rejoined the wholesome chain.
As stake pool operators and exchanges adopted the patches, the load of consensus step by step tipped again towards a single ledger.
By the top of Nov. 21, the community had converged, and the poisoned department was deserted.
The incident uncovered an uncomfortable hole: two canonical ledgers existed concurrently, however a number of boundaries prevented it from cascading right into a deep reorganization or everlasting lack of finality.
First, the bug lived in application-layer validation logic, not in Cardano’s cryptographic primitives or Ouroboros’ chain-selection guidelines. Signature checks and stake weighting continued to function usually. The disagreement centered solely on whether or not the delegation transaction met ledger validity circumstances.
Second, the partition was uneven. Many vital actors, together with older stake pool operators and a few exchanges, ran software program that rejected the dangerous transaction, making certain substantial stake weight remained behind the wholesome chain from the beginning.
Third, Cardano had pre-positioned a disaster-recovery plan underneath CIP-135, which documented a course of for coordinating round a canonical chain in additional excessive situations.
Intersect is ready to invoke that plan as a fallback, however voluntary upgrades proved ample to revive consensus underneath regular Ouroboros guidelines.
The slim scope of the bug additionally mattered. The flaw affected a particular hash deserialization routine for delegation transactions, a bounded assault floor that could possibly be patched and closed with out requiring broader protocol modifications.
As soon as mounted, the exploit path disappeared, and no generalizable class of malformed transactions remained obtainable to set off future splits.
| Time (UTC) / Date | Section | What occurred | Detection / sign | Mitigation step |
|---|---|---|---|---|
| Nov 20, 2025 – night | Testnet precursor | Malformed delegation transaction is submitted on the Preview testnet and exploits a dormant deserialization bug within the hash-handling code, making a break up between a “poisoned” and “wholesome” testnet chain. | Engineers and SPOs see anomalous behaviour on Preview; incident is logged and a technical response ready in a single day as a result of the bug is clearly reproducible. | Core groups start creating and testing a hotfix and up to date node binaries so the identical malformed sample might be rejected in future. |
| Nov 21, 2025 – round 08:00 | Malformed tx hits mainnet (T0) | An virtually an identical malformed delegation transaction is broadcast on Cardano mainnet from a pockets later tied to a former stake-pool operator. Newer node variations settle for it; older variations reject it, creating two competing chains. | Block explorers and monitoring dashboards start to diverge; some SPOs discover inconsistent tip hashes and slowed block manufacturing. | Preliminary containment is procedural: exchanges and infrastructure groups are instructed to look at for anomalies whereas engineers verify that the mainnet behaviour matches the Preview testnet bug. |
| Nov 21, 2025 – minutes after T0 | Formal detection and public flag | Intersect and IOG classify the scenario as a “momentary chain partition” between a poisoned and wholesome chain. Groups throughout Intersect, IOG, Cardano Basis, EMURGO, and main SPOs be a part of a coordinated incident bridge. | Inside alerts fan out to SPO channels; Intersect notes that groups have been “alerted inside minutes.” Shortly after, the “Mainnet Incident Replace” put up is printed on X to warn the broader ecosystem {that a} malformed transaction has triggered a partition. | Exchanges are pausing ADA deposits and withdrawals as a precaution; SPOs are suggested to not blindly improve and to await patched binaries that can converge on the wholesome chain. |
| Nov 21, 2025 – late morning to afternoon | Hotfix launch and improve marketing campaign | Core builders verify the foundation trigger as a legacy hash-deserialization bug current in particular latest node variations and absent in older ones. | With the trigger understood, the chance of repeated malformed transactions is assessed and shared with SPOs, CEXs, and infra suppliers in coordination channels. | Patched variations 10.5.2 and 10.5.3 of the node are launched with the deserialization bug mounted. SPOs, relays, and exchanges are instructed to improve in order that their stake weight strikes to the wholesome chain; a CIP-135 disaster-recovery plan is ready as a fallback if upgrades lag. |
| Nov 21, 2025 – by ~22:17 | Community reconverges | As upgraded nodes reject the poisoned department and comply with the wholesome chain, Ouroboros consensus density shifts decisively towards the wholesome ledger. The poisoned chain continues solely on a shrinking minority of un-upgraded nodes. | Monitoring exhibits that block manufacturing and tip hashes are once more constant throughout main swimming pools, explorers, and exchanges. Intersect confirms that Cardano “by no means went offline,” solely slowed through the partition. | Intersect stories that every one nodes voluntarily joined the primary chain at about 22:17 UTC and that the community converged again to a single wholesome chain inside roughly 14.5 hours of the malformed transaction. A reconciliation working group has been set as much as deal with any transactions that existed solely on the poisoned department. |
| Nov 22–23, 2025 | Submit-incident mitigation and disclosure | Attacker “Homer J” publicly admits to crafting the malformed transaction utilizing AI-generated directions; FBI and different companies are notified. Full “information at a look” report and ongoing after-action overview are printed by Intersect. | Neighborhood and media obtain a exact reconstruction of the occasion; myths a few “protocol hack” or a “complete outage” are explicitly debunked. | Lengthy-term fixes are scoped to expanded take a look at protection for legacy code, accelerated improve cycles, stronger monitoring, and a renewed emphasis on accountable disclosure and bug bounties moderately than mainnet experimentation. |
Ethereum’s multi-client insurance coverage coverage
Ethereum treats consumer variety as a first-order resilience property. For the reason that Merge, Ethereum has run separate execution and consensus layers, every supported by a number of unbiased implementations.
On the execution aspect, Geth, Nethermind, Erigon, and others course of transactions and compute…
