Skip to main content

Midnight Indexer v4.3.7 release notes

For the complete documentation index, see llms.txt
  • Version: v4.3.7
  • Date: August 18, 2026
  • Paired node: 1.0.0
  • Paired ledger: 8.1.0

High-level summary

Midnight Indexer 4.3.7 is a maintenance patch for the Mainnet line. It takes v4.3.3-hotfix, the emergency build that Mainnet has been running, and adds one chain-indexer fix for the DUST validity window. The result resolves the OutOfDustValidityWindow and IntentTtlExpired case without regressing the runtime-upgrade enactment-block tolerance that the hotfix introduced.

There is no feature delta. The GraphQL schema is byte-for-byte identical to 4.3.3, and the release adds no migrations. This release pairs with Node 1.0.0 and Ledger 8.1.0, the same pairing as 4.3.3.

Version ordering does not imply supersession

4.3.7 is a deliberate branch off v4.3.3-hotfix, not a roll-up of everything tagged before it. The v4.3.4 and v4.3.5 tags and the unreleased 4.3.6 branch carry 4.4.0-preview content, including ledger v9, the c2m-bridge, and storage gc-v1. That work belongs to the 4.4.0 line and 4.3.7 excludes it. If you need the ledger v9 or node 2.0 line, track 4.4.0 instead of this release.

Upstream release status

Upstream has not completed QA sign-off for this release. GitHub marks the v4.3.7 tag as a pre-release and still lists 4.3.3 as its latest release. The five Docker images are published at tag 4.3.7, but treat this as a targeted maintenance patch for operators who need the DUST validity window fix, not as a routine upgrade. Check your own deployment gates before you roll it out.


Audience

This release note is relevant for:

  • Operators running the Midnight Indexer on the Mainnet line against Node 1.0.0 and Ledger 8.1.0
  • Operators already running the v4.3.3-hotfix emergency build
  • Wallet integrators who hit OutOfDustValidityWindow or IntentTtlExpired on the first transaction in a block

Operators on Node 0.22.x should track the 4.0.x maintenance line, not this release. Operators moving to the ledger v9 and node 2.0 line should track 4.4.0, not this release.


What changed

  • Fixed the DUST validity window so the first regular transaction of a block no longer fails with OutOfDustValidityWindow or IntentTtlExpired (#1367, #1371)
  • Consolidated the runtime-upgrade enactment-block tolerance in get_contract_state from v4.3.3-hotfix
  • No GraphQL schema change and no new migrations relative to 4.3.3

New features

No new features are introduced in v4.3.7. This is a maintenance release.


Breaking changes

No breaking changes are introduced in v4.3.7.


Bug fixes

The following bug fixes are included in this release.

DUST validity window on the first transaction of a block

The chain indexer now reproduces the node's mempool tblock bump off the parent block timestamp, and seeds that timestamp from the highest stored block on restart. Before this fix, the first regular transaction of a block could fail with OutOfDustValidityWindow or IntentTtlExpired because the indexer and the node disagreed on the block time used to evaluate the DUST validity window. (#1367, #1371)

Runtime-upgrade enactment block tolerance

get_contract_state tolerates a runtime-upgrade enactment block. This fix originated in v4.3.3-hotfix and is consolidated here, so upgrading from that hotfix does not lose it. If you upgrade from plain v4.3.3 rather than from the hotfix, you gain this tolerance as well.


Upgrade notes

Upgrading from v4.3.3-hotfix is drop-in. Bump the image tag and rolling-restart. There are no new migrations, no schema change, and no chain reset, because the release is v4.3.3-hotfix plus one chain-indexer fix.

Upgrading from plain v4.3.3 is also drop-in, and additionally gains the runtime-upgrade enactment-block tolerance.

Upgrading from the 4.0.x line still requires an indexer reset and a re-index from genesis. Budget approximately 3 to 4 days at Mainnet and Preprod scale.


Known issues

Upstream marks this tag as a pre-release pending QA sign-off. No functional issues specific to 4.3.7 are reported in the upstream release notes.