Release Notes - v0.92.2
v0.92.2
Section titled “v0.92.2”Title: Improve performance, synchronization, and protocol reliability
Version: v0.92.2
Release: v0.92.2
Comparison: v0.92.1…v0.92.2
Dingo v0.92.2 improves database efficiency, rollback recovery, protocol validation, ledger processing, Leios content delivery, and operational reliability.
Recommended Network Compatibility ⚠️
Section titled “Recommended Network Compatibility ⚠️”| Network | Compatible |
|---|---|
| mainnet | ⛔ |
| preprod-testnet | ✅ |
| preview-testnet | ✅ |
| musashi | ✅ |
Database and storage
Section titled “Database and storage”- Improved SQLite fee queries by aggregating execution slot transaction fees with
dingo_coin_sum, preserving inclusive slot ranges, Leios selection, validation, overflow detection, and transaction visibility; PostgreSQL and MySQL continue streaming rows. - Added opt-in lazy preparation for hot SQL statements through
Config.LazyHotStatements. Test SQLite stores now prepare eligible statements on first write-pool use, memoize preparation failures, fall back to uncached execution, and refresh lazy caches after planner statistics; production leaves lazy preparation off and keeps eager preparation as the default.
Chain selection and recovery
Section titled “Chain selection and recovery”- Refreshed Praos schedules after rollback. The node preserves the current immutable epoch schedule, removes stale future schedules, rejects stale in-flight results through generation tracking, and recomputes current and next nonce-ready schedules.
- Bounded consumed-input recovery after restart to a configurable window with a default of 1000 blocks. The node still performs full recovery for identity-less legacy checkpoints, and recovery stops when periodic checkpoint persistence fails.
- Limited accepted header protocol versions to the highest major version that enabled eras support for live and historical peer processing. TrustedReplay and Mithril exemptions remain, and the node still rewinds processing after rejection.
- Preserved elected VRF keys in imported snapshots through the v55 migration and frozen key validation. Legacy snapshots without the stored key now fail closed instead of using the removed bootstrap fallback.
Ledger and protocol correctness
Section titled “Ledger and protocol correctness”- Corrected PV10 and later DRep deregistration to clear current targets from forward delegation state. PV9 retains its existing behavior, and the node leaves inactive accounts unchanged.
- Matched the Mithril STM lottery logarithm with
math.Log(1-phiF)and rejected the reported floating point boundary losing ticket. - Updated the
gouroborosdependency to tagged versionv0.218.2, bringing upstream validation and allocation changes into the node. - Applied ready historical Leios prefixes while the node fetches later closures. The node validates certificates first, handles cancellation safely, and preserves trusted and immutable boundaries.
- Skipped unchanged governance vote restoration during SQLite rollback with null-safe tuple and storage-class handling, non-correlated orphan detection, and deterministic Leios deadline coverage.
- Constrained incremental SQLite planner analysis with
PRAGMA optimize(0x10012), retaininganalysis_limitsampling, avoiding unbounded scans, and preserving planner statistics.
API, peer, and backfill behavior
Section titled “API, peer, and backfill behavior”- Reported expired UTxORPC history as Connect
FailedPreconditionacross UTxORPC methods, with the node reporting the oldest retained slot when known; the node maintains a cached history bound. - Rejected submitted transactions from the wrong era with typed mismatch errors. Historical block application still accepts predecessor-era transactions, and fee and size validation share canonical
TxSizeForFeebehavior. - Revised the Debian
bookworm-slimimage digest for Docker builds. - Reused frozen candidate nonce prefixes during peer fork-header verification before the era cutoff and safely fell back when a prefix was unavailable.
- Conditioned PostgreSQL bad-credentials tests on authentication enforcement. Trust-authenticated databases skip only those tests, while enforced authentication retains strict coverage.
- Accepted backfill blocks that share a Byron EBB slot only for the valid EBB to non-EBB pair. The node resolves checkpoint identity from persisted index, slot, and hash data and restores Mithril and API backfill resume.
Forging and network reliability
Section titled “Forging and network reliability”- Enforced slot-effective Dijkstra protocol capacity for endorser transaction and reference selection and manifest size. When capacity is unavailable or zero, forging skips EB production, continues ranking blocks, and records the skip reason.
- Stabilized Koios parity restart and universe-change tests by awaiting durable chunk checkpoints before returning poisoned responses.
- Expanded eligible SQLite UTxO overlay insert batches to 2047 after schema and parameter guards; the node falls back to the legacy width when the wider batch is unsafe or canceled.
- Removed spent intra-block outputs from the overlay before later transactions, preventing those outputs from being reused.
- Synchronized Leios announcements with content availability by deferring headers and offers until manifests and requested transactions are servable. Bounded waits and dependency tracking reduce unavailable-content connection failures.
- Reused deferred peer ancestry by caching unresolved bounded ancestry for retries and descendants until the primary chain reaches the reachable window.
Docs authored by Doc Holiday