Chain-facing capabilities have not been reviewed.
Next: Review production entry points and integration behavior.
In review: This tooling data is still being verified and may change.
Masumi Network · container / npm
Masumi Registry Service
Dijkstra readiness: gap (see below). Dependency evidence does not establish compatibility.
Dijkstra hardfork
All tools →Not verifiedNo confirmed gap; not checked against Dijkstra
Exposure dependency · inherited readiness gap · scanned at 1374f327da
Changed surfaces touched by shipped code (7)
- block-encodinggap · via cardano-serialization-lib-csl
- era-identitygap · via meshjs-mesh-sdk, blockfrost, cardano-serialization-lib-csl
- plutus-languagegap · via meshjs-mesh-sdk, cardano-serialization-lib-csl
- protocol-parametersgap · via meshjs-mesh-sdk, blockfrost, cardano-serialization-lib-csl
- stake-pool-registrationgap · via meshjs-mesh-sdk, cardano-serialization-lib-csl
- transaction-encodinggap · via meshjs-mesh-sdk, blockfrost, cardano-serialization-lib-csl
- transaction-rulesno-evidence · via meshjs-mesh-sdk, cardano-serialization-lib-csl
Lead decisions
not-reached· blockfrostera-identityprotocol-parameterstransaction-encoding
The registry reads assets and transaction UTxOs from Blockfrost; no parameters or eras.
- src/services/cardano-registry/cardano-registry.service.ts:399
const txsUtxos = await blockfrost.txsUtxos(tx.tx_hash);
- src/services/cardano-registry/cardano-registry.service.ts:399
not-reached· cardano-serialization-lib-cslplutus-languageblock-encodingera-identityprotocol-parametersstake-pool-registrationtransaction-encodingtransaction-rules
CSL comes in through @blockfrost/blockfrost-js, which uses it for address derivation helpers.
- pnpm-lock.yaml:419
'@blockfrost/blockfrost-js@6.1.1':
- pnpm-lock.yaml:419
not-reached· meshjs-mesh-sdkplutus-languageprotocol-parametersstake-pool-registrationtransaction-encodingera-identitytransaction-rules
Builds and submits its own Conway-shaped transactions; nothing Dijkstra-only is decoded.
- package.json:50
"@meshsdk/core": "1.9.0",
- package.json:50
Artifact mapping
partial
Native resolution
unresolved
Integration review
unresolved
Capability review
unresolved
- Discovered source release
- unreleased:main
- Source repository
- masumi-network/masumi-registry-service
- Last successful discovery
- 2026-10-17T16:52:51.535Z
- Last attempt
- 2026-10-17T16:52:49.626Z
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
Runtime, bundled, and service dependencies have not been reviewed.
Next: Export a discovery review packet.
No GitHub stable release was found; default-branch source is discovery evidence only.
Next: Confirm distribution artifacts and production configuration with release evidence.
No native dependency resolution has been imported.
Next: Collect a native resolution for a declared release/profile.
Discovered manifests (3)
Evidence index (2)
- Release selection and immutable source identity
evidence:90291e167785ddcbef75f346fe0384bbf1ee36a6744fce34a53035e22ec53ed9Retained at data/readiness/evidence/90291e167785ddcbef75f346fe0384bbf1ee36a6744fce34a53035e22ec53ed9.json.gz - Pinned repository tree for manifest and integration discovery
evidence:b887f0c577f7817b91e5de9d9bd4456cecda6d2da7476d923acd56e882770386Retained at data/readiness/evidence/b887f0c577f7817b91e5de9d9bd4456cecda6d2da7476d923acd56e882770386.json.gz