DevX Initiative
In review: This tooling data is still being verified and may change.

Obsidian Systems · cabal / nix

Hydra Pay

Dijkstra readiness: upstream (see below). Dependency evidence does not establish compatibility.

Dijkstra hardfork

All tools →

DismissedAbandoned; no activity since 2023-09. (2026-10-26)

Otherwise: Not verified

Exposure dependency · inherited readiness upstream · scanned at 620e58e364

Changed surfaces touched by shipped code (9)
  • block-encodingunassessed · via marker:raw-cbor-codec
  • cardano-api-haskellupstream · via dependency:cardano-api
  • cardano-cliupstream · via service:cardano-cli
  • era-identityupstream · via dependency:cardano-api, dependency:cardano-ledger
  • node-configurationunassessed · via marker:genesis-config
  • node-to-client-protocolupstream · via service:node-socket
  • protocol-parametersupstream · via dependency:cardano-ledger, marker:cost-models-or-parameters
  • transaction-encodingupstream · via dependency:cardano-api, dependency:cardano-ledger, marker:raw-cbor-codec
  • transaction-rulesupstream · via dependency:cardano-ledger

Lead decisions

  • undetermined· own codenode-configuration

    Ships mainnet, preprod and preview node configurations without a DijkstraGenesisFile; the target node reads that file only behind ExperimentalHardForksEnabled, so whether a 11.2 node started from these files follows the fork depends on the tagged release.

  • not-reached· own codeblock-encodingprotocol-parameterstransaction-encoding

    The Hydra head runs on its own protocol-parameters file, and the CBOR lines are Nix package overrides.

Inspect source release

Artifact mapping

partial

Native resolution

unresolved

Integration review

unresolved

Capability review

unresolved

Discovered source release
v1.1.2
Source repository
obsidiansystems/hydra-pay
Last successful discovery
2026-10-17T16:53:02.836Z
Last attempt
2026-10-17T16:53:00.738Z

Dependency profiles

No native profile has been collected. Dependency coverage is unresolved, not empty.

Chain-facing capabilities

Findings describe behavior in a specific release and configuration. Suggestions need verification; historical findings do not establish behavior in the current source. None establishes hardfork compatibility.

No capability findings have been returned. Behavior remains unresolved; an empty list does not mean this tool has no chain-facing capabilities.

Unresolved frontiers and next actions

capability

Chain-facing capabilities have not been reviewed.

Next: Review production entry points and integration behavior.

integration

Runtime, bundled, and service dependencies have not been reviewed.

Next: Export a discovery review packet.

resolution

No native dependency resolution has been imported.

Next: Collect a native resolution for a declared release/profile.

artifact

Source release identified; published package/binary correspondence and supported profiles need verification.

Next: Confirm distribution artifacts and production configuration with release evidence.

Discovered manifests (165)
Evidence index (2)