Release Notes - v0.81.2
v0.81.2
Section titled “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.
Recommended Network Compatibility ⚠️
Section titled “Recommended Network Compatibility ⚠️”| Network | Compatible |
|---|---|
| mainnet | ⛔ |
| preprod-testnet | ✅ |
| preview-testnet | ✅ |
| musashi | ✅ |
Snapshot integrity and storage
Section titled “Snapshot integrity and storage”- 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.
Storage, topology, and recovery
Section titled “Storage, topology, and recovery”- 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
hotValencyas avalencyalias withvalencytaking precedence and validateswarmValency; bootstrap recovery uses bounded snapshot preferred attempts; and SQLite cancellation behavior includes the required fix.
Peer synchronization and block fetch
Section titled “Peer synchronization and block fetch”- 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
BlockfetchLowWatermarkEnabledsetting throughblockfetchLowWatermarkEnabledin YAML,--blockfetch-low-watermark-enabledon the CLI, andDINGO_BLOCKFETCH_LOW_WATERMARK_ENABLEDin the environment. The setting defaults tofalse; when enabled, Dingo starts far from tip block fetch after one queued batch range instead of waiting for the larger queue threshold.
Docs authored by Doc Holiday