DevX Tracker Point Out Dijkstra Compatibility Gaps Across 110 Cardano Tools

The Cardano DevX Initiative don publish one public readiness tracker for the Dijkstra hard fork, wey classify 110 tools as “Breaks after HF” for im November 1 assessment. This designation mean say compatibility gap dey inside the tool released code or inside im dependencies. Input Output highlight the tracker for their latest weekly development report.

The map connect findings to source code, development issues, and test results, show which components need changes and which other tools depend on dem.

Dijkstra Assessment Cover 206 Cardano Tools

DevX review one catalog of 268 tools and include 206 wey their shipped code dey interact with parts of the protocol wey Dijkstra affect. From the 62 tools wey dem exclude, 41 no get public source code, 18 no touch changed interfaces or structures, and three just match only through tests or examples.

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

“Ready for HF” mean say one tool don release im own support and e no get unresolved dependencies wey the assessment dey track. “Not verified” mean say dem never confirm any compatibility gap, but the tool never still get passing result. DevX label the data as under review and e fit change.

Upstream Dependencies Shape the Fix Order

The tracker model 19 upstream steps wey fit remove dependency barriers for 82 tools. The proposed sequence prioritize the extra tools wey each step go unlock after dem don address earlier dependencies.

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

Some projects still need changes for their own code, so to update only dependency no go complete their migration. The map separate those cases from tools wey dey wait entirely on upstream support. The classifications describe the revisions wey dem examine; any later releases need to make dem assess am against that snapshot.

[NEWSBREAK]

Devnet Results Guide Maintainer Follow-Up

After cardano-node 11.2.0 get tagged, DevX run the assessment again against the prerelease. All 39 runtime results wey dem fit compare for identical component versions match the earlier assessment.

The update move cardano-c and Plutarch to ready status after their Dijkstra support releases. Adder move to in progress, while the node, CLI, submit API, and cardano-testnet dem classify as target components because dem be part of the reference release itself.

Cardano-node 11.2.0 still be prerelease wey the release notes never yet recommend for mainnet use. To test against am no be activation of the Dijkstra era.

The next step wey DevX announce na to send diagnostic packages to maintainers of components wey get confirmed devnet failures, including Ogmios, Kupo, db-sync, Pallas, CML, and gOuroboros. Each package go document the failure, provide reproduction steps, and identify the tools wey the failure dey block.