Cardano Blockchain Disruption Marks First Chain Split in Network History

The Cardano ecosystem witnessed one of its most disruptive events to date on Friday after a malfunctioning transaction caused the blockchain to fracture into two separate chains — a scenario that has never occurred in the network’s eight years of operation.

The incident triggered widespread uncertainty across exchanges, infrastructure providers, and developers, forcing emergency coordination within the ecosystem. While block production continued uninterrupted, ledger states diverged, leaving the blockchain running along two competing histories until consensus eventually reconverged.

The situation has now escalated into a legal matter, with Cardano founder Charles Hoskinson confirming that the matter has been referred to the FBI after indications that the transaction was crafted intentionally rather than by accident.

How the Chain Split Happened

According to Intersect, the ecosystem governance body for Cardano, the disruption began when a malformed or “toxic” delegation transaction entered the network. The bug was rooted in a version mismatch within Cardano node software:

Node versionResponse to toxic transaction10.5.2 and laterAccepted as valid10.3.1 and earlierRejected

The discrepancy created two active chains:

• One containing the transaction

• One rejecting it

Because both versions continued to produce blocks independently, the network split instead of halting — a rare occurrence in blockchain architecture and one that resulted in duplicated history and inconsistent state across wallets, dApps, explorers, and exchanges.

Developers issued software patches within hours, and the network converged naturally after most node operators upgraded. However, the temporary split was enough to rattle ecosystem participants across the globe.

Exchanges Freeze ADA Activity as Data Turns Unreliable

Some of the largest exchanges moved quickly to protect user funds. Coinbase paused ADA deposits and withdrawals for roughly 14 hours while monitoring which chain would ultimately dominate. Upbit, Kraken, and several mid-tier exchanges took similar precautions.

During the disruption:

• DeFi platforms saw settlement delays

• Some smart contracts executed on one chain but not the other

• Block explorers displayed conflicting information

Under normal conditions, Cardano transactions are finalized within seconds. On Friday, settlement times stretched to minutes, and many transfers failed altogether.

ADA’s price fell sharply during the turbulence, dropping roughly 16% at its lowest point before stabilizing above $0.40.

Developer Takes Responsibility, Calls Incident an Experiment Gone Wrong

A staking pool operator known as Homer J (AAA) claimed responsibility shortly after the disruption began. In a public apology on X, he described the event as a misguided experiment rather than a coordinated attack.

He posted that he attempted to reproduce the malformed transaction using code generated by an AI assistant and said he failed to realize that the transaction could propagate across mainnet. He also attempted to firewall his server based on the AI’s instructions — something he now admits he did not validate properly.

“It started as a personal challenge,” he wrote. “I’m ashamed of my carelessness and take full responsibility.”

Despite the statement, his intentions are now under scrutiny.

Hoskinson Rejects the Apology and Calls It a Deliberate Attack

Cardano founder Charles Hoskinson issued a direct response that sharply contradicted the developer’s explanation. In a widely shared post, he asserted the transaction was not an accident but a targeted effort to damage the Cardano brand and disrupt confidence in the ecosystem.

Hoskinson referenced evidence that the same malformed transaction was submitted on Cardano’s Preview test network approximately 24 hours before the mainnet incident — a sign, he claimed, of premeditation rather than experimentation.

He confirmed that the incident has now been referred to the FBI and that authorities are preparing to investigate potential malicious intent. The move has drawn mixed reactions within the Cardano community, with some praising the firm stance on protocol security and others expressing concern about the precedent it could set for developer liability.

Internal Fallout: IOG Engineer Resigns Over Legal Fears

The situation has already triggered internal consequences within Cardano’s development ecosystem. Roman — a widely respected Plutus engineer known as effectfully — resigned shortly after Hoskinson acknowledged the FBI’s involvement.

In his resignation note, he expressed concern that typical developer activity, including security exercises and stress testing, could now expose team members to legal risk. He stated that he has participated in network security simulations before and now fears that honest research could be misinterpreted as hostile behavior.

The departure has opened a broader conversation in the Cardano community about how to balance protocol safety with an environment that does not discourage engineers from identifying vulnerabilities.

What Comes Next for Cardano

The chain has fully reconverged and network activity has normalized. Exchanges have resumed ADA deposits and withdrawals, and ecosystem services are back online.

However, deeper questions now loom:

• How did a three-year-old bug persist undiscovered?

• Should node version diversity be reduced to prevent future splits?

• Will legal escalation discourage independent testing?

• Could the event affect institutional sentiment toward Cardano?

The incident has become both a technical and cultural milestone for the blockchain — not because service was permanently disrupted, but because it exposed friction between decentralized research culture and centralized public-company leadership.

Going forward, the Cardano community is now in a position where maintaining rapid innovation must coexist with the responsibility of safeguarding a multibillion-dollar network.