Skip to main content
Version: v1

Midnight Indexer v4.3.0 release notes

For the complete documentation index, see llms.txt
  • Version: v4.3.0
  • Date: April 30, 2026
  • Paired node: 1.0.0 (0.22.x also supported)
  • Paired ledger: 8.1

High-level summary​

Midnight Indexer 4.3.0 is the indexer component of the Midnight 1.1 bundle, on the Node 1.0.0 and ledger 8.1 track. It brings the SPO indexer to the standalone SQLite deployment, lets the CLI print its version without a configuration file, and emits DustGenerationDtimeUpdate items in the dustGenerations subscription. Three bug fixes cover the in-memory pub/sub drain task, dust subscription input validation, and a redirect loop on unknown /api/v3 and /api/v4 paths. No GraphQL schema breaking changes.

Operators on Node 0.22.x should stay on the 4.0.x maintenance line.

Audience​

This release note is relevant for:

  • Operators running the Midnight Indexer against Node 1.0.0 or later, in particular standalone deployments that need SPO data
  • Wallet integrators consuming the dustGenerations subscription
  • Developers integrating against the Indexer API

What changed​

  • Added the SPO indexer to indexer-standalone (SQLite mode), a community contribution from hlolli (#979)
  • Made --version work without a configuration file (#1083)
  • Emitted DustGenerationDtimeUpdate items in the dustGenerations subscription (#1080)
  • Kept standalone in-memory pub/sub drain tasks alive across lag events (#1063)
  • Tightened dust subscription input validation (#1090)
  • Fixed an infinite redirect loop on unknown /api/v3 and /api/v4 paths (#1093)

New features​

SPO indexer in standalone SQLite mode​

indexer-standalone, the single-binary SQLite deployment, now bundles the SPO indexer alongside chain-indexer, indexer-api and wallet-indexer. Standalone operators can produce SPO data without the cloud-mode stack of a separate spo-indexer binary, PostgreSQL and NATS.

--version without configuration​

indexer --version and the per-binary CLIs print their version without a valid configuration file, which removes a failure mode in CI and container introspection.

DustGenerationDtimeUpdate in dustGenerations​

The dustGenerations subscription emits DustGenerationDtimeUpdate events alongside the existing dust generation events, so wallet integrators receive the dtime advance through the stream instead of polling.

Breaking changes​

None. Drop-in upgrade for operators already on the 4.x development line; the GraphQL schema is unchanged at v4.

Bug fixes​

  • Standalone-mode in-memory broadcast drain tasks could exit after a lag event and leave subscribers without further messages; they now survive lag (#1063)
  • The dust subscription accepted malformed input; validation is tightened (#1090)
  • Unknown sub-paths under /api/v3 and /api/v4 no longer redirect in a loop (#1093)