Release Notes - v0.46.2
v0.46.2 (May 15, 2026)
Section titled “v0.46.2 (May 15, 2026)”Title: Safer Mithril restore boundaries, rollback recovery, and peer stability
Date: May 15, 2026
Version: v0.46.2
Hi folks! Here’s what we shipped in v0.46.2.
✨ What’s New
Section titled “✨ What’s New”- Noted no new end user features: This patch release focuses on fixes and day to day operational improvements.
💪 Improvements
Section titled “💪 Improvements”- Improved dependency freshness for supporting services: Dingo updated Plutigo from v0.1.11 to v0.1.13, which keeps connected tooling current.PR #2327
- Streamlined default validation runs for routine checks: Default validation now skips the vanRossem scenario unless an explicit
-runselection includes it, which keeps routine checks more focused.PR #2325 - Refined network compatibility upkeep: Dingo updated Gouroboros from v0.170.0 to v0.170.1, which keeps network handling aligned with current dependencies.PR #2321
- Modernized release validation coverage: CI linting migrated from
gomodguardtogomodguard_v2, which keeps release checks current.PR #2320 - Documented the previous patch release in source: The repository now includes release notes for v0.46.1 in source, which keeps release history easier to review.PR #2314
🔧 Fixes
Section titled “🔧 Fixes”- Hardened restore safety at trusted boundaries: Dingo now rejects rollbacks below the trusted snapshot boundary, bypasses covered header only checks when the snapshot already includes them, and replays later stored blocks to rebuild transaction metadata after restore.PR #2326
- Stabilized peer handling during divergence: Dingo now temporarily denies peers that follow a conflicting sync path, closes denied inbound peers immediately, and applies deny list checks consistently across connection flows.PR #2324
- Recorded forge activity earlier in block handling: Dingo now records forged block counters, latency metrics, and forged block events as soon as it builds a block, even when later adoption fails.PR #2323
- Reconciled live rollback recovery after deep divergence: Over-K live rollback and fork recovery now reconcile ledger and primary-chain divergence to a common ancestor and resume syncing.PR #2322
- Corrected peer timing and timeout handling: Outbound peer backoff and
ConnectedAttracking now behave correctly, negative timing glitches clamp safely, and configurable chainsync block timeouts apply without mutating shared protocol globals.PR #2316 - Safeguarded repeated database shutdown paths: Database shutdown now handles repeated close paths safely so resource cleanup no longer double closes handles or triggers a panic.PR #2315
📋 What You Need to Know
Section titled “📋 What You Need to Know”- Clarified safer restore recovery after snapshot use: Snapshot restore now enforces trusted boundaries more carefully and rebuilds the data needed for safer replay and rollback handling after restore.
- Strengthened peer stability through difficult sync conditions: Dingo now recovers more reliably from rollback divergence, handles unstable peers more decisively, and keeps sync progress steadier on sparse networks.
- Sharpened operational visibility and release upkeep: Forge activity now reports more accurately, while dependency updates, validation coverage, CI checks, and release documentation stay current in this patch release.
Recommended Network Compatibility ⚠️
Section titled “Recommended Network Compatibility ⚠️”| Network | Compatible |
|---|---|
| mainnet | ⛔ |
| preprod-testnet | ⛔ |
| preview-testnet | ✅ |
🙏 Thank You
Section titled “🙏 Thank You”Thank you for trying!