Skip to content

Release Notes - v0.81.2

Title: Improve snapshot integrity, synchronization, and storage reliability

Version: v0.81.2

Release: v0.81.2

Dingo v0.81.2 strengthens snapshot validation, storage reliability, and peer synchronization while adding more responsive block fetch recovery and an opt in block fetch threshold.

NetworkCompatible
mainnet⛔
preprod-testnet✅
preview-testnet✅
musashi✅
  • Verified reward stake snapshot provenance while holding the migration lock. Dingo now stops startup before schema migrations, backfills, or other database and journal changes when it cannot verify provenance. Only version 2 snapshots with validated genesis, era, and protocol parameters, no Leios context, and consistent genesis selection across database open paths can reach calculation version 3.
  • Optimized SQLite committee authorization cleanup during Mithril backfills by limiting each batch to superseded IDs and deleting rows through their integer primary keys, avoiding full table scans caused by stale statistics.
  • Improved failure visibility by surfacing storage, iterator, timestamp, and decoding errors instead of masking them. Restore, truncate, and shutdown operations now limit subscription draining; topology accepts hotValency as a valency alias with valency taking precedence and validates warmValency; bootstrap recovery uses bounded snapshot preferred attempts; and SQLite cancellation behavior includes the required fix.
  • Resynchronized ChainSync connections when they fell behind or moved ahead of the tip, admitted disconnected headers, and recovered stale cursors even when no best peer was available.
  • Launched block fetch for queued headers while forecast horizon waits delayed progress, and resynchronized when dispatch failed.
  • Accepted the first epoch 0 peer relative Byron EBB at chain origin when Dingo anchored it to the configured genesis hash.
  • Enabled the opt in BlockfetchLowWatermarkEnabled setting through blockfetchLowWatermarkEnabled in YAML, --blockfetch-low-watermark-enabled on the CLI, and DINGO_BLOCKFETCH_LOW_WATERMARK_ENABLED in the environment. The setting defaults to false; when enabled, Dingo starts far from tip block fetch after one queued batch range instead of waiting for the larger queue threshold.

Doc Holiday logo

Docs authored by Doc Holiday

Edit page

Last updated: