TLDR:
- Cardano partition stemmed from a malformed transaction that split node versions during routine operations.
- Older node versions kept the chain active while newer versions struggled and caused temporary front-end issues.
- Hoskinson linked the incident to a targeted attack tied to activity in the Fake Fred Discord group.
- CryptoRus stated the chain stayed operational, framing the event as a fork caused by a node software bug.
The Cardano network faced an unexpected mainnet partition that triggered widespread concern across the ecosystem. The issue surfaced after a malformed delegation transaction caused newer node versions to desynchronize.
Older versions continued running, which kept block production online but at a slower pace. Stake pool operators began rapid upgrades as the incident gained attention across social platforms.
Cardano Partition Incident Explained
Charles Hoskinson stated that the disruption started when certain node versions failed to process the malformed transaction.
According to Hoskinson, this triggered parallel chain behavior that created confusion about the network’s state. He said the chain kept running the entire time, though block production slowed and some interfaces struggled to display accurate data. The Cardano Foundation and Input Output later confirmed that upgrades to version 10.5.3 stabilized operations.
The founder added that older node versions remained synchronized and continued validating blocks. This allowed the chain to stay operational despite front-end issues reported by users.
The upgrade rollout advanced throughout the day as operators worked to align versions. Hoskinson emphasized that funds remained safe and that the chain never halted.
Crypto commentator CryptoRus offered additional clarification on the event. He attributed the fork to a bug introduced in newer cardano-node releases rather than a full network outage.
His post noted that the blockchain stayed live as older node versions maintained continuity. He said the disruption created slower block production and temporary UI inconsistencies.
Hoskinson’s remarks sparked continued debate within the community. Some participants argued that broader context should be considered, referencing comments from SPOs who warned against internal division.
Others pointed to the active discussions in the Fake Fred Discord, where the individual tied to the incident was reportedly involved.
Targeted Attack Allegations Intensify Debate
Hoskinson later linked the malformed transaction to a premeditated attack. He said a disgruntled stake pool operator spent months in the Fake Fred Discord exploring ways to damage IOG’s reputation.
According to his account, the attacker targeted his personal pool, creating network-wide disruption. He said the individual attempted to distance himself after learning that a criminal investigation had begun.
Hoskinson described the impact as broad and immediate. He said every user experienced disruption due to the chain split. He added that DeFi applications faced interruptions and that repairing reputational damage would take time.
He said the involved operator apologized after seeing that earlier ITN references connected him to the event.