Cardano faced a temporary fork on its mainnet early Thursday morning after a bad block was propagated, echoing a similar issue observed on the testnet the previous day.
Despite the brief disruption, the blockchain remained operational, continuing to produce blocks without halting network activity. Operators running the affected node versions were quick to update to the recently released 10.5.2 version, while nodes on unaffected versions contributed to overall network stability.
Dave, a Cardano stake pool operator (SPO), highlighted that his pool, running version 10.1.4, maintained full block production during the incident. His pool, with 34 million ADA delegated, exemplifies the resilience built into Cardano’s architecture.
The protocol is designed to handle these types of forks, allowing the chain to converge back to a single canonical chain even when some nodes are temporarily disrupted.
Dave noted that the collaboration among SPOs and builders worldwide was remarkable, with rapid communication, problem-solving, and guidance helping maintain smooth operations.
Intersect, a Cardano ecosystem membership-based group, has revealed that the issue was discovered in the Preview environment prior to its activation on mainnet. The production of new blocks was temporarily affected as teams representing Cardano Foundation and Input Output HK collaborated on a technology plan.
Node operators with versions 10.3.1 or later were instructed to update as soon as possible to version 10.5.2, which can be acquired through the official GitHub site, while those with versions prior to 10.3.1 didn’t need any immediate action, and users of Daedalus were not affected by this incident.
The fast response demonstrates the effectiveness of Cardano’s decentralized approach, with nodes holding the unaffected versions continuing to produce blocks and thereby preventing larger issues within the network. The 10.5.2 patch corrects issues with the BadBlocks and ensures all nodes are synchronized with respect to the main chain.
The incident also highlighted the resilience of decentralized collaboration. Stake pool operators, developers, and community members from different time zones came together in real time to share advice and help fix GPS issues.
The reaction from the community again gave developers confidence that Cardano could carry on without negatively affecting users. Early signs indicate that block times are returning to normal, meaning the network is stabilizing after a short fork.
While these events are uncommon, they remind us of the need for appropriate upgrades and the importance of participation in the global Cardano community.
The design of the network and thriving ecosystem allows for a responsive work environment where developers and users can work together to establish the strength of decentralized blockchain protocols.
Also Read: Cardano (ADA) To Lose Top 20 Spot: Market Frenzy Begins

