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

TxPipe · cargo

CShell

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

Dijkstra hardfork

All tools →

Not verifiedWaits on a verdict for utxorpc

Exposure dependency · inherited readiness gap · scanned at 37e9c61d75

Changed surfaces touched by shipped code (9)
  • block-encodinggap · via pallas, utxorpc, marker:raw-cbor-codec
  • consensus-participationin-progress · via pallas
  • era-identitygap · via pallas
  • node-to-client-protocolreleased · via pallas
  • plutus-languagein-progress · via pallas, marker:plutus-language-enum
  • protocol-parametersin-progress · via pallas
  • stake-pool-registrationin-progress · via pallas, marker:pool-registration
  • transaction-encodingin-progress · via pallas, utxorpc, marker:legacy-stake-certificate, marker:raw-cbor-codec
  • transaction-rulesin-progress · via pallas

Waiting on

  • utxorpcin-progress, no verdictblock-encodingtransaction-encoding

Lead decisions

  • not-reached· own codeblock-encodingplutus-languagestake-pool-registrationtransaction-encoding

    The explorer renders UTxO RPC protobuf messages, not chain CBOR; the wallet decodes only transactions it built through tx3 to sign them, and Conway-form transactions stay valid after the fork.

  • not-reached· pallasblock-encodingera-identityconsensus-participationplutus-languageprotocol-parametersstake-pool-registrationtransaction-encodingtransaction-rules

    The wallet uses Pallas for keys, addresses and hashing; chain data comes from its UTxO RPC provider. Transactions it signs come from tx3 in Conway form, which stays valid after the fork.

Inspect source release

Artifact mapping

partial

Native resolution

unresolved

Integration review

unresolved

Capability review

unresolved

Discovered source release
v0.15.0
Source repository
txpipe/cshell
Last successful discovery
2026-10-17T16:53:15.965Z
Last attempt
2026-10-17T16:53:14.283Z

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 (2)
Evidence index (2)