Source: ETHNews
Original Title: Cardano Faced Temporary Chain Split After Malformed Transaction Exposed Old Bug
Original Link: https://www.ethnews.com/cardano-faced-temporary-chain-split-after-malformed-transaction-exposed-old-bug/
The Cardano blockchain experienced a brief but notable disruption on November 21, 2025, after a malformed transaction triggered an old software bug and caused a temporary chain split. While the issue was resolved quickly, the event highlighted how legacy code paths can still surface unexpected behavior in major proof-of-stake networks.
How the Chain Split Happened
According to Intersect, Cardano’s ecosystem governance organization, the incident began when a delegation transaction containing malformed data was submitted to the network.
Although the transaction was valid at the protocol level, it exploited a dormant bug inside an underlying software library used by older node versions.
Nodes running outdated software rejected the transaction, while fully updated nodes accepted it. This divergence created two temporary versions of the blockchain:
A “healthy chain” processed by updated nodes
A “poisoned chain” formed by unpatched nodes
As a result, block production slowed and the network briefly operated in a partitioned state.
Issue Resolved Through Emergency Node Updates
To restore chain convergence, staking pool operators (SPOs) were instructed to upgrade immediately to node versions 10.5.2 or 10.5.3.
Once the majority of block-producing nodes updated, the network re-aligned and normal block production resumed.
Intersect emphasized that no user funds were lost, and final settlement integrity was preserved throughout the incident.
Perpetrator Admits to Submitting the Triggering Transaction
In an unusual twist, an X (formerly Twitter) user named Homer J., a known Cardano staking pool operator, publicly admitted to submitting the malformed transaction.
He described the act as careless experimentation, claiming he used AI-generated instructions without understanding the consequences. He insisted that it was not an attempt to harm the network.
However, Cardano co-founder Charles Hoskinson initially referred to the event as a premeditated attack, noting that the transaction appeared intentionally crafted to exploit the vulnerable code path.
Given the nature of the disruption, the matter has been escalated to law-enforcement agencies, including the FBI, which is now investigating the incident.
A Reminder About Node Diversity and Legacy Code
The chain split underscores a recurring challenge for decentralized networks: even when protocol rules are sound, node version fragmentation can magnify the impact of subtle bugs. Cardano core developers noted that the issue would not have materialized if the majority of the network had already migrated to the newer software versions.
Still, the coordinated response from SPOs and developers ensured that the event remained contained, with no lasting damage.
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
10 Likes
Reward
10
6
Repost
Share
Comment
0/400
LayoffMiner
· 11-24 05:28
Cardano has another issue, the old bugs haven't been fixed yet, how careless can this be?
View OriginalReply0
MondayYoloFridayCry
· 11-23 22:30
Another chain split? When will Cardano's problem be completely resolved...
View OriginalReply0
RamenDeFiSurvivor
· 11-23 12:50
When will this Cago issue finally be completely fixed? It's the same old bug again, and now we have to fork—it's ridiculous.
View OriginalReply0
WalletDivorcer
· 11-23 12:49
Cardano is having issues again? This bug has been hidden for way too long.
View OriginalReply0
GateUser-c799715c
· 11-23 12:47
Why did the old pit get dug up again? I shouldn't have touched it in the first place.
Cardano Faced Temporary Chain Split After Malformed Transaction Exposed Old Bug
Source: ETHNews Original Title: Cardano Faced Temporary Chain Split After Malformed Transaction Exposed Old Bug Original Link: https://www.ethnews.com/cardano-faced-temporary-chain-split-after-malformed-transaction-exposed-old-bug/ The Cardano blockchain experienced a brief but notable disruption on November 21, 2025, after a malformed transaction triggered an old software bug and caused a temporary chain split. While the issue was resolved quickly, the event highlighted how legacy code paths can still surface unexpected behavior in major proof-of-stake networks.
How the Chain Split Happened
According to Intersect, Cardano’s ecosystem governance organization, the incident began when a delegation transaction containing malformed data was submitted to the network.
Although the transaction was valid at the protocol level, it exploited a dormant bug inside an underlying software library used by older node versions.
Nodes running outdated software rejected the transaction, while fully updated nodes accepted it. This divergence created two temporary versions of the blockchain:
As a result, block production slowed and the network briefly operated in a partitioned state.
Issue Resolved Through Emergency Node Updates
To restore chain convergence, staking pool operators (SPOs) were instructed to upgrade immediately to node versions 10.5.2 or 10.5.3.
Once the majority of block-producing nodes updated, the network re-aligned and normal block production resumed.
Intersect emphasized that no user funds were lost, and final settlement integrity was preserved throughout the incident.
Perpetrator Admits to Submitting the Triggering Transaction
In an unusual twist, an X (formerly Twitter) user named Homer J., a known Cardano staking pool operator, publicly admitted to submitting the malformed transaction.
He described the act as careless experimentation, claiming he used AI-generated instructions without understanding the consequences. He insisted that it was not an attempt to harm the network.
However, Cardano co-founder Charles Hoskinson initially referred to the event as a premeditated attack, noting that the transaction appeared intentionally crafted to exploit the vulnerable code path.
Given the nature of the disruption, the matter has been escalated to law-enforcement agencies, including the FBI, which is now investigating the incident.
A Reminder About Node Diversity and Legacy Code
The chain split underscores a recurring challenge for decentralized networks: even when protocol rules are sound, node version fragmentation can magnify the impact of subtle bugs. Cardano core developers noted that the issue would not have materialized if the majority of the network had already migrated to the newer software versions.
Still, the coordinated response from SPOs and developers ensured that the event remained contained, with no lasting damage.