Chain-facing capabilities have not been reviewed.
Next: Review production entry points and integration behavior.
BloxBean (CF-backed) · container / gradle / npm
Dijkstra readiness: gap (see below). Dependency evidence does not establish compatibility.
In progress
Exposure implements · inherited readiness gap · boundary component, R2 status in-progress · scanned at 01b2aa85ef
confirmed· bloxbean-cardano-client-libraryera-identity
Era-dependent processing uses cardano-client-lib's Era enum, which ends at Conway.
if (event.getMetadata().getEra().getValue() < Era.Conway.getValue()) {confirmed· ogmiostransaction-encodingera-identity
When an Ogmios URL is configured, the submit component relays transactions through Ogmios.
this.ogmiosBackendService = new OgmiosBackendService(ogmiosUrl);confirmed· scalusplutus-script-contexttransaction-encoding
The submit component evaluates scripts with Scalus.
import scalus.bloxbean.ScalusTransactionEvaluator;not-reached· blockfrostera-identityprotocol-parameters
The Blockfrost extension serves a Blockfrost-compatible API from Yaci Store's own data.
not-reached· bloxbean-cardano-client-libraryplutus-languageprotocol-parametersstake-pool-registrationtransaction-encoding
Its other cardano-client-lib use is addresses, crypto, utilities and building its own transactions.
exclude group: "com.bloxbean.cardano", module: "cardano-client-core"not-reached· cardano-db-syncblock-encodingera-identityprotocol-parametersstake-pool-registrationtransaction-encoding
Yaci Store indexes the chain itself; db-sync names appear in analytics table metadata and export scripts.
not-reached· koiosera-identityprotocol-parameters
Koios is used only by a debugging script that cross-checks values.
Cross-check yaci-store's adapot (ada pot) values against Koios.not-reached· ogmiosblock-encodingplutus-languageprotocol-parameters
Yaci Store follows the chain with Yaci and evaluates with Scalus; Ogmios is only an optional submission relay.
@ConditionalOnProperty(name = "store.cardano.ogmios-url")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: Confirm distribution artifacts and production configuration with release evidence.
evidence:47d318b08d0dd4e4e19a06f5d9c78d1b706a8b77aaac632d4f14d2135f0d50f0Retained at data/readiness/evidence/47d318b08d0dd4e4e19a06f5d9c78d1b706a8b77aaac632d4f14d2135f0d50f0.json.gzevidence:4d8425bb95cb228ab05a7071c1a0156130c786f8fe9ba891682e8001b66a41beRetained at data/readiness/evidence/4d8425bb95cb228ab05a7071c1a0156130c786f8fe9ba891682e8001b66a41be.json.gz