Release Notes - v0.82.0
v0.82.0
Section titled “v0.82.0”Title: Improve protocol reliability, observability, and developer capabilities
Version: v0.82.0
Release: v0.82.0
Compared with v0.81.3, Dingo v0.82.0 strengthens protocol validation, synchronization, recovery, observability, cloud storage, governance, and developer workflows.
Recommended Network Compatibility ⚠️
Section titled “Recommended Network Compatibility ⚠️”| Network | Compatible |
|---|---|
| mainnet | ⛔ |
| preprod-testnet | ✅ |
| preview-testnet | ✅ |
| musashi | ✅ |
Protocol and synchronization
Section titled “Protocol and synchronization”- Improved ChainSync header verification by safely reusing cryptographic verification results bound to the header generation and point across ledger and block fetch admission.
- Streamlined documentation only changes by skipping expensive CI jobs while retaining documentation parity checks and safe fallback behavior when the change cannot be classified safely.
- Expanded synchronization resilience by retaining the full Genesis density window, observing idle peers through ChainSync
AwaitReply, improving block fetch retries and monitoring, adding peer identity cooldowns, and wiring tracing through the affected paths. - Clarified deterministic Conway governance proposal return failures so rewind and resynchronization recovery can handle them consistently.
- Secured token registry snapshots with signed Ed25519 manifests, HTTPS enforcement, exact size and digest checks, and an explicit rollback policy. Token registry configuration must provide authenticated snapshot metadata over HTTPS.
- Preserved imported operational certificate boundary counters and rejected conflicting counter values.
- Reduced committee pruning overhead by avoiding SQLite scans that rely on stale statistics.
- Applied era-aware
ParameterChangeand protocol parameter domain validation during live processing, replay, import, and Mithril gap handling. - Made container metrics binding explicit and added optional Bearer authentication for node and Mithril metrics. Container deployments must configure the metrics bind address explicitly.
- Cached governance vote SQL statements where the database supports statement caching.
Observability and recovery
Section titled “Observability and recovery”- Introduced OpenTelemetry tracing configuration, spans, sampling, and request context propagation across supported operations.
- Distinguished hashed slot zero blocks from origin blocks during intersection, recovery, and restart.
- Bounded Bark diagnostics with persistent snapshot catalogs, authenticated cloud manifests, pagination, and cancellation.
- Enabled Dijkstra Plutus V4 evaluation and exposed Dijkstra parameters through the APIs.
- Activated S3 and GCS cloud restore atomically with namespaced blobs and durable recovery after interruption.
- Propagated signal cancellation through Mithril synchronization and deferred indexes so interrupted work can resume safely.
Leios, governance, and developer workflows
Section titled “Leios, governance, and developer workflows”- Required complete, validated Leios endorser effects before adoption or commit and scoped votes to the corresponding announcement.
- Selected Dijkstra pool parameters at the correct SNAP boundary.
- Limited retries after failed mempool overlay rebuilds to prevent repeated immediate work.
- Exported funded devnet faucet credentials and preserved persistent devnet state across restarts.
Docs authored by Doc Holiday