Skip to content

Midnight Indexer 4.3.3-rc.4

Pre-release
Pre-release

Choose a tag to compare

@cosmir17 cosmir17 released this 01 Jun 15:04
v4.3.3-rc.4
2ddbd90

Midnight Indexer 4.3.3-rc.4 Release Notes

Release date: 2026-06-01

Release type: Pre-release (development line)

Git tag: v4.3.3-rc.4

Tree hash: 18fa059cf3bb1df49b7d49c20f0af4193c399cb4

Environment: All public networks (mainnet, preprod, preview, devnet, qanet)

Note: this release candidate pairs with node 1.0.0 and ledger 8.1.0 and is the fast-follow patch on the Midnight 1.1 indexer line. Refer to MNF advisories for current deployment recommendations.

Summary

Release candidate on top of 4.3.3-rc.3. Adds a lazy transaction reference field to the dust and shielded nullifier transaction subscriptions (#1208), so consumers can navigate from a nullifier match to the full transaction without a separate lookup query. The field is @ beta. This is the only change since rc.3.

Dependencies

No dependency changes in this release candidate; the only change since rc.3 is #1208. Node 1.0.0 and ledger 8.1.0 are the paired versions carried by the 4.3.3 line (set in rc.3 and rc.2 respectively).

Docker Images

  • midnightntwrk/chain-indexer:4.3.3-rc.4
  • midnightntwrk/indexer-api:4.3.3-rc.4
  • midnightntwrk/wallet-indexer:4.3.3-rc.4
  • midnightntwrk/indexer-standalone:4.3.3-rc.4
  • midnightntwrk/spo-indexer:4.3.3-rc.4

Audience

  • Operators running an indexer on public networks (paired with node 1.0.0).
  • Testnet and devnet administrators.
  • DApp and wallet developers integrating against the indexer GraphQL API, in particular consumers of the dustNullifierTransactions and shieldedNullifierTransactions subscriptions.
  • QA and release managers.

What Changed

Change Type PR
Add transaction reference to nullifier event types New feature (@ beta) #1208

New Features

Transaction reference on nullifier event types (#1208)

Adds a transaction: Transaction! field (@beta) to DustNullifierTransaction and ShieldedNullifierTransaction. It is resolved lazily via the existing transaction DataLoader, so it is fetched only when the field is selected, with no payload cost for consumers that don't request it. This lets wallet sync pull the full transaction inline from a nullifier match instead of gathering hashes and querying separately. Both source tables (dust_nullifiers, zswap_nullifiers) have transaction_id NOT NULL, so the field is non-null. transactionId and transactionHash are retained as the resumption cursor and sequencing key.

Breaking Changes or Required Actions

None for stable API consumers. The transaction field added in #1208 is additive and @beta (no stability guarantee), so existing queries are unaffected.

Links and References

(Per-PR links are embedded in the What Changed and Breaking Changes sections above.)