Release Notes - v0.90.3
v0.90.3
Section titled “v0.90.3”Title: Improve consensus correctness, API resilience, and operational safeguards
Version: v0.90.3
Release: v0.90.3
Comparison: v0.90.2…v0.90.3
Dingo v0.90.3 improves stake handling across era boundaries, bounds API and database work, strengthens peer and download safety, and refines Leios and operational behavior for node and library users.
Recommended Network Compatibility ⚠️
Section titled “Recommended Network Compatibility ⚠️”| Network | Compatible |
|---|---|
| mainnet | ⛔ |
| preprod-testnet | ✅ |
| preview-testnet | ✅ |
| musashi | ✅ |
Consensus and ledger
Section titled “Consensus and ledger”- Fixed epoch-boundary stake handling so same-rule era changes retain the existing SNAP-point stash. Dingo now reconstructs historical stake only when pointer-stake eligibility changes, including Babbage to Conway transitions, and applies one consistent pointer-stake rule.
- Passed the hard-fork-selected incoming era into boundary stake reads before the incoming epoch row exists, allowing Dingo to reuse corrected stake distributions.
- Improved local-extension header verification by retrying transient failures after ledger context changes within the existing bounded wait and parking headers when retries expire.
- Introduced certification-deadline handling for relayed Leios votes while keeping locally produced votes within the local vote window.
- Enabled caching and persistence of empty leader schedules for zero-stake epochs.
API, database, and performance
Section titled “API, database, and performance”- Expanded Leios key-epoch snapshot and retirement lookups with migration v51 composite indexes and bounded seek and UNION logic, preventing unbounded database work.
- Refined Blockfrost pool stake aggregation with bounded SQL aggregates and network-wide active-pool totals. Fallback handling covers unavailable aggregate data and overflow errors; shared admission allows four global and two per-client pool aggregate operations, returning HTTP 429 with
Retry-After: 1when capacity is full. - Bounded Blockfrost asset detail and listing work with shared admission, a 15-second deadline, cancellation propagation, and SQL aggregation. Requests return HTTP 429 or 503 with
Retry-Afterwhen capacity or service availability requires a retry, and requests exceeding 1,000,000 live UTxOs return HTTP 400. - Secured cloud mirror marker reads and publication by bounding marker size and rejecting unsafe or replaced paths.
Networking and configuration
Section titled “Networking and configuration”- Grouped eligible identity-less outbound peers by IPv4
/24, IPv6/64, or hostname for Genesis corroboration while preserving explicit control identities and excluding inbound or unknown peers. - Resumed Mithril downloads with a bounded full request when HTTP 416 provides no verifiable size, preserving the named cache until replacement succeeds.
- Rejected on-disk Badger compression with
blockCacheSize=0during initialization and documented the required configuration. - Defined
TxSubmissionLogicVersionhandling so absent values default to V1, V1 remains accepted, and V2 or unknown values fail during configuration loading. Dingo documents the implemented strategy as legacy per-peer inbound submission.
Validation and devnet
Section titled “Validation and devnet”- Updated devnet txpump image digests for era-tagged transaction IDs.
- Hardened Conway CBOR validation and reporting with refreshed conformance inputs. Linux Turbo now defaults to all programs through
TURBO_MAX_PROGRAMS=0, and the release validatescoverage.json.
Docs authored by Doc Holiday