Skip to content

Get Ogmios ready for the Dijkstra hard fork #21

Open

Description

@rober-m

Hi team! Thank you for all your work to get this tool ready for the HF! Although you already made a lot of progress, I ran a few tests on a devnet with cardano-node 11.2.0, and found several things to work on before it's ready:

  • Serialise Dijkstra transactions in full — Dijkstra transaction serialisation support #22
  • Support queryLedgerState/protocolParameters in Dijkstra
  • Return an error instead of dropping the connection on rejected Dijkstra submissions and in mempool monitoring
  • Accept the node configuration layout written by cardano-node 11.2.0
  • Merge the Dijkstra work into CardanoSolutions/ogmios and release it

Testing scenario

Tested on 2026-11-10: this fork's master (2f9b5d14, nix build .#ogmios, nightly (2f9b5d14)) against cardano-node 11.2.0, on a cardano-testnet devnet (magic 42) that hard-forked from Conway to Dijkstra. The chain has 15 Conway and 2,356 Dijkstra blocks, with test transactions built in both eras: payments, metadata, stake registration, a direct deposit, a PlutusV4 reference script, and a sub-transaction. Plutus script evaluation was not tested beyond an empty evaluateTransaction.

What already works: chain sync reaches the tip with no decode errors (Ogmios v7.0.0 stops at the first Dijkstra block on node 11.2.0 with expected list len or indef). Submitting a Dijkstra payment works and returns the same id as cardano-cli. eraSummaries, epoch, tip, and genesisConfiguration work.

To reproduce:
The devnet scripts are in scripts/readiness/devnet: its README builds the devnet and the test transactions, and forks.sh builds this fork and runs ogmios-probe/probe.mjs against it. Logs from the run: 2026-11-10-forks.

Serialise Dijkstra transactions in full

Every Dijkstra transaction comes back with only id and spends:

{"id":"11336636dfb1218b1103bc6f0fc43a176233a8093c2df96bce37d9d2402a3837","spends":"inputs"}

Inputs, outputs, fees, certificates, metadata, scripts, witnesses, and sub-transactions are missing. See the TODO(dijkstra): minimal body. Kupo's Ogmios path waits on this too (IntersectMBO/kupo#12).

Support protocol parameters in Dijkstra

{"jsonrpc":"2.0","method":"queryLedgerState/protocolParameters","id":1}

returns {"code":2002,"message":"Query unavailable in the current era."}. The Dijkstra arm returns Nothing until there is an encoder for DijkstraPParams (Query.hs#L1843-L1847). Transaction builders that read parameters from Ogmios can't build Dijkstra transactions.

Don't drop the connection on rejected submissions and in mempool monitoring

Submitting the same Dijkstra payment twice, so the node rejects the second, closes the WebSocket without a JSON-RPC reply. So does acquireMempool while the mempool holds a Dijkstra transaction. The server logs:

{"WebSocket":{"exception":"TODO(dijkstra): toRawTxIdHash Dijkstra arm (GenTxIdDijkstra)","tag":"WebSocketUnknownException"}}

from NodeToClient.hs#L277.

Accept the 11.2.0 configuration layout

cardano-testnet 11.2.0 writes the genesis file entries nested under Protocol, and the Dijkstra genesis under Testing. With that file Ogmios exits with:

Missing 'ByronGenesisFile' and/or 'ShelleyGenesisFile' from Cardano's configuration?

A copy with the same entries at the top level works. Not checked: which layout the public network configurations will use for Dijkstra.

Merge into CardanoSolutions/ogmios

None of this work can be consumed by downstream tooling until this is in CardanoSolutions/ogmios.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions