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.
NMKR · Ecosystem unresolved
NMKR Studio API
Dijkstra readiness: gap (see below). Dependency evidence does not establish compatibility.
Dijkstra hardfork
All tools →Breaks after HF
Move off maestro
Exposure dependency · inherited readiness gap · scanned at 5c8f0d1876
Changed surfaces touched by shipped code (8)
- block-encodinggap · via marker:raw-cbor-codec, cardano-db-sync
- era-identitygap · via cardanosharp, cardano-db-sync, koios, service:maestro
- node-to-client-protocolupstream · via cardano-db-sync, service:node-socket
- plutus-languagegap · via cardanosharp
- protocol-parametersgap · via cardanosharp, marker:cost-models-or-parameters, cardano-db-sync, koios, service:maestro
- stake-pool-registrationgap · via cardanosharp, cardano-db-sync
- transaction-encodinggap · via cardanosharp, marker:legacy-stake-certificate, marker:raw-cbor-codec, cardano-db-sync, koios, service:maestro
- transaction-rulesno-evidence · via cardanosharp
Blocked by
- upstream fixcardano-db-syncblock-encodingera-identityprotocol-parametersstake-pool-registrationtransaction-encoding
- upstream fixkoiosprotocol-parameters
- upstream fixmaestro (deprecated)era-identityprotocol-parameterstransaction-encoding
Waiting on
- cardanosharpno-evidence, no verdictera-identityprotocol-parametersstake-pool-registrationtransaction-rules
- koiosno-evidence, no verdicttransaction-encoding
Lead decisions
confirmed· cardano-db-syncblock-encodingera-identityprotocol-parametersstake-pool-registrationtransaction-encoding
The API and minting services query db-sync through an EF Core model that maps epoch_param, pool and transaction tables. db-sync cannot index Dijkstra blocks (R2 gap), so these queries return pre-fork data only.
- NMKR.Api/Startup.cs:57
GlobalFunctions.optionsBuilderDbSync.UseNpgsql(connectionStringDbSync); - NMKR.Shared/DbSyncModel/DbSyncContext.cs:412
entity.ToTable("epoch_param");
- NMKR.Api/Startup.cs:57
confirmed· koiosprotocol-parameters
Koios /epoch_params is a protocol-parameter source for minting transactions.
- NMKR.Shared/Functions/Koios/KoiosFunctions.cs:924
string url = (tip == null || tip.Epoch==null)? $"{GeneralConfigurationClass.KoiosApi}/epoch_params" : $"{GeneralConfigurationClass.KoiosApi}/epoch_params?_epoch_no={tip.Epoch}";
- NMKR.Shared/Functions/Koios/KoiosFunctions.cs:924
confirmed· maestro (deprecated)era-identityprotocol-parameterstransaction-encoding
The shared NMKR functions read UTxOs from Maestro and submit turbo transactions through it.
- NMKR.Shared/Functions/Meastro/MaestroFunctions.cs:18
GeneralConfigurationClass.MaestroConfiguration.ApiUrl}/addresses/{address}/utxos - NMKR.Shared/Functions/Meastro/MaestroFunctions.cs:113
private static async Task<SubmissionResultClass> SubmitTurboTransactionAsync(byte[] signedTx)
- NMKR.Shared/Functions/Meastro/MaestroFunctions.cs:18
not-reached· cardanosharpplutus-languagetransaction-encoding
Uses CardanoSharp for keys, addresses, coin selection and its own transactions; it decodes no chain transactions with it.
- NMKR.Shared/NMKR.Shared.csproj:34
<PackageReference Include="CardanoSharp.Wallet" Version="5.1.0" />
- NMKR.Shared/NMKR.Shared.csproj:34
not-reached· koiosera-identity
Era handling is hard-coded (a Babbage-era min-UTxO workaround), not read from Koios.
- NMKR.Shared/Functions/ConsoleCommands.cs:3161
// We are adding 0.25 ADA because of the error in Babbage era with minutxo
- NMKR.Shared/Functions/ConsoleCommands.cs:3161
Artifact mapping
partial
Native resolution
unresolved
Integration review
unresolved
Capability review
unresolved
- Discovered source release
- unreleased:main
- Source repository
- nftmakerio/NMKR-Studio
- Last successful discovery
- 2026-10-17T16:53:01.583Z
- Last attempt
- 2026-10-17T16:52:59.171Z
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.
No recognized manifests were found; source may use an unsupported build system.
Next: Review the pinned repository and identify its distribution/build process.
Discovered manifests (0)
No recognized manifests have been discovered.
Evidence index (2)
- Pinned repository tree for manifest and integration discovery
evidence:8775792ee460f10ccd47a81da8132912ee620376e37e14478fe7464adf1001d8Retained at data/readiness/evidence/8775792ee460f10ccd47a81da8132912ee620376e37e14478fe7464adf1001d8.json.gz - Release selection and immutable source identity
evidence:b827675332b2a79e831b0197938beddfebf46ddf071df0fdf4df9c1c3c453867Retained at data/readiness/evidence/b827675332b2a79e831b0197938beddfebf46ddf071df0fdf4df9c1c3c453867.json.gz