Chain-facing capabilities have not been reviewed.
Next: Review production entry points and integration behavior.
Martin Lang (gitmachtl) · Ecosystem unresolved
Dijkstra readiness: gap (see below). Dependency evidence does not establish compatibility.
Breaks after HF
Exposure service · inherited readiness gap · scanned at b84a552d2b
confirmed· own codeera-identity
The era read from the node (dijkstra after the fork) selects the min-UTxO calculation by name; only babbage and conway get the map-based output encoding, so a Dijkstra-era output is sized with the pre-Babbage array format and the computed minimum is wrong.
"online") local tmpEra=$(${cardanocli} latest query tip ${magicparam}nodeEraParam="--${tmpEra}-era";*"babbage"* | *"conway"* ) #Build the tx-out cbor in babbage-tx format with maps* ) #Build the tx-out cbor in alonzo/shelley format with arrayconfirmed· own codeprotocol-parameters
Vote tallies assign each changed parameter to a governance group by name; the 23 Dijkstra parameters match no group, so a proposal changing only those leaves the threshold at zero and the script exits with an error.
*"poolPledgeInfluence"*|*"poolRetireMaxEpoch"*|*"stakePoolTargetNum"*|*"costModels"*|*"collateralPercentage"*)if [[ "${dRepPowerThreshold}" == "0" || "${dRepPowerThreshold}" == "" ]]; then echo -e "\e[35mERROR - Something went wrong finding the dRepPowerThreshold.not-reached· koiosera-identityprotocol-parameters
Light mode reads the tip, UTxOs, pools and governance from Koios, but protocol parameters from a separate hosted JSON file and the era from configuration.
#queryLight_protocolParameters functionnot-reached· own codecardano-clistake-pool-registration
cardano-cli is called with the era the node reports (cardano-cli 11.3 has a dijkstra group), and pool certificates are built by cardano-cli.
cliEra="${tmpEra,,}" #new era selection parameter for cardano cli 8.12.0+PoolRegistration|PoolReRegistration|PoolRetirement )partial
unresolved
unresolved
unresolved
No native profile has been collected. Dependency coverage is unresolved, not empty.
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.
Next: Review production entry points and integration behavior.
Next: Export a discovery review packet.
Next: Collect a native resolution for a declared release/profile.
Next: Review the pinned repository and identify its distribution/build process.
Next: Confirm distribution artifacts and production configuration with release evidence.
No recognized manifests have been discovered.
evidence:1760a58e5c678ec8eac63e281146716c8ba6f043cb740a57105db43270efe66cRetained at data/readiness/evidence/1760a58e5c678ec8eac63e281146716c8ba6f043cb740a57105db43270efe66c.json.gzevidence:84140a30dd4dab0839f31109dad950407bff52519f535d192268f8931c652818Retained at data/readiness/evidence/84140a30dd4dab0839f31109dad950407bff52519f535d192268f8931c652818.json.gz