DevX Tracker Flags Dijkstra Compatibility Gaps Across 110 Cardano Tools

The Cardano DevX Initiative has published a public readiness tracker for the Dijkstra hard fork, classifying 110 tools as “Breaks after HF” in its November 1 assessment. The designation identifies a compatibility gap in a tool’s released code or its dependencies. Input Output highlighted the tracker in its latest weekly development report.

The map connects findings to source code, development issues, and test results, showing which components need changes and which other tools depend on them.

Dijkstra Assessment Covers 206 Cardano Tools

DevX reviewed a catalog of 268 tools and included 206 whose shipped code interacts with parts of the protocol affected by Dijkstra. Of the 62 excluded tools, 41 lacked public source code, 18 did not touch changed interfaces or structures, and three matched only through tests or examples.

The published assessment lists 110 tools as “Breaks after HF,” nine as “In progress,” four as “Ready for HF,” and four as “Target component.” Another 45 remain unverified, while 34 were set aside with documented reasons, including abandonment or limited use.

“Ready for HF” means a tool has released its own support and has no unresolved dependencies tracked by the assessment. “Not verified” means no compatibility gap has been confirmed, but the tool has not earned a passing result. DevX labels the data as under review and subject to change.

Upstream Dependencies Shape the Fix Order

The tracker models 19 upstream steps that could remove dependency barriers for 82 tools. Its proposed sequence prioritizes the additional tools each step would unlock after earlier dependencies have been addressed.

The first five steps involve cardano-db-sync, Blockfrost, Ogmios, Koios, and Kupo. Together, those changes would remove the tracked barriers for 45 of the 82 tools. Blockfrost and Koios depend on db-sync, while Kupo depends on Ogmios.

Some projects also require changes to their own code, so updating a dependency alone would not complete their migration. The map distinguishes those cases from tools waiting entirely on upstream support. Its classifications describe the revisions examined; subsequent releases need to be assessed against that snapshot.

[NEWSBREAK]

Devnet Results Guide Maintainer Follow-Up

After cardano-node 11.2.0 was tagged, DevX reran the assessment against the prerelease. All 39 runtime results that could be compared at identical component versions matched the earlier assessment.

The update moved cardano-c and Plutarch to ready status following their Dijkstra support releases. Adder moved to in progress, while the node, CLI, submit API, and cardano-testnet were classified as target components because they form part of the reference release itself.

Cardano-node 11.2.0 remains a prerelease whose release notes do not yet recommend mainnet use. Testing against it does not constitute activation of the Dijkstra era.

DevX’s announced next step is to send diagnostic packages to maintainers of components with confirmed devnet failures, including Ogmios, Kupo, db-sync, Pallas, CML, and gOuroboros. Each package is intended to document the failure, provide reproduction steps, and identify the tools blocked by it.