@blinklabs/dingo 0.46.3 → 0.80.0

package/RELEASE_NOTES.md

@@ -1,2029 +0,0 @@
-# Dingo Releases
-
-## v0.46.2 (May 15, 2026)
-
-**Title:** Mithril trust-boundary protection, safer peer recovery, and sturdier rollback handling
-
-**Date:** May 15, 2026
-
-**Version:** v0.46.2
-
-Hi folks! Here’s what we shipped in v0.46.2.
-
-### ✨ What's New
-
-* Added **record forged-block signals before chain adoption completes:** Operators can now see forged-block metrics and events as soon as a block is built, which improves observability even when chain adoption later fails. ([#2323](https://github.com/blinklabs-io/dingo/pull/2323))
-* Introduced **tune chainsync block timeout and safer reconnect resets:** Operators can now configure the NtN chainsync block timeout, and peer reconnect handling now clears connection timing and outbound retry state only when the connection path truly requires it. ([#2316](https://github.com/blinklabs-io/dingo/pull/2316))
-
-### 💪 Improvements
-
-* Improved **refresh upstream compatibility with plutigo v0.1.13:** Deployments now stay aligned with the newer upstream support in `plutigo`, which keeps compatibility and routine maintenance steadier. ([#2327](https://github.com/blinklabs-io/dingo/pull/2327))
-* Refined **tighten default era-test coverage selection:** Default erastest runs now exclude vanRossem unless an explicit run filter is supplied, which keeps routine validation focused unless broader coverage is intentionally requested. ([#2325](https://github.com/blinklabs-io/dingo/pull/2325))
-* Enhanced **refresh protocol-library compatibility with gouroboros v0.170.1:** Protocol support now stays aligned with the newer upstream `gouroboros` release, which supports ongoing compatibility and maintenance work. ([#2321](https://github.com/blinklabs-io/dingo/pull/2321))
-* Updated **modernize dependency-policy checks in CI:** Continuous integration now uses the newer `gomodguard_v2` policy checks, which keeps dependency-policy maintenance current. ([#2320](https://github.com/blinklabs-io/dingo/pull/2320))
-
-### 🔧 Fixes
-
-* Fixed **enforce Mithril trust boundaries during rollback recovery:** Mithril-restored nodes now treat the trusted snapshot boundary as a hard recovery limit, skip header-only verification at or below that boundary, and rebuild post-restore transaction metadata safely after restore. ([#2326](https://github.com/blinklabs-io/dingo/pull/2326))
-* Corrected **deny divergent peers before they can loop recovery:** Nodes now temporarily deny-list divergent peers, close denied inbound peers, and enforce those denials across more connection paths, which reduces rollback loops and reconnect churn. ([#2324](https://github.com/blinklabs-io/dingo/pull/2324))
-* Strengthened **recover live rollback divergence from a safe shared ancestor:** Live rollback reconciliation can now bring the primary chain and ledger back to a safe common ancestor, which improves recovery from over-K rollback and fork-divergence scenarios. ([#2322](https://github.com/blinklabs-io/dingo/pull/2322))
-* Stabilized **close databases safely during repeated shutdown paths:** Repeated shutdown or cleanup calls no longer trigger duplicate-close failures because `Database.Close` now behaves safely when called more than once. ([#2315](https://github.com/blinklabs-io/dingo/pull/2315))
-
-### 📋 What You Need to Know
-
-* Clarified **trust the Mithril restore boundary during recovery:** Mithril-restored nodes now treat the trusted snapshot boundary as a hard rollback and replay limit, and they rebuild post-restore transaction metadata from restored block data after recovery completes.
-* Highlighted **safer divergent-peer recovery paths:** Nodes now temporarily deny bad peers during divergence recovery, and live rollback reconciliation can recover more safely by returning the primary chain and ledger to a shared safe ancestor.
-* Emphasized **stronger forging visibility and connection control:** Forged-block metrics and events now appear as soon as a block is built, and operators can tune the chainsync block timeout more directly.
-* Summarized **broader maintenance refreshes:** Dependency compatibility, validation defaults, dependency-policy checks, and database shutdown handling all received updates in this release.
-
-### Recommended Network Compatibility ⚠️
-
-| Network             | Compatible |
-|---------------------|------------|
-| mainnet             | ⛔         |
-| preprod-testnet     | ⛔         |
-| preview-testnet     | ✅         |
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.46.1 (May 14, 2026)
-
-**Title:** Conway genesis governance bootstrap, safer startup recovery, and networking fixes
-
-**Date:** May 14, 2026
-
-**Version:** v0.46.1
-
-Hi folks! Here’s what we shipped in v0.46.1.
-
-### ✨ What's New
-
-* Added **bootstrap Conway governance from genesis settings:** Networks that define initial governance delegates and voter registrations now start with that governance state already in place, which gives governance aware services a more complete view from the first block.
-
-### 💪 Improvements
-
-* Improved **surface clearer governance stability signals:** Operators can now see when stored governance proposals fail to decode during stability checks, which makes governance troubleshooting easier and keeps transition monitoring clearer.
-* Refined **pick up devnet configurator changes at startup:** Devnet runs now rebuild the configurator image before launch, which helps environment setup reflect the latest configuration behavior more reliably.
-* Enhanced **steady hard-fork readiness checks in tests:** Release validation now waits for hard-fork readiness checks to finish before asserting results, which makes test outcomes more dependable.
-* Updated **clarify mempool and UTxO RPC package guidance:** Embedded package guidance now explains transaction handling and UTxO filtering more clearly, which makes the exposed behavior easier to understand.
-
-### 🔧 Fixes
-
-* Fixed **stop block producers when genesis snapshots fail:** Block producers now stop immediately if startup cannot build the required initial snapshot, which helps prevent unsafe forging starts.
-* Corrected **recover startup state from the right common chain point:** Startup recovery now rolls back to the latest shared chain point when local state no longer matches the selected chain, which helps nodes resume more cleanly after interrupted or divergent starts.
-* Strengthened **honor peer-sharing settings consistently:** Nodes now apply peer-sharing choices correctly across connections, which makes network behavior match the configured role more reliably.
-* Stabilized **return startup errors instead of crashing on missing services:** Startup now reports missing required services as ordinary errors, which makes failed launches easier to diagnose and recover.
-* Hardened **respect real epoch boundaries during leader scheduling:** Block production scheduling now follows the active epoch layout more accurately, which helps leaders avoid incorrect scheduling around changing epoch boundaries.
-* Repaired **restore pool state details more accurately:** Pool state recovery now reads stored pool details more reliably, which helps stake pool views stay complete after startup and rollback work.
-* Prevented **misread offset data from Byron boundary blocks:** Nodes now skip offset indexing for Byron epoch boundary blocks that carry no transactions, which avoids false indexing results during historical processing.
-* Secured **start UTxO RPC TLS sessions without reloading files:** UTxO RPC now keeps the loaded TLS certificate in memory for server startup, which makes secure startup behavior more reliable.
-
-### 📋 What You Need to Know
-
-* Clarified **genesis governance now starts in place:** Networks that define initial governance delegates and voter registrations now begin with that governance state already loaded, which makes early governance visibility more complete from startup.
-* Highlighted **safer startup recovery and clearer failure handling:** Block producers now stop when required startup snapshots fail, startup reports missing required services as ordinary errors, and divergent startup state now rolls back to the right shared chain point more cleanly.
-* Emphasized **more reliable scheduling and peer behavior:** Block production scheduling now respects the active epoch layout more accurately, and peer sharing behavior now follows the configured role more consistently across connections.
-* Summarized **steadier operational support paths:** Governance observability, pool state recovery, historical offset handling, secure UTxO RPC startup, and devnet validation all received updates that make operations easier to trust.
-
-### Recommended Network Compatibility ⚠️
-
-| Network             | Compatible |
-|---------------------|------------|
-| mainnet             | ⛔         |
-| preprod-testnet     | ⛔         |
-| preview-testnet     | ✅         |
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.46.0 (May 13, 2026)
-
-**Title:** Stake account APIs, cardano-node Praos selection, and safer sync recovery
-
-**Date:** May 13, 2026
-
-**Version:** v0.46.0
-
-Hi folks! Here’s what we shipped in v0.46.0.
-
-### ✨ What's New
-
-* Added **expand Blockfrost stake-account coverage:** Blockfrost compatible services can now return stake-account details, associated addresses, delegation history, registration history, and reward history through stake-address endpoints.
-* Introduced **surface chain block-proposed events:** Locally forged blocks now follow a dedicated proposal path before the chain accepts them, which gives operators clearer behavior around block adoption.
-* Expanded **track the highest observed pool certificate sequence:** Block producers can now compare the newest observed pool certificate sequence during startup, which makes outdated certificate counters easier to catch before they cause trouble.
-
-### 💪 Improvements
-
-* Improved **raise the default Leios mempool capacity:** Leios mode now starts with a larger default mempool capacity, which gives transaction-heavy runs more room before the queue fills.
-* Refined **reduce SQLite batch allocation churn:** SQLite metadata backfill now reuses batch storage more efficiently, which helps sustained indexing work run more smoothly.
-* Enhanced **quiet routine NoBlocks log noise:** Routine blockfetch responses that return no blocks now stay at debug level, which keeps normal logs easier to scan for real issues.
-* Updated **strengthen chain-iterator regression coverage:** Regression checks now cover more iterator ordering, rollback, and waiting paths, which increases confidence in chain recovery behavior.
-* Clarified **explain Mithril API-mode backfill behavior more clearly:** API mode guidance now states that historical metadata backfill runs after Mithril snapshot import, which makes full-history expectations easier to understand.
-
-### 🔧 Fixes
-
-* Fixed **align Praos chain selection with cardano-node behavior:** Equal-height chain choices now follow cardano-node tie breaking more closely, which helps nodes converge more reliably during competing forges.
-* Corrected **refresh connections after unrecoverable sync failures:** Nodes now drop affected sync connections and start fresh after security-window or unrecoverable recovery failures, which gives sync recovery a cleaner restart path.
-* Strengthened **use safer chain intersects across snapshot gaps:** Recovery now prefers better chain intersect points across snapshot gaps, which helps sync continue more reliably when history is incomplete.
-* Stabilized **restore account history in deterministic order:** Account recovery now uses block order as well as certificate order, which keeps restored account state consistent when multiple transactions share a slot.
-* Hardened **initialize ledger metrics earlier:** Ledger metrics now exist as soon as ledger state starts, which avoids failures in paths that read metrics before full startup completes.
-* Repaired **propagate rollback recovery errors correctly:** Rollback recovery now returns ancestor lookup and rollback errors directly, which makes serious recovery failures easier to detect and handle.
-
-### 📋 What You Need to Know
-
-* Clarified **broader Blockfrost stake-account API coverage:** Blockfrost compatible services now cover stake-account details, address listings, delegation history, registration history, and reward history through stake-address endpoints.
-* Highlighted **cardano-node aligned Praos tie breaking and safer fresh sync recovery:** Equal-height Praos decisions now follow cardano-node behavior more closely, and unrecoverable sync failures now restart from fresh connections more aggressively.
-* Emphasized **larger Leios mempool defaults and stronger startup checks:** Leios mode now uses a larger default mempool, and pool certificate tracking gives block producers a clearer startup check for stale certificate counters.
-* Summarized **operational polish and documentation updates:** Logging, SQLite batching, regression coverage, and Mithril API-mode guidance all received changes that make operations easier to follow.
-
-### Recommended Network Compatibility ⚠️
-
-| Network             | Compatible |
-|---------------------|------------|
-| mainnet             | ⛔         |
-| preprod-testnet     | ⛔         |
-| preview-testnet     | ✅         |
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.45.0 (May 12, 2026)
-
-**Title:** Batched backfill, ledger safety fixes, and stronger PV11 readiness
-
-**Date:** May 12, 2026
-
-**Version:** v0.45.0
-
-Hi folks! Here’s what we shipped in v0.45.0.
-
-### ✨ What's New
-
-* Added **batch historical backfill work for smoother replay progress:** Historical metadata replay now writes work in larger batches, which helps long backfills move forward more smoothly and keeps checkpoint recovery safer when replay resumes.
-
-### 💪 Improvements
-
-* Improved **verify upcoming protocol-step readiness on a live multi-node path:** Release validation now checks the Conway to vanRossem progression more directly, which increases confidence that mixed-node networks can cross that protocol step cleanly.
-* Refined **expand fuzz-driven regression coverage across core behaviors:** More parsing, storage, networking, and configuration paths now receive broader stress coverage, which helps surface edge cases before they reach operators and integrators.
-* Enhanced **keep publish workflows moving while package indexing catches up:** Release publishing now avoids a broken package refresh step, which keeps releases moving even when package index updates take longer to appear.
-
-### 🔧 Fixes
-
-* Fixed **recover sparse chain intersections more reliably after missing history gaps:** Synchronization can now fall back to safer recent chain points more consistently, which helps recovery continue when recent ledger history is incomplete.
-* Corrected **reject headers that run ahead of safe ledger rules:** Ledger validation now stops headers that claim a protocol step too far beyond the active rules, which reduces the risk of unsafe acceptance during version transitions.
-* Strengthened **skip rollback work that moves past the known ledger tip:** Recovery now avoids applying rollbacks that run ahead of recorded ledger progress, which keeps replay and catch-up behavior safer when metadata trails the raw chain.
-
-### 📋 What You Need to Know
-
-* Clarified **backfill batching and safer replay progress:** Historical replay now batches more backfill work and keeps checkpoint progress safer, which helps long catch-up runs resume more smoothly after interruptions.
-* Highlighted **safer ledger validation, rollback handling, and sparse recovery:** Ledger validation now rejects headers that jump too far ahead, rollback handling no longer pushes past the known ledger tip, and sparse intersect recovery finds safer restart points more reliably.
-* Emphasized **stronger PV11 and fuzz regression coverage:** Release validation now exercises PV11 crossing behavior more directly, and broader stress coverage checks more parsing, storage, networking, and configuration paths for regressions.
-* Summarized **publish maintenance and package-index timing:** Release publishing keeps moving even while package index refreshes may lag because the refresh pull remains disabled.
-
-### Recommended Network Compatibility ⚠️
-
-| Network             | Compatible |
-|---------------------|------------|
-| mainnet             | ⛔         |
-| preprod-testnet     | ⛔         |
-| preview-testnet     | ✅         |
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.44.0 (May 11, 2026)
-
-**Title:** Blockfrost transaction endpoints, steadier Mithril backfill, and safer chain recovery
-
-**Date:** May 11, 2026
-
-**Version:** v0.44.0
-
-Hi folks! Here’s what we shipped in v0.44.0.
-
-### ✨ What's New
-
-* Added **expand Blockfrost transaction access:** Blockfrost compatible services can now look up transaction details, metadata, UTxOs, certificates, redeemers, required signers, and signed CBOR, and they can also submit transactions with clearer submit responses.
-
-### 💪 Improvements
-
-* Improved **preserve Mithril backfill progress across interruptions:** Mithril bootstrap now keeps more recovery state and resumes metadata backfill more safely, which helps interrupted runs continue without losing important progress.
-* Refined **give full devnet validation more time:** Devnet validation now has a longer default timeout, which reduces avoidable failures during full environment checks.
-* Enhanced **recover forked chains across more rollback paths:** Chain reconciliation now handles more rollback and fork combinations without dropping useful chain history, which makes recovery steadier after difficult fork scenarios.
-* Updated **align operational tooling with newer cardano-cli support:** Operational tooling now stays aligned with the newer `cardano-cli` release for smoother maintenance.
-* Modernized **align data handling with newer CBOR support:** Data handling now stays aligned with the newer CBOR library release for steadier compatibility maintenance.
-* Strengthened **align secrets handling with newer sops support:** Encrypted configuration and secrets handling now stay aligned with the newer `sops` release for steadier maintenance.
-* Advanced **align compression support with newer library updates:** Compression support now stays aligned with the newer `klauspost/compress` release for routine compatibility maintenance.
-* Polished **align system support with newer platform updates:** System level compatibility now stays aligned with the newer `golang.org/x/sys` release for steadier maintenance.
-
-### 🔧 Fixes
-
-* Fixed **return safer intersect points from sparse ledger history:** Chains can now find safer meeting points even when recent ledger history is sparse, which helps sync and recovery continue more reliably.
-
-### 📋 What You Need to Know
-
-* Clarified **broader Blockfrost transaction coverage and submit handling:** Blockfrost compatible integrations can now use transaction detail and submit endpoints with clearer coverage across metadata, UTxOs, certificates, redeemers, required signers, signed CBOR, and submit outcomes.
-* Highlighted **safer Mithril backfill and resume handling:** Mithril bootstrap now preserves more recovery state and resumes metadata backfill more safely, which lowers the chance of losing progress after an interrupted run.
-* Emphasized **safer fork and intersect recovery behavior:** Chain recovery now handles sparse intersect points and more fork reconciliation scenarios more safely, which helps nodes recover from difficult rollback paths with less risk of getting stuck.
-* Summarized **maintenance, validation, and dependency updates:** Validation timing and dependency compatibility were refreshed to keep operations and maintenance steadier around this release.
-
-### Recommended Network Compatibility ⚠️
-
-| Network             | Compatible |
-|---------------------|------------|
-| mainnet             | ⛔         |
-| preprod-testnet     | ⛔         |
-| preview-testnet     | ✅         |
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.43.0 (May 9, 2026)
-
-**Title:** Safer block-producer startup, deeper observability, and easier dashboard imports
-
-**Date:** May 9, 2026
-
-**Version:** v0.43.0
-
-Hi folks! Here’s what we shipped in v0.43.0.
-
-### ✨ What's New
-
-* Added **catch block-producer credential problems during startup:** Block producers now stop early when forging credentials are missing, mismatched, expired, or not yet valid, which prevents later surprises after launch.
-* Expanded **track protocol activity and peer state changes:** Operators can now see clearer network behavior signals, which makes it easier to spot unhealthy connections and shifting peer conditions.
-* Introduced **prompt for the Prometheus datasource during dashboard imports:** Bundled Grafana dashboards now ask for the right Prometheus datasource during import, which makes dashboard setup smoother across different Grafana environments.
-
-### 💪 Improvements
-
-* Improved **show epoch progress against wall-clock time in dashboards:** Operators can now compare current epoch slot progress with a wall-clock reference line, which makes slot stalls easier to notice.
-* Refined **track compatibility with gouroboros 0.168.0:** Protocol compatibility now stays aligned with the newer `gouroboros` `0.168.0` release for steadier maintenance and integration tracking.
-
-### 🔧 Fixes
-
-* Updated **limit slow fallback block lookups in large databases:** Large databases and fork recovery paths now avoid long lookup stalls because fallback scans stop quickly and move on to safer recovery paths.
-* Modernized **restart ledger recovery after stale rollback iterators:** Rollback recovery now restarts cleanly when an iterator points at stale chain data, which helps forked chains continue without getting stuck on the wrong branch.
-
-### 📋 What You Need to Know
-
-* Clarified **fail-fast forging startup checks:** Block-producer startup now validates VRF, KES, and operational certificate inputs against Shelley genesis data and available ledger state, so misconfigured or expired credentials stop the node early instead of failing later.
-* Highlighted **broader observability and easier dashboard imports:** Operators now get new protocol and peer observability metrics, and bundled dashboards are easier to import because Grafana prompts for the Prometheus datasource.
-* Emphasized **safer rollback recovery and block-hash lookups:** Rollback recovery and block-hash lookups now behave more safely on forked chains and very large databases because stale iterators restart cleanly and expensive fallback scans stop quickly.
-* Summarized **dependency tracking updates:** Maintenance tracking now includes the `gouroboros` `0.168.0` update.
-
-### Recommended Network Compatibility ⚠️
-
-| Network             | Compatible |
-|---------------------|------------|
-| mainnet             | ⛔         |
-| preprod-testnet     | ⛔         |
-| preview-testnet     | ✅         |
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.42.0 (May 8, 2026)
-
-**Title:** Batch stake account lookups for faster delegation queries
-
-**Date:** May 8, 2026
-
-**Version:** v0.42.0
-
-Hi folks! Here’s what we shipped in v0.42.0.
-
-### ✨ What's New
-
-* Added **batch stake account lookups for faster delegation queries:** Stake-key-heavy delegation and reward account requests now return more smoothly because Dingo can load many stake accounts in one pass.
-
-### 💪 Improvements
-
-* Improved **catch-up checks that no longer stall sync work:** Catch-up runs now stay smoother because hard-fork readiness checks evaluate in the background instead of pausing the main sync path.
-* Refined **larger deep catch-up block batches:** Nodes now pull much larger block batches during deep catch-up, which helps long syncs move forward faster with less stop-and-go behavior.
-* Enhanced **quieter inbound listener logging:** Routine inbound connection handling now produces calmer logs, which makes real connection problems easier to spot.
-* Updated **test environments aligned with cardano-node 11.0.1:** Validation and demo environments now track `cardano-node` `11.0.1`, which keeps operational testing closer to current network expectations.
-* Modernized **project alignment with Go 1.26.x:** Build, test, and release workflows now align on Go `1.26.x`, which keeps maintenance and contributor environments current.
-* Strengthened **Mithril bootstrap rollover coverage:** Regression coverage now checks Mithril bootstrap and candidate nonce rollover paths more thoroughly, which improves confidence around snapshot recovery.
-
-### 🔧 Fixes
-
-* Fixed **governance imports that now preserve proposal history:** Mithril-bootstrapped nodes now keep parent action links, full proposal details, and ratified hard-fork timing so governance stays aligned after snapshot startup.
-* Corrected **archive demo teardown that no longer hangs on pruning shutdown:** The archive demonstration now cleans up pruning data with the right permissions, which makes teardown finish reliably.
-* Stabilized **clearer Bark and UTxO RPC startup failures:** Bark and UTxO RPC now return deterministic startup errors for TLS and port-binding problems, which makes failed launches easier to diagnose.
-* Preserved **Mithril governance roots across snapshot startup:** Mithril bootstrap now seeds governance roots so chained governance proposals keep progressing instead of silently expiring after startup.
-* Hardened **safer peer-sharing defaults by node role:** Block producers now keep peer sharing off by default, while non-block producers fall back to `cardano-node` behavior when the setting is unset.
-* Prevented **rollback recovery from replaying applied headers:** Chainsync rollback recovery now skips headers the node already applied, which prevents recovery from wedging after rollback scenarios.
-* Repaired **benchmark runs that no longer leave stray cloud paths in the worktree:** Benchmark tests now keep temporary cloud-backend metadata out of the worktree, which leaves local checkouts cleaner.
-* Eliminated **pinned-tip rollback loops during no-op rollbacks:** No-op rollbacks at the current tip no longer trigger repeated local resync loops, which keeps chainsync from wedging at a pinned tip.
-* Renamed **Dingo-owned metrics under the dingo_metrics prefix:** Dingo-owned metric families moved from `cardano_node_metrics_*` names to `dingo_metrics_*` names, bundled dashboards now use the new names, and operators who use any affected metrics must update alerts, dashboards, and monitoring queries.
-
-### 📋 What You Need to Know
-
-* Clarified **faster stake account queries:** Batched account lookups now improve delegation and reward account queries for stake-key-heavy workloads.
-* Highlighted **faster and smoother catch-up behavior:** Catch-up behavior is faster and smoother because blockfetch batching scales much more aggressively, and hard-fork initiation checks no longer block the ledger path the same way.
-* Emphasized **safer governance continuity after Mithril bootstrap:** Mithril-bootstrapped nodes should see safer governance continuity because governance roots, parent action links, and ratification timing are now preserved more accurately after snapshot import.
-* Reviewed **operator updates for startup, peer sharing, and metrics:** Operators using Bark, UTxO RPC, PeerSharing, or any affected metrics must update alerts, dashboards, and monitoring queries for the Dingo-owned metric families that moved from `cardano_node_metrics_*` names to `dingo_metrics_*` names:
-  * `cardano_node_metrics_txsEvictedNum_int` -> `dingo_metrics_txsEvictedNum_int`
-  * `cardano_node_metrics_txsExpiredNum_int` -> `dingo_metrics_txsExpiredNum_int`
-  * `cardano_node_metrics_slotBattlesTotal_int` -> `dingo_metrics_slotBattlesTotal_int`
-  * `cardano_node_metrics_blockForgingLatency_seconds` -> `dingo_metrics_blockForgingLatency_seconds`
-  * `cardano_node_metrics_forgedBlockSize_bytes` -> `dingo_metrics_forgedBlockSize_bytes`
-  * `cardano_node_metrics_forgedBlockTxCount_int` -> `dingo_metrics_forgedBlockTxCount_int`
-  * `cardano_node_metrics_leader_slot_checks_total` -> `dingo_metrics_leader_slot_checks_total`
-  * `cardano_node_metrics_leader_slot_won_total` -> `dingo_metrics_leader_slot_won_total`
-  * `cardano_node_metrics_leader_slot_not_won_total` -> `dingo_metrics_leader_slot_not_won_total`
-  * `cardano_node_metrics_leader_vrf_eval_duration_seconds` -> `dingo_metrics_leader_vrf_eval_duration_seconds`
-  * `cardano_node_metrics_leader_stake_lookup_duration_seconds` -> `dingo_metrics_leader_stake_lookup_duration_seconds`
-  * `cardano_node_metrics_leader_last_epoch_slots_checked_int` -> `dingo_metrics_leader_last_epoch_slots_checked_int`
-  * `cardano_node_metrics_leader_last_epoch_slots_won_int` -> `dingo_metrics_leader_last_epoch_slots_won_int`
-  * `cardano_node_metrics_leader_last_epoch_slots_not_won_int` -> `dingo_metrics_leader_last_epoch_slots_not_won_int`
-  * `cardano_node_metrics_leader_last_evaluated_epoch_int` -> `dingo_metrics_leader_last_evaluated_epoch_int`
-  * `cardano_node_metrics_stake_snapshot_capture_duration_seconds` -> `dingo_metrics_stake_snapshot_capture_duration_seconds`
-  * `cardano_node_metrics_stake_snapshot_capture_success_total` -> `dingo_metrics_stake_snapshot_capture_success_total`
-  * `cardano_node_metrics_stake_snapshot_capture_failure_total` -> `dingo_metrics_stake_snapshot_capture_failure_total`
-  * `cardano_node_metrics_stake_snapshot_pool_count_int` -> `dingo_metrics_stake_snapshot_pool_count_int`
-  * `cardano_node_metrics_stake_snapshot_total_active_stake_lovelace` -> `dingo_metrics_stake_snapshot_total_active_stake_lovelace`
-  * `cardano_node_metrics_stake_snapshot_last_successful_epoch_int` -> `dingo_metrics_stake_snapshot_last_successful_epoch_int`
-  * `cardano_node_metrics_peerSelection_peers_by_source` -> `dingo_metrics_peerSelection_peers_by_source`
-  * `cardano_node_metrics_peerSelection_churn_demotions_by_source` -> `dingo_metrics_peerSelection_churn_demotions_by_source`
-  * `cardano_node_metrics_peerSelection_churn_promotions_by_source` -> `dingo_metrics_peerSelection_churn_promotions_by_source`
-  * `cardano_node_metrics_peerSelection_InboundWarmTarget` -> `dingo_metrics_peerSelection_InboundWarmTarget`
-  * `cardano_node_metrics_peerSelection_InboundHotQuota` -> `dingo_metrics_peerSelection_InboundHotQuota`
-  * `cardano_node_metrics_peerSelection_InboundWarmHeld` -> `dingo_metrics_peerSelection_InboundWarmHeld`
-  * `cardano_node_metrics_peerSelection_InboundHotHeld` -> `dingo_metrics_peerSelection_InboundHotHeld`
-  * `cardano_node_metrics_peerSelection_InboundPruned` -> `dingo_metrics_peerSelection_InboundPruned`
-  * `cardano_node_metrics_peerSelection_InboundArrivalsTotal` -> `dingo_metrics_peerSelection_InboundArrivalsTotal`
-  * `cardano_node_metrics_peerSelection_InboundTopologyMatched` -> `dingo_metrics_peerSelection_InboundTopologyMatched`
-  * `cardano_node_metrics_peerSelection_InboundDuplexHeld` -> `dingo_metrics_peerSelection_InboundDuplexHeld`
-  * `cardano_node_metrics_peerSelection_InboundPrunedByReason` -> `dingo_metrics_peerSelection_InboundPrunedByReason`
-  * `cardano_node_metrics_peerSelection_InboundLifecycleTotal` -> `dingo_metrics_peerSelection_InboundLifecycleTotal`
-  * `cardano_node_metrics_peerSelection_InboundHotQuotaUsage` -> `dingo_metrics_peerSelection_InboundHotQuotaUsage`
-  * `cardano_node_metrics_peerSelection_InboundWarmTargetOccupancy` -> `dingo_metrics_peerSelection_InboundWarmTargetOccupancy`
-* Summarized **refreshed tooling and validation:** Tooling and validation were refreshed through Go `1.26.x` alignment, `cardano-node` `11.0.1` test coverage, stronger Mithril rollover regression coverage, and archive-demo reliability improvements.
-
-### Recommended Network Compatibility ⚠️
-
-| Network             | Compatible |
-|---------------------|------------|
-| mainnet             | ⛔         |
-| preprod-testnet     | ⛔         |
-| preview-testnet     | ✅         |
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.41.0 (May 6, 2026)
-
-**Title:** Batched metadata writes, leaner memory use, and safer node behavior
-
-**Date:** May 6, 2026
-
-**Version:** v0.41.0
-
-Hi folks! Here’s what we shipped in v0.41.0.
-
-### ✨ What's New
-
-* Added **batched metadata persistence across supported databases:** Metadata transaction data can now flush in batches across sqlite, MySQL, and Postgres backends, which makes high-volume metadata persistence easier to manage.
-* Expanded **archive node demonstration tooling:** Teams can now run an archive node demonstration with MinIO-backed archive storage, a pruning node, helper scripts, and an end-to-end runnable flow.
-
-### 💪 Improvements
-
-* Improved **leaner default subscriber buffering:** Default subscriber buffers are now much smaller, while high-burst consumers keep large queues where needed, which reduces idle memory use.
-* Refined **era test harness organization:** The era test harness now lives in a clearer shared location, which makes validation work easier to follow.
-* Enhanced **Conway and PV11 readiness confidence:** Readiness coverage now checks Conway and PV11 behavior more clearly, which improves validation confidence.
-* Cleaned **stale rate limit maintenance:** The project now drops an outdated rate-limit constant, which keeps maintenance cleaner without changing runtime behavior.
-* Strengthened **archive node validation coverage:** The archive node demonstration now checks the full runnable flow more thoroughly, which makes the operational demo easier to trust.
-
-### 🔧 Fixes
-
-* Fixed **safer Mithril startup around recoverable metadata gaps:** Missing blob commit-timestamp keys now resolve as empty values, and recoverable mismatches no longer block Mithril or related startup paths.
-* Corrected **iterator handling after storage closes:** Iterator creation now returns an error after Badger closes, which prevents a shutdown panic.
-* Synchronized **stability window reads during era changes:** Stability-window reads now stay aligned with concurrent era updates, which avoids race-driven failures.
-* Released **pruning locks earlier:** Pruning now releases the metadata and prune lock sooner, which reduces contention and improves diagnostics.
-* Preserved **eligible peer continuity during local tip plateaus:** Nodes no longer disconnect their only eligible peer when a local tip plateau appears.
-* Unified **peer identity handling across DNS fallbacks:** Hostname and IP variants now stay consistent for deduplication, deny lists, and DNS-failure logging.
-
-### 📋 What You Need to Know
-
-* Clarified **batched metadata persistence availability:** Batched metadata persistence is now available across sqlite, MySQL, and Postgres backends.
-* Highlighted **lower idle heap usage:** Idle heap usage should be lower because default event subscriber buffers are smaller.
-* Emphasized **safer startup and shutdown paths:** Mithril startup and shutdown behavior is safer around recoverable database edge cases.
-* Summarized **more robust sync and peer management:** Sync and peer-management behavior is safer because plateau recovery and DNS-fallback peer handling are more robust.
-* Reviewed **archive demo updates:** The project now includes an archive-node demonstration plus stronger validation coverage.
-
-### Recommended Network Compatibility ⚠️
-
-| Network             | Compatible |
-|---------------------|------------|
-| mainnet             | ⛔         |
-| preprod-testnet     | ⛔         |
-| preview-testnet     | ✅         |
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.40.0 (May 5, 2026)
-
-**Title:** Governance DRep APIs and safer rollback recovery
-
-**Date:** May 5, 2026
-
-**Version:** v0.40.0
-
-Hi folks! Here’s what we shipped in v0.40.0.
-
-### ✨ What's New
-
-* Added **Blockfrost compatible governance DRep lookups:** Blockfrost compatible services can now look up governance DReps by hex or bech32 identifier and retrieve registration, voting power, and activity details.
-
-### 💪 Improvements
-
-* Improved **newer Blockfrost client compatibility:** Blockfrost backed integrations now stay aligned with the newer `blockfrost-go` client release for smoother API compatibility.
-* Refreshed **protocol and UTxO RPC compatibility:** Core protocol and UTxO RPC support now stay aligned with newer upstream releases, including Conway version 11 expectations, for steadier interoperability.
-
-### 🔧 Fixes
-
-* Corrected **rollback loop recovery:** Nodes now force a fresh chainsync resync when the same rollback repeats, which helps recovery move forward instead of circling on the same point.
-* Stabilized **shutdown during catch up:** Nodes now finish in flight replay work before closing storage, which prevents `DB Closed` shutdown failures during catch up.
-* Realigned **ledger state after rollbacks:** Rollback recovery now rewinds ledger state together with the chain, which prevents repeated validation failures after peers resend the same blocks.
-* Enabled **faster source port reuse:** TCP reconnects now reuse configured source ports more reliably, which reduces reconnect failures after connection churn.
-
-### 📋 What You Need to Know
-
-* Clarified **patch release upgrade guidance:** This is a patch release, and normal upgrade procedures are generally sufficient.
-* Highlighted **new governance DRep lookups:** Blockfrost compatible API users can now look up governance DReps through the new endpoint.
-* Summarized **safer rollback and resync recovery:** Rollback handling now detects loops, rewinds state correctly, and resyncs more cleanly after recovery problems.
-* Emphasized **steadier shutdowns and reconnects:** Catch up shutdowns and source port reuse now behave more reliably, which reduces avoidable interruptions.
-* Reviewed **dependency updates:** Blockfrost, protocol, and UTxO RPC dependencies were refreshed.
-
-### Recommended Network Compatibility ⚠️
-
-| Network             | Compatible |
-|---------------------|------------|
-| mainnet             | ⛔         |
-| preprod-testnet     | ⛔         |
-| preview-testnet     | ✅         |
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.39.3 (May 4, 2026)
-
-**Title:** Correct era transitions, Bark metadata, and peer recovery
-
-**Date:** May 4, 2026
-
-**Version:** v0.39.3
-
-Hi folks! Here’s what we shipped in v0.39.3.
-
-### ✨ What's New
-
-* Noted **no new features:** This patch release focuses on improvements and fixes.
-
-### 💪 Improvements
-
-* Improved **refreshed bundled Cardano network settings:** Synced bundled network settings now include newer peer snapshots, updated guardrails scripts, refreshed topology values, and newer node version expectations for smoother setup.
-* Updated **bundled cardano configs package:** Docker and bundled network settings now use `cardano-configs` `20260430-1` to stay aligned with the refreshed upstream configuration set.
-* Refined **AWS SDK config compatibility:** AWS backed configuration handling now stays aligned with the latest patch level for steadier cloud integration behavior.
-* Modernized **MySQL driver support:** MySQL backed deployments now stay current with `v1.10.0` for ongoing compatibility and maintenance.
-* Refreshed **Google API client support:** Google API integrations now stay current with `v0.277.0` for routine compatibility maintenance.
-* Advanced **AWS S3 SDK maintenance:** S3 backed storage support now includes the latest patch level for steadier ongoing compatibility.
-* Streamlined **devnet contributor workflow:** Contributors can work with the devnet test harness more easily because the end to end test support now lives under `internal/test/devnet` in a clearer shared location.
-
-### 🔧 Fixes
-
-* Corrected **cross era transition correctness:** Dingo now keeps chain selection, nonce handling, leader schedule checks, slot battle resolution, and protocol parameter reads aligned across Shelley to Conway boundaries so peer validation and block production remain correct through hard fork transitions.
-* Preserved **Bark archive metadata for historical lookups:** Bark backed historical block access now keeps the metadata needed to find archived, tombstoned, or pruned blocks through indexed lookups.
-* Realigned **peer recovery after local tip plateaus:** Nodes now resync peer positions after plateau recovery so plateau triggered peer switching is less likely to stay stuck on misaligned peers.
-
-### 📋 What You Need to Know
-
-* Clarified **patch release upgrade guidance:** This is a patch release, and normal upgrade procedures are generally sufficient.
-* Highlighted **safer Shelley to Conway transitions:** The most important runtime change is more reliable cross era validation and block production during Shelley to Conway transitions.
-* Summarized **Bark historical metadata availability:** Bark backed historical block access now returns the metadata needed for archived and tombstoned block lookups.
-* Emphasized **safer plateau recovery behavior:** Plateau recovery now realigns peers after a stalled active peer is recycled, which reduces the chance of getting stuck.
-* Reviewed **config and dependency refreshes:** Bundled Cardano configs now use the newer sync set, and several dependencies were updated for compatibility and maintenance.
-
-### Recommended Network Compatibility ⚠️
-
-| Network             | Compatible |
-|---------------------|------------|
-| mainnet             | ⛔         |
-| preprod-testnet     | ⛔         |
-| preview-testnet     | ✅         |
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.39.2 (May 2, 2026)
-
-**Title:** Improve fork recovery and hard fork readiness
-
-**Date:** May 2, 2026
-
-**Version:** v0.39.2
-
-Hi folks! Here’s what we shipped in v0.39.2.
-
-### ✨ What's New
-
-* Added **hard fork validation plumbing:** Dingo now includes early validation infrastructure for scheduled era transitions and hard fork behavior, which improves confidence before future network changes take effect.
-
-### 💪 Improvements
-
-* Improved **era transition protocol version handling:** Dingo now advances scheduled era transitions with the right protocol version, which makes era changes more reliable and reduces the chance of stalling at a fork boundary.
-* Refined **slot aware post fork protocol handling:** Dingo now selects the right protocol rules for the slot it is forging, which reduces the chance of producing era incompatible boundary blocks during scheduled forks.
-
-### 🔧 Fixes
-
-* Restored **safer at tip fork recovery:** Dingo now backs out more effectively from repeated validation failures at tip, which gives chain selection more room to escape a bad fork instead of getting trapped on the same failing path.
-* Corrected **VRF nonce handling at epoch boundaries:** Dingo now carries forward the right nonce values across epoch boundaries, which keeps leader checks and boundary validation aligned with the active chain.
-
-### 📋 What You Need to Know
-
-* Clarified **patch release upgrade guidance:** This is a patch release, and normal upgrade procedures are generally sufficient.
-* Highlighted **safer tip recovery behavior:** Nodes are less likely to remain stuck on the same failing fork after a tip validation problem.
-* Emphasized **safer era transitions and hard forks:** Scheduled era changes now progress more reliably, with lower risk of stalls or boundary blocks that do not match the active era.
-* Summarized **corrected nonce behavior at epoch boundaries:** Epoch boundary validation and leader related behavior now stay aligned with the correct nonce progression.
-
-### Recommended Network Compatibility ⚠️
-
-| Network             | Compatible |
-|---------------------|------------|
-| mainnet             | ⛔         |
-| preprod-testnet     | ⛔         |
-| preview-testnet     | ✅         |
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.39.1 (May 1, 2026)
-
-**Title:** Safer pruning, rollback recovery, and snapshot nonces
-
-**Date:** May 1, 2026
-
-**Version:** v0.39.1
-
-Hi folks! Here’s what we shipped in v0.39.1.
-
-### ✨ What's New
-
-* Noted **no new features:** This patch release focuses on improvements and fixes.
-
-### 💪 Improvements
-
-* Refined **archive aware Bark cleanup behavior:** Archived blocks now remain resolvable during prune and cleanup work because Bark leaves archive aware tombstones in place and reads honor them.
-
-### 🔧 Fixes
-
-* Preserved **safer rollback cleanup near the Mithril boundary:** Rollback cleanup now keeps gap UTxOs intact near the Mithril boundary, which makes rollback recovery safer.
-* Hardened **archive aware Bark cleanup handling:** Bark pruning and archival handling now preserve the resolvability of archived blocks during cleanup.
-* Corrected **snapshot bootstrap nonce handling across state layouts:** Snapshot bootstrap now reads epoch and snapshot nonces correctly across supported state layouts, which keeps epoch boundary validation correct after bootstrap.
-
-### 📋 What You Need to Know
-
-* Clarified **patch release upgrade guidance:** This is a patch release, and normal upgrade procedures are sufficient for most operators and users.
-* Highlighted **safer pruning and rollback recovery:** Bark pruning now preserves resolvable live UTxOs, and Mithril boundary rollback recovery now preserves the required gap block state for safe recovery.
-* Corrected **snapshot nonce handling after bootstrap:** Snapshot bootstrapped nodes now read the right nonce data across supported snapshot layouts so epoch boundary header and VRF validation continue correctly after bootstrap.
-
-### Recommended Network Compatibility ⚠️
-
-| Network             | Compatible |
-|---------------------|------------|
-| mainnet             | ⛔         |
-| preprod-testnet     | ⛔         |
-| preview-testnet     | ✅         |
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.39.0 (April 30, 2026)
-
-**Title:** Era-aware forging, Bark tuning, and safer diagnostics
-
-**Date:** April 30, 2026
-
-**Version:** v0.39.0
-
-Hi folks! Here’s what we shipped in v0.39.0.
-
-### ✨ What's New
-
-* Added **dedicated profiling listener controls:** Operators can now enable runtime profiling on `debugPort` without exposing those endpoints on the metrics listener, and profiling stays disabled unless explicitly turned on.
-* Expanded **Bark cleanup control and custom S3 endpoint support:** Bark operators can now tune how often cleanup runs, and S3 compatible Bark storage now works more smoothly with custom endpoints.
-* Introduced **ledger driven Bark safety windows:** Bark now derives its safety window from live ledger state, which removes the need to manage a separate `barkSecurityWindow` setting.
-
-### 💪 Improvements
-
-* Improved **near tip sync pacing:** Nodes now gate backup block requests against median peer latency and expose new gate metrics, which keeps near tip sync steadier with less duplicate work.
-* Refined **slot timing tolerance:** Busy nodes and catch up runs now tolerate more normal clock drift before raising noise about timing issues.
-* Enhanced **devnet validation workflow:** Development teams can now run `make test-devnet` for a more consistent devnet validation flow.
-* Modernized **Docker build cleanliness:** Container builds now avoid worktree and bot metadata directories, which keeps build contexts cleaner.
-* Updated **Bark download cancellation handling:** Bark block downloads now honor request cancellation and timeout context more cleanly, and lint coverage now checks that path again.
-
-### 🔧 Fixes
-
-* Fixed **candidate nonce fallback safety:** Epoch and leader election calculations now stay protected when stored nonce rows trail behind block ingestion.
-* Corrected **Shelley to Allegra verification behavior:** Historical era verification now stays correct across the Shelley to Allegra boundary, which restores successful post fork VRF verification.
-* Hardened **multi era block forging:** Block producers can now forge correctly across Shelley through Conway era transitions instead of assuming Conway only block structure.
-* Stabilized **devnet config access for non root containers:** Generated configs and keys now remain easier for non root containers to read during devnet runs.
-* Repaired **txpump devnet build context:** Devnet and test transaction pump builds now resolve the correct Docker Compose build context more reliably.
-
-### 📋 What You Need to Know
-
-* Clarified **Bark tuning changes:** Bark operators should stop expecting a separate `barkSecurityWindow` setting and should use `barkPrunerFrequency` when cleanup cadence needs tuning.
-* Highlighted **profiling opt in behavior:** Profiling users can enable runtime `pprof` on `debugPort`, while metrics stay isolated from debug endpoints by default.
-* Emphasized **safer era transition behavior:** Historical era and era transition runs should see safer behavior from the candidate nonce fallback, the Shelley to Allegra VRF correction, and pre Conway forging support.
-* Summarized **calmer sync and timing behavior:** Near tip sync and timing should feel steadier because shadow blockfetch gating is smarter and slot clock tolerance now allows 500ms of drift.
-* Simplified **devnet and container workflows:** Devnet and test workflows are easier because `make test-devnet`, the txpump build context correction, cleaner Docker contexts, and relaxed test config permissions reduce setup friction.
-
-### Recommended Network Compatibility ⚠️
-
-| Network             | Compatible |
-|---------------------|------------|
-| mainnet             | ⛔         |
-| preprod-testnet     | ⛔         |
-| preview-testnet     | ✅         |
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.38.0 (April 29, 2026)
-
-**Title:** Smarter sync decisions, clearer operations, and ready made dashboards
-
-**Date:** April 29, 2026
-
-**Version:** v0.38.0
-
-Hi folks! Here’s what we shipped in v0.38.0.
-
-### ✨ What's New
-
-* Added **inbound peer controls and visibility:** Operators can now track how inbound peers are accepted, denied, warmed, promoted, cooled down, and pruned, which makes public relays easier to tune and unsolicited traffic easier to manage.
-* Expanded **dashboard based monitoring setup:** Operators can now deploy a full Grafana dashboard bundle with Prometheus scrape settings, alert rules, provisioning files, and setup guidance, which makes node monitoring faster to stand up.
-* Introduced **parallel backup block delivery near tip:** Nodes can now request the same near tip block range from a second suitable peer and prefer the faster response, which keeps sync steadier when multiple peers report the same tip.
-* Delivered **structured era mismatch errors:** Integrations can now detect era mismatch failures through consistent error details instead of relying on plain text parsing.
-* Surfaced **earlier era transition stability signals:** Operators and integrators can now see when an upcoming era transition has effectively stabilized before the epoch boundary arrives, which makes planning safer around governance driven changes.
-
-### 💪 Improvements
-
-* Improved **one step era advancement safety:** Era changes now advance one boundary at a time, which avoids skipping required transition handling when the chain crosses into a new era.
-* Refined **future protocol setting audit guidance:** Maintainers now have a clearer note about a future audit at era boundaries, which makes upcoming governance work easier to track.
-* Enhanced **Windows and macOS build reliability:** Automation now avoids platform specific native linker issues on Windows and macOS, which keeps routine build verification steadier.
-* Modernized **Windows test stability on slower runners:** Automation now gives slower Windows runners more room to finish successfully, which reduces avoidable test failures.
-* Updated **OpenTelemetry stdout tracing support:** Tracing support now stays current with the newer `go.opentelemetry.io/otel/exporters/stdout/stdouttrace` release.
-* Refreshed **Connect API compatibility:** Connect based integrations now stay current with the newer `connectrpc.com/connect` release.
-* Advanced **AWS S3 integration currency:** S3 backed workflows now stay aligned with the newer `github.com/aws/aws-sdk-go-v2/service/s3` release.
-* Polished **AWS client compatibility:** AWS backed components now stay aligned with the newer `github.com/aws/smithy-go` release.
-
-### 🔧 Fixes
-
-* Fixed **active block download continuity during peer switches:** Near tip sync can now keep a block download moving even when the best peer changes, which reduces the chance of repeated restarts during equal tip switching.
-* Corrected **stale nonce cleanup after rollbacks:** Rollback recovery now removes outdated nonce data after fork changes and while loading tip state, which keeps nonce dependent behavior aligned with the active chain.
-* Hardened **async block delivery failure reporting:** Connection error handling now surfaces asynchronous block delivery failures, which makes stuck or failed block delivery easier to detect.
-* Stabilized **connection setup diagnostics:** Connection failure logs now include the remote peer address, which makes troubleshooting failed handshakes easier.
-
-### 📋 What You Need to Know
-
-* Adopt the new Grafana and Prometheus dashboard bundle and alert rules to monitor Dingo nodes more quickly.
-* Expect steadier near-tip sync and smoother equal-tip peer switching because shadow blockfetch, latency aware peer choice, preserved in-flight batches, and clearer blockfetch failure reporting now work together.
-* Note more explicit era and hard-fork handling because Dingo now surfaces upcoming transition stability earlier, advances only one era at a time, and returns typed era mismatch errors.
-* Review the dependency refreshes when maintaining integrations.
-
-### Recommended Network Compatibility ⚠️
-
-| Network             | Compatible |
-|---------------------|------------|
-| mainnet             | ⛔         |
-| preprod-testnet     | ⛔         |
-| preview-testnet     | ✅         |
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.37.0 (April 27, 2026)
-
-**Title:** Genesis bootstrap, governance, and steadier Mithril recovery
-
-**Date:** April 27, 2026
-
-**Version:** v0.37.0
-
-Hi folks! Here’s what we shipped in v0.37.0.
-
-### ✨ What's New
-
-* Added **Ouroboros Genesis bootstrap support:** Operators can now start from Genesis bootstrap flows, which gives early sync a clearer path before the node reaches the current chain tip.
-* Expanded **Genesis mode chain selection:** Nodes can now choose the chain more safely during Genesis mode, which keeps early sync aligned with the right history.
-* Introduced **bootstrap aware peer promotion:** Peer promotion now accounts for bootstrap state, which helps early sync keep useful peers active while the node is still catching up.
-* Delivered **Conway governance ratification support:** Governance aware services can now track ratified actions more completely as Conway governance advances.
-* Enabled **Conway governance enactment handling:** Governance state now follows enacted actions more accurately, which gives operators and integrators a clearer view of active governance outcomes.
-* Preserved **committee quorum persistence:** Committee quorum information now persists across restarts, which keeps governance state steadier after interruptions.
-* Opened **broader governance state handling:** Governance aware integrations can now read and handle more of the Conway governance state without losing important context.
-* Unlocked **new Blockfrost compatible block endpoints:** Blockfrost compatible users can now retrieve additional block details through new block endpoints.
-* Extended **new Blockfrost compatible network endpoints:** Network status integrations can now access new network endpoints in a Blockfrost compatible shape.
-* Introduced **new Blockfrost compatible era endpoints:** Era aware clients can now request era information through new Blockfrost compatible endpoints.
-* Added **new Blockfrost compatible genesis endpoints:** Genesis data is now available through new Blockfrost compatible endpoints for services that need network bootstrap details.
-
-### 💪 Improvements
-
-* Improved **newer Mithril snapshot compatibility:** Bootstrap runs now accept newer snapshot shapes more reliably, which makes setup and recovery smoother across current Mithril data.
-* Refined **interrupted Mithril resume safety:** Resuming after an interrupted Mithril run now behaves more safely, which reduces the chance of a broken recovery path.
-* Enhanced **bootstrap aware peer governance:** Peer promotion and selection now align more closely with bootstrap state, which helps early sync keep useful peers active.
-* Modernized **bootstrap and governance observability:** Operators can now see more metrics and event signals around bootstrap and governance behavior.
-* Updated **operator and integrator guidance:** Documentation and workflow refreshes make recent bootstrap, governance, and API behavior easier to follow.
-
-### 🔧 Fixes
-
-* Fixed **Mithril bootstrap resume reliability:** Mithril bootstrap and resume handling now recover more reliably when a previous run stopped before completion.
-* Corrected **snapshot bootstrap handling:** Snapshot based bootstrap flows now handle current snapshot layouts correctly, which reduces failed setup paths.
-* Hardened **early sync recovery behavior:** Recovery during early sync now follows Genesis mode chain selection and bootstrap aware promotion more safely after interruptions.
-* Stabilized **governance state continuity:** Governance state now keeps ratification, enactment, and committee quorum handling steadier across restarts and replay.
-
-### 📋 What You Need to Know
-
-* Clarified **Genesis bootstrap rollout:** Ouroboros Genesis bootstrap changes early sync behavior, including Genesis mode chain selection and bootstrap aware peer promotion.
-* Highlighted **governance support growth:** Conway governance coverage now reaches ratification, enactment, committee quorum persistence, and broader governance state handling.
-* Emphasized **steadier Mithril recovery:** Mithril bootstrap and resume handling now work more reliably with newer snapshot shapes and safer interrupted resume behavior.
-* Summarized **expanded Blockfrost compatibility:** Blockfrost compatible users can now use new block, network, era, and genesis endpoints.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.36.1 (April 21, 2026)
-
-**Title:** Steadier catch-up sync and refreshed integrations
-
-**Date:** April 21, 2026
-
-**Version:** v0.36.1
-
-Hi folks! Here’s what we shipped in v0.36.1.
-
-### 💪 Improvements
-
-* Improved **catch-up sync stability:** Nodes now stay steadier while catching up because stall checks wait longer, plateau recovery allows more time, and recycle cooldowns stay longer until the node reaches tip, which reduces unnecessary connection recycling and socket churn during large syncs.
-* Updated **AWS integration currency:** AWS backed integrations stay current because the AWS SDK config package and related AWS modules were refreshed.
-* Refreshed **core AWS compatibility:** AWS integrated behavior stays aligned with upstream fixes because the core AWS SDK and `aws/smithy-go` were updated.
-* Modernized **Google API client support:** Google API client support stays current because `google.golang.org/api` now uses a newer release.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.36.0 (April 20, 2026)
-
-**Title:** Asset endpoints and steadier chain operations
-
-**Date:** April 20, 2026
-
-**Version:** v0.36.0
-
-Hi folks! Here’s what we shipped in v0.36.0.
-
-### ✨ What's New
-
-* Added **asset queries for Blockfrost API users:** Blockfrost API users can now query native assets through `/api/v0/assets/{asset}` with the combined asset identifier format.
-* Expanded **era transition visibility:** Era history now shows confirmed upcoming change points more clearly, so slot and time forecasts stay aligned with known transitions.
-* Clarified **safe epoch boundaries:** Era history now reports when an era change cannot happen in the current epoch, which makes forecast results steadier near the epoch boundary.
-
-### 💪 Improvements
-
-* Improved **contributor setup guidance:** Development work is easier to follow because the project now includes clearer guidance for testing, architecture, and profiling.
-* Refreshed **build cache stability:** Automation now uses a newer cache action release for steadier build runs.
-* Updated **protocol support alignment:** Network compatibility stays current with newer upstream protocol updates.
-* Modernized **operator tooling support:** Operational workflows stay aligned with newer Cardano command line tooling.
-* Streamlined **era rollover handling:** Era changes now follow one transition path, which makes chain operations more consistent during rollovers.
-
-### 🔧 Fixes
-
-* Fixed **single relay sync stalls:** Single-relay block producers now keep chain progress steadier when the relay reconnects first after an interruption.
-* Hardened **ledger startup safeguards:** Startup and rollback related paths now stop immediately when the Ouroboros security parameter K is missing or zero.
-* Corrected **fork recovery error reporting:** Fork recovery now returns ancestor lookup failures directly, which makes recovery issues easier to detect.
-* Prevented **Blockfrost startup crashes:** Blockfrost startup now returns a clear error when ledger state is missing instead of crashing.
-* Set **forged block version markers:** Forged blocks now carry the expected minor protocol version for steadier interoperability.
-
-### 📋 What You Need to Know
-
-* Blockfrost API users can now query native assets through /api/v0/assets/{asset} using the concatenated {policy_id}{asset_name_hex} identifier format.
-* Operators should ensure ledger initialization provides a positive Ouroboros security parameter K, because startup and rollback-related paths now fail fast when K is unset or zero.
-* Most users can upgrade normally to v0.36.0; single-relay block producers should see steadier sync behavior, and Blockfrost startup now reports missing ledger state as an error instead of panicking.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.35.3 (April 19, 2026)
-
-**Title:** Improve peer sharing compatibility
-
-**Date:** April 19, 2026
-
-**Version:** v0.35.3
-
-Hi folks! Here’s what we shipped in v0.35.3.
-
-### ✨ What's New
-
-* Noted **no new features:** This patch focuses on improvements and fixes.
-
-### 🔧 Fixes
-
-* Corrected **safer peer sharing behavior:** Dingo now avoids asking peers to share more peers when they do not offer that capability, so connections stay steadier and compatibility is smoother across mixed peer setups.
-
-### 📋 What You Need to Know
-
-* Simplified **upgrade guidance:** Most users only need to upgrade to v0.35.3, and peer sharing now behaves more safely with peers that do not advertise sharing.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.35.2 (April 18, 2026)
-
-**Title:** Safer era forecasts and refreshed dependencies
-
-**Date:** April 18, 2026
-
-**Version:** v0.35.2
-
-Hi folks! Here’s what we shipped in v0.35.2.
-
-### ✨ What's New
-
-* Noted **no new features:** This patch focuses on improvements and fixes.
-
-### 💪 Improvements
-
-* Improved **protocol library compatibility:** Dingo now uses gouroboros v0.165.1 to stay current with upstream protocol library updates.
-
-### 🔧 Fixes
-
-* Corrected **safer era forecasts:** Hard fork era history now stays within the safe forecast horizon, so slot and time lookups do not promise certainty too far past the current ledger tip.
-
-### 📋 What You Need to Know
-
-* Simplified **upgrade guidance:** No action is required for most users, and upgrading to v0.35.2 is sufficient.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.35.1 (April 17, 2026)
-
-**Title:** Steadier peers and faster schedule calculations
-
-**Date:** April 17, 2026
-
-**Version:** v0.35.1
-
-Hi folks! Here’s what we shipped in v0.35.1.
-
-### ✨ What's New
-
-- **No new features:** This patch focuses on improvements and fixes.
-
-### 💪 Improvements
-
-- **Faster epoch nonce computation:** Ledger processing moves faster because epoch nonce calculation now uses stored nonce data instead of decoding every block again.
-- **Quicker leader schedule generation:** Schedule calculation finishes dramatically faster, especially on lower-powered hardware, while keeping the same scheduling behavior.
-- **Current upstream protocol compatibility:** Cardano protocol support stays current because key upstream dependencies were refreshed for smoother compatibility.
-- **Stronger PostgreSQL compatibility:** PostgreSQL-backed setups are more robust because upstream database coverage and compatibility were improved.
-- **More predictable Antithesis defaults:** Test environments are easier to reason about because the default `IMAGE_TAG` now resolves to `main` instead of `latest`.
-
-### 🔧 Fixes
-
-- **Steadier peer selection near tip:** Nodes are less likely to bounce between near-tip peers because chain selection now compares the tips it has actually observed.
-- **Safer UTxO RPC predicate handling:** Deep or cyclic request predicates no longer recurse indefinitely, so requests do not hang or risk crash-like behavior.
-- **More reliable UTxO RPC queries:** SQLite-backed address queries now handle the reserved `transaction` table name correctly, and broader Connect RPC coverage helps harden query, submit, sync, and watch behavior.
-
-### 📋 What You Need to Know
-
-- **No action required for most users:** You're all set—just upgrade to v0.35.1.
-- **Antithesis users:** If you rely on the default IMAGE_TAG in the dingo-praos testnet compose file, it now resolves to `main` instead of `latest`.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-
-## v0.35.0 (April 15, 2026)
-
-**Title:** Smoother sync and faster block lookups
-
-**Date:** April 15, 2026
-
-**Version:** v0.35.0
-
-Hi folks! Here’s what we shipped in v0.35.0.
-
-### ✨ What's New
-
-- **Blockfrost-compatible metadata-label transaction endpoints:** Building Blockfrost-style integrations is easier because you can now query transaction metadata labels using Blockfrost-compatible endpoints.
-
-### 💪 Improvements
-
-- **More complete Mithril bootstrap snapshots:** Startup is smoother because nodes now prepare more of the snapshot data needed for the current epoch window after a Mithril bootstrap.
-- **More resilient peer retry behavior:** Sync is more rock-solid because chainsync and blockfetch retry using the active best peer when target connections aren’t available.
-- **Faster block lookup by hash:** Hash-based block queries are faster because block-by-hash resolution is streamlined across blob storage backends.
-- **Larger event queue capacity:** Bursty workloads are easier to handle because the event queue capacity was increased from 10,000 to 100,000.
-- **Stronger connection direction tracking:** Networking is more rock-solid because chainsync tracks outbound-started clients and the connection manager detects inbound/outbound `ConnectionId` collisions.
-- **Simpler SQLite metadata batching:** Batched metadata writes are easier to manage because a `BatchAccumulator` streamlines collecting and resetting SQLite metadata model batches.
-
-### 🔧 Fixes
-
-- **No user-facing fixes:** This release focuses on new features and improvements.
-
-### 📋 What You Need to Know
-
-- **No action required:** You're all set—just upgrade to v0.35.0.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-
-## v0.34.0 (April 14, 2026)
-
-**Title:** Blockfrost-compatible metadata label endpoints
-
-**Date:** April 14, 2026
-
-**Version:** v0.34.0
-
-Hi folks! Here’s what we shipped in v0.34.0.
-
-### ✨ What's New
-
-- **Blockfrost-compatible metadata-label transaction endpoints:** Building Blockfrost-style integrations is easier because you can now retrieve transactions by metadata label using endpoints that match Blockfrost conventions.
-
-### 💪 Improvements
-
-- **Ledger validation guardrails:** Ledger validation and processing is more consistent in edge cases, which helps avoid repeated work and makes failures easier to understand.
-- **Safer Unix-domain socket startup:** Local Unix socket startup is safer and more reliable, reducing the chance of startup failures due to leftover files.
-- **Clearer submit errors (`utxorpc/submit.go`):** Error messages now provide clearer context when a submission fails, making troubleshooting faster.
-- **Shared SQL address filtering and sentinel errors:** SQL plugins now share a consistent way to filter UTxO addresses and report common failure cases, which improves maintainability and debugging.
-- **Dependency refresh:** Dependencies were refreshed to keep the project current and compatible with upstream fixes and improvements.
-- **More adaptive Antithesis workflow defaults:** CI workflow behavior is now more adaptive, helping reduce unintended pinning to outdated behavior in automation runs.
-
-### 🔧 Fixes
-
-- **No user-facing fixes:** This release focuses on new features and improvements.
-
-### 📋 What You Need to Know
-
-- **Blockfrost integrations:** If you rely on Blockfrost-compatible behavior, you can start using the new metadata-label transaction endpoints immediately without changing existing endpoints.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-
-## v0.33.0 (April 13, 2026)
-
-**Title:** Blockfrost-compatible address endpoints
-
-**Date:** April 13, 2026
-
-**Version:** v0.33.0
-
-Hi folks! Here’s what we shipped in v0.33.0.
-
-### ✨ What's New
-
-- **Blockfrost-compatible address endpoints:** Plugging Dingo into existing Blockfrost-based tooling is easier because you can now query address UTxOs and transactions via Blockfrost-compatible HTTP endpoints.
-- **Epoch-scoped protocol parameters:** Clients can fetch the exact settings they need for historical or upcoming validation because protocol parameters can now be requested for a specific epoch.
-
-### 💪 Improvements
-
-- **Node internals split into focused files:** The codebase is easier to navigate because chainsync recycling, forging, and shutdown logic moved out of `node.go` into dedicated files.
-- **Makefile help and lint targets:** Build and contributor workflows are easier to run consistently because the Makefile now includes `help` and `lint` targets with inline target descriptions.
-- **Dependency and CI refresh:** Compatibility stays smoother because Go module dependencies (including `golang.org/x`), key CI actions, and the txtop Docker image were updated.
-- **Clearer package docs and licensing:** Development is simpler because core packages now include Apache 2.0 headers, richer package docs, and conformance test suite docs under `internal/test/conformance`.
-- **More complete `dingo.yaml.example`:** Getting started is easier because the example config now includes a default `databasePath` that matches the expected on-disk layout.
-
-### 🔧 Fixes
-
-- **Safer chainsync recycling on small topologies:** Small networks are less likely to lose their only workable connection because the recycler now avoids recycling the only eligible peer.
-
-### 📋 What You Need to Know
-
-- **No action required:** You're all set—just upgrade to v0.33.0.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-
-## v0.32.3 (April 10, 2026)
-
-**Title:** Certificate-aware transaction matching
-
-**Date:** April 10, 2026
-
-**Version:** v0.32.3
-
-Hi folks! Here’s what we shipped in v0.32.3.
-
-### ✨ What's New
-
-- **Certificate-aware transaction pattern matching (`has_certificate`):** Filtering certificate-related transactions is easier because you can now match and validate Cardano certificates directly in transaction pattern rules.
-
-### 💪 Improvements
-
-- **More reliable persistent-fork recovery:** Sync is more rock-solid because chain sync now closes the affected connection when it detects a persistent fork.
-
-### 🔧 Fixes
-
-- **No user-facing fixes:** This patch focuses on new features and improvements.
-
-### 📋 What You Need to Know
-
-- **Transaction-pattern configs:** If you maintain custom transaction-pattern rules, you can start using `has_certificate` to filter or detect certificate-related transactions.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-
-## v0.32.2 (April 9, 2026)
-
-**Title:** Stability and polish updates
-
-**Date:** April 9, 2026
-
-**Version:** v0.32.2
-
-Hi folks! Here’s what we shipped in v0.32.2.
-
-### ✨ What's New
-
-- **No new features:** This patch focuses on improvements and fixes.
-
-### 💪 Improvements
-
-- **More reliable connection cleanup:** Network operations stay more rock-solid because the node now detects inactive connections and purges leftover state tied to closed links.
-- **Refreshed telemetry and runtime dependencies:** Observability and compatibility stay smoother because core dependencies (including OpenTelemetry, gRPC, and gonum) were refreshed.
-
-### 📋 What You Need to Know
-
-- **No action required:** You're all set—just upgrade to v0.32.2.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-
-## v0.32.1 (April 7, 2026)
-
-**Title:** Smoother submission controls and matching
-
-**Date:** April 7, 2026
-
-**Version:** v0.32.1
-
-Hi folks! Here’s what we shipped in v0.32.1.
-
-### ✨ What's New
-
-- **No new features:** This patch focuses on improvements and fixes.
-
-### 💪 Improvements
-
-- **Disable transaction submission throttling:** High-throughput workloads are easier to run because setting the transaction submission rate limit to `0` now fully disables throttling.
-- **Refined transaction pattern matching:** Filtering rules are easier to reason about because transaction pattern matching now uses dedicated helpers for `consumes`, `produces`, `has_address`, and asset filters.
-
-### 🔧 Fixes
-
-- **AWS SDK patch updates:** AWS S3 integrations are more rock-solid because AWS SDK for Go v2 S3 modules were bumped to newer patch versions.
-
-### 📋 What You Need to Know
-
-- **No action required:** You're all set—just upgrade to v0.32.1.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-
-## v0.32.0 (April 7, 2026)
-
-**Title:** Background pruning and scalable UTxO search
-
-**Date:** April 7, 2026
-
-**Version:** v0.32.0
-
-Hi folks! Here’s what we shipped in v0.32.0.
-
-### ✨ What's New
-
-- **Periodic Bark block pruning:** Long-running nodes stay smooth because a nifty background task now periodically prunes no-longer-needed Bark blocks and starts and stops cleanly with node startup and shutdown.
-- **Structured `SearchUtxos` pagination and asset filtering:** Finding and listing UTxOs is more consistent and scalable because `SearchUtxos` pagination and asset filtering now use a structured query model handled in the database layer.
-
-### 💪 Improvements
-
-- **Slot-aware transaction validation:** Transaction validation is more rock-solid across slot-clock changes because the ledger and mempool now validate against the current-or-tip slot and track slot-clock fallbacks.
-- **Clearer external interfaces docs:** Integration decisions are simpler because docs now describe client-facing **external interfaces**, clarify Bark’s role, and expand port and configuration tables with defaults and role descriptions.
-- **Updated CI and Docker Go toolchains:** Maintenance is smoother because workflows now use actions/setup-go v6.4.0 and the Dockerfile build image moved from Go 1.25.8-1 to 1.26.1-1.
-- **Dependency refresh:** Compatibility stays rock-solid because we updated fxamacker/cbor to v2.9.1, plutigo to v0.1.1, AWS SDK for Go v2 S3 modules, OpenTelemetry Go to v1.43.0, and google.golang.org/api to v0.274.0.
-
-### 🔧 Fixes
-
-- **No user-facing fixes:** This release focuses on new features and improvements.
-
-### 📋 What You Need to Know
-
-- **No action required:** You're all set—just upgrade to v0.32.0.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-
-## v0.31.1 (April 4, 2026)
-
-**Title:** Clearer rollback recovery outcomes
-
-**Date:** April 4, 2026
-
-**Version:** v0.31.1
-
-Hi folks! Here’s what we shipped in v0.31.1.
-
-### ✨ What's New
-
-- **Clearer rollback recovery status:** Recovery is simpler to understand because chain recovery now reports clearer outcomes after a local rollback.
-
-### 💪 Improvements
-
-- **More consistent recovery staleness checks:** Recovery decisions are more rock-solid because staleness checks are now based on the primary chain tip.
-
-### 🔧 Fixes
-
-- **Rollback-aware recovery test coverage:** Reliability is more rock-solid because recovery and chainsync tests now validate rollback-aware behavior.
-
-### 📋 What You Need to Know
-
-- **No action required:** You're all set—just upgrade to v0.31.1.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-
-## v0.31.0 (April 3, 2026)
-
-**Title:** Storage safeguards and smarter peer sync
-
-**Date:** April 3, 2026
-
-**Version:** v0.31.0
-
-Hi folks! Here’s what we shipped in v0.31.0.
-
-### ✨ What's New
-
-- **Immutable storage settings:** Upgrades are more rock-solid because the node now persists storage mode and network metadata and refuses to open a database if they don’t match your current `--storage-mode` configuration.
-- **Earlier ledger peer discovery:** Peer discovery starts sooner because reconciliation now invokes ledger-based discovery earlier with debug logs and configurable target and bound settings.
-- **Shared transaction filtering (`TxPredicate`):** Transaction submit and watch are more consistent because filtering now uses a shared `TxPredicate` evaluation engine.
-
-### 💪 Improvements
-
-- **Quieter near-tip chain sync logs:** Routine operation is less noisy because chain-sync progress logging now pauses once you’re at least 99.9% synced.
-- **Smarter peer lag filtering:** Sync catch-up is smoother because peer selection now skips nodes that are far behind the best known tip using a `securityParam`-based filter.
-- **Smoother Prometheus defaults and cache visibility:** Metrics setup is simpler because the node now uses the default Prometheus registry when none is provided and exports Badger cache gauges.
-- **More accurate SQLite disk reporting:** Troubleshooting is easier because SQLite disk size reporting and error diagnostics are now more accurate.
-- **Clearer CI workflow documentation:** Release automation is easier to follow because workflow behavior and related documentation were refined.
-
-### 🔧 Fixes
-
-- **Safer fork extension handling:** Fork recovery is smoother because block fetching now restarts cleanly on forks and skips unnecessary rollbacks when a fork extends from your local tip.
-- **Earlier validity-interval rejection:** Mempool processing is more efficient because transactions that can’t be valid yet are rejected up front.
-- **Security dependency update:** Security stays solid because `github.com/go-jose/go-jose/v4` was updated to v4.1.4.
-
-### 📋 What You Need to Know
-
-- **No action required for most users:** You're all set—just upgrade to v0.31.0.
-- **Operators changing storage settings:** If you change storage mode or network for an existing database, the node will now fail fast to prevent opening it with incompatible settings.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-
-## v0.30.0 (April 2, 2026)
-
-**Title:** Paginated pools API and steadier automation
-
-**Date:** April 2, 2026
-
-**Version:** v0.30.0
-
-Hi folks! Here’s what we shipped in v0.30.0.
-
-### ✨ What's New
-
-- **Paginated extended stake pool details (HTTP API):** Pool queries are easier to work with because you can now request extended stake pool data in smaller pages via `/api/v0/pools/extended`.
-
-### 💪 Improvements
-
-- **Dependency refresh:** Builds stay more rock-solid because we updated a key upstream dependency.
-- **More predictable Antithesis runs:** Automation is easier to reason about because the Antithesis GitHub Actions workflow now runs with the expected default argument.
-
-### 🔧 Fixes
-
-- **No surprise automation runs:** CI noise is lower because affected workflows no longer auto-trigger unexpectedly.
-
-### 📋 What You Need to Know
-
-- **Pools API users:** If you use the pools API, consider switching to `/api/v0/pools/extended` to page through extended pool data.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-
-## v0.29.1 (April 2, 2026)
-
-**Title:** Safer APIs and steadier sync
-
-**Date:** April 2, 2026
-
-**Version:** v0.29.1
-
-Hi folks! Here’s what we shipped in v0.29.1.
-
-### ✨ What's New
-
-- **Rolled out expanded transaction builders and txpump testing:** End-to-end testing is easier because you can now build more transaction types and run a randomized txpump loop.
-- **Handy devnet and testnet setup tooling:** Spinning up local and testnet environments is simpler because you now have additional helper scripts, specs, and Antithesis wiring.
-
-### 💪 Improvements
-
-- **Safer API opt-in defaults:** Service exposure is clearer because APIs now only activate when you explicitly opt in.
-- **Steadier rollback iteration:** Catch-up and restart behavior is more predictable because chain iteration is now safer under rollbacks.
-- **Relaxed peer-tip validation during catch-up:** Sync is smoother because peer tip checks are less likely to reject useful peers while you’re catching up.
-- **More reproducible CI and release automation:** Builds are easier to operate because CI and Antithesis automation were hardened.
-- **Refreshed dependency set:** Compatibility stays rock-solid because a key dependency was updated.
-
-### 🔧 Fixes
-
-- **Iterator cleanup in ledger iteration:** Long-running processes are steadier because ledger iteration now avoids potential resource leaks.
-
-### 📋 What You Need to Know
-
-- **No action required:** You're all set—just upgrade to v0.29.1.
-- **API users:** If you rely on Dingo APIs, make sure your configuration explicitly opts in so the endpoints are enabled.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-
-## v0.29.0 (March 31, 2026)
-
-**Title:** Smoother operations and API refinements
-
-**Date:** March 31, 2026
-
-**Version:** v0.29.0
-
-Hi folks! Here’s what we shipped in v0.29.0.
-
-### ✨ What's New
-
-- **Conway-era transaction builders and txpump:** End-to-end testing is easier because you can now generate and run newer-era transactions in automated runs.
-- **Devnet and testnet helpers:** Spinning up test environments is simpler because you now have wallet-focused tests, a configurator script, local devnet helpers, a Dingo testnet spec, and Antithesis `docker-compose` wiring.
-- **Storage disk-usage metrics:** Capacity planning is easier because the blob store and metadata store now export disk-usage (`DiskSize`) Prometheus gauge metrics.
-
-### 💪 Improvements
-
-- **Faster post-snapshot replay:** Restarts are faster because chain-sync now uses a Mithril trust-boundary slot to skip replay work already covered by a snapshot.
-- **Configurable CBOR cache sizing:** Performance tuning is simpler because you can now set the CBOR cache size in configuration.
-- **More predictable Badger defaults:** Deployments are more consistent because storage-mode-specific defaults only apply when values are truly unset.
-- **More accurate Blockfrost responses:** Block and epoch data is more reliable because latest block, epoch, and protocol-parameter responses are now sourced from ledger state and the database.
-
-### 🔧 Fixes
-
-- **Safer rollbacks behind snapshots:** Rollback behavior is more rock-solid because the Mithril trust-boundary now resets when a rollback crosses it.
-- **Rock-solid rollback recovery:** Recovery is smoother because “rollback point not found” now follows the same handling path as `local_tip_plateau`.
-- **Rock-solid WatchTx rollbacks:** Transaction watching is more reliable because WatchTx now supports undo and rollback during chain reorganizations.
-
-### 📋 What You Need to Know
-
-- **No action required:** You're all set—just upgrade to v0.29.0.
-- **Replay and rollback near snapshots:** Testing runs may look different because chain-sync replay now respects the Mithril trust-boundary and resets it on rollback.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-
-## v0.28.0 (March 30, 2026)
-
-**Title:** Network-aware metrics and steadier block production
-
-**Date:** March 30, 2026
-
-**Version:** v0.28.0
-
-Hi folks! Here's what we shipped in v0.28.0.
-
-### ✨ What's New
-
-- **Network-labelled Prometheus metrics and build info:** Dashboard setup is easier because every Prometheus metric now carries a `network` label automatically, and a new `dingo_build_info` gauge exposes version, commit, and Go version at a glance.
-- **Tip gap and epoch gauges:** Sync monitoring is simpler because three new gauges track tip gap (wall-clock slot minus chain tip), Shelley genesis start time, and epoch length.
-- **Transaction metadata label index (Blockfrost):** Metadata queries are faster because a new transaction metadata label table powers indexed lookups with deterministic pagination and rollback-safe cleanup.
-
-### 💪 Improvements
-
-- **Smarter chain selection near tip:** Tip following is steadier because chain selection now prefers the actually-delivered chainsync tip over the advertised remote tip and sticks with the incumbent peer when two peers report the same frontier.
-- **Paginated DumpHistory (UTxO RPC):** Large history queries are more reliable because `DumpHistory` now uses a chain iterator with `next_token` pagination and sensible defaults when `max_items` is omitted.
-- **Leaner TxSubmission pipeline:** CPU usage under load is lower because the unnecessary rate limiter on the pull-based TxSubmission protocol was removed, eliminating a tight retry loop that starved chainsync and blockfetch.
-- **Leios protocols gated behind config:** Compatibility with non-Leios peers is more rock-solid because Leios mini-protocols are now only registered when `EnableLeios` is set, preventing muxer errors from peers that reject unknown protocols.
-
-### 🔧 Fixes
-
-- **Post-Mithril leader election:** Block production after a Mithril bootstrap is more reliable because `EpochNonce()` now falls through to the database when the in-memory nonce is empty, and `CaptureGenesisSnapshot()` falls back to the latest epoch start slot when slot 0 yields no pools.
-- **Forged-block rollback exemption:** Fork resolution after slot battles is correct because the rollback loop detector now exempts rollbacks through slots where the node forged a block.
-- **Richer UTxO RPC responses:** Script evaluation and data queries are more complete because `evalTx` now includes redeemer payloads and `readData` now returns parsed datums.
-
-### 📋 What You Need to Know
-
-- **Metrics dashboards:** If you run Prometheus dashboards, all metrics now include a `network` label — update your queries or selectors if you filter by metric name alone.
-- **Leios users:** If you use Leios mode, make sure `EnableLeios` is set in your configuration; the protocols are no longer registered by default.
-- **Default make target:** `make` no longer runs tests by default — use `make test` explicitly.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-
-## v0.27.7 (March 24, 2026)
-
-**Title:** Steadier sync and leaner storage
-
-**Date:** March 24, 2026
-
-**Version:** v0.27.7
-
-Hi folks! Here’s what we shipped in v0.27.7.
-
-### ✨ What's New
-
-- **Configurable network ID:** Connecting to the right Cardano network is more rock-solid because you can now set the network identifier in configuration.
-- **Optional blob-store compression:** Disk usage can be lower because you can now enable compression for blob storage in some environments.
-- **Devnet transaction pump:** Testing transaction flow is easier because development networks now include an additional transaction pump service.
-
-### 💪 Improvements
-
-- **More stable chain following:** Sync is more rock-solid because chain following and recovery is now more stable during tip changes and temporary peer issues.
-- **Safer rollbacks and replay:** Reorg handling is more predictable because rollback and ledger replay behavior is now safer.
-- **Lighter rewind pruning:** Larger cleanups are smoother because rewind and pruning operations now put less pressure on storage backends.
-- **Stickier best-peer selection:** Peer churn can be lower because peer selection now better preserves stable connections when multiple peers report equivalent tips.
-
-### 🔧 Fixes
-
-- **More consistent blob deletion:** Cleanup is more reliable because blob deletion now better matches transaction behavior.
-- **Graceful missing-blob recovery:** Processing is more resilient because missing blob data is now handled more gracefully in some cases.
-
-### 📋 What You Need to Know
-
-- **Multi-network deployments:** If you run against different Cardano networks, review your config to ensure the correct network is selected.
-- **Docker builds:** If you rely on custom Docker build caching, Docker builds may behave differently.
-- **Tooling refreshes:** Routine updates to build tooling and libraries may land as part of keeping the project secure and compatible.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-
-## v0.27.5 (March 19, 2026)
-
-**Title:** Faster UTxO lookups and steadier sync
-
-**Date:** March 19, 2026
-
-**Version:** v0.27.5
-
-Hi folks! Here’s what we shipped in v0.27.5.
-
-### ✨ What's New
-
-- **Stable UTxO ordering and address queries:** Wallet and explorer-style queries are more predictable because you can now query UTxOs with a stable ordering and look them up efficiently by address.
-- **Observability-only chain-sync clients:** Metrics are clearer because you can now run observability-only chain-sync clients that are counted in metrics without affecting normal client operation.
-- **Automatic chain realignment on startup:** Recoveries after interruptions are easier because ledger startup can now realign chain state automatically without noisy side effects.
-
-### 💪 Improvements
-
-- **More consistent rollback scheduling:** Recovery after chain reorganizations is more reliable because rollback handling now keeps scheduling state more consistent.
-- **Sliding-window chain density:** Chain health signals are more representative because chain density calculations now use a sliding window of recent slots and blocks.
-- **Safer raw block copy resume:** Resuming raw/direct block copying is safer because resume checks are now stricter and reduce accidental skipping or duplication.
-- **Smoother peer governance convergence:** Early runtime is steadier because peer governance now converges faster after startup and follows configuration defaults more consistently.
-- **Better default peer targets:** Peer configuration works out of the box more often because Dingo now falls back to Cardano P2P peer target values when Dingo peer targets aren’t set.
-- **Richer UTxO RPC chain references:** Downstream indexing is easier because UTxO RPC responses now include a more complete reference to chain position.
-- **Clearer stake snapshot errors (SQLite):** Operational debugging is easier because stake snapshot maintenance errors now include clearer context.
-- **Dependency refresh:** Builds are more rock-solid because dependencies were refreshed to keep compatibility and security posture current.
-- **Clearer tests and documentation:** Maintenance is easier because tests and documentation were clarified for long-term readability.
-
-### 🔧 Fixes
-
-- **Resilient ledger block processing:** The node is less likely to go down on transient ledger errors because block processing now restarts on non-fatal errors instead of exiting.
-- **Safer block fetch flushing:** Block downloads recover more cleanly after flush failures because block fetch now cleans up state when flushing pending blocks fails.
-
-### 📋 What You Need to Know
-
-- **Client-count metrics may shift:** Capacity planning may look different because observability-only chain-sync clients are now tracked separately from eligible clients.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-
-## v0.27.4 (March 18, 2026)
-
-**Title:** Reliability and usability refinements
-
-**Date:** March 18, 2026
-
-**Version:** v0.27.4
-
-Hi folks! Here’s what we shipped in v0.27.4.
-
-### ✨ What's New
-
-- **Rock-solid chain-sync recovery:** Sync stays more rock-solid because chain-sync recovers more reliably from stalled or unstable network connections.
-- **Solid chain selection:** Sync wastes less time on poor candidates because chain selection now takes peer suitability into account.
-
-### 💪 Improvements
-
-- **Simpler config loading:** Configuration stays under your control because config loading no longer fills in a default Cardano configuration path.
-- **Sleeker block downloads:** Block downloads are more consistent because header processing no longer gets blocked by duplicate headers.
-- **More robust intersections:** Synchronization starts from the right place more often because intersection point selection is now more robust.
-
-### 🔧 Fixes
-
-- **No missing boundary blocks:** Historical imports are more complete because older-era boundary blocks are no longer skipped during block loading.
-
-### 📋 What You Need to Know
-
-- **Inbound peers excluded from chain choice:** Chain selection behavior may change in mixed inbound/outbound topologies because inbound peers no longer influence which chain is selected.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.27.3 (March 17, 2026)
-
-**Title:** Safer rollbacks and steadier leader election
-
-**Date:** March 17, 2026
-
-**Version:** v0.27.3
-
-Hi folks! Here’s what we shipped in v0.27.3.
-
-### ✨ What's New
-
-- **Follow-tip reset and rollback:** Tip tracking is easier to manage because the follow-tip API now supports safe reset and rollback with clearer metadata about what changed.
-- **Leader election readiness:** Block producer readiness is easier to track because leader election now surfaces epoch-nonce readiness and carries schedule state more reliably across restarts.
-
-### 💪 Improvements
-
-- **More consistent cache sizing:** Sizing runs are easier to tune because cache defaults are more consistent and the BP/PI sizing script now supports explicit memory limits and optional cache overrides.
-- **Predictable KES period semantics:** Operational certificate (KES) periods are more predictable because KES endpoints now standardize on absolute periods while translating internally from the certificate start period.
-- **Preserved original block bytes:** Downstream tooling can retain exact block bytes because API block objects now include the original encoded bytes.
-- **Standard network identifiers from genesis:** Network identification is simpler because genesis reads now return a standard CAIP-2 network identifier derived from network magic.
-- **Smoother peer switching:** Sync stays more rock-solid because chain-sync now preserves its state while only swapping the active connection during a peer switch.
-- **More consistent Mithril imports:** Mithril snapshot imports are more consistent across epochs because imports now normalize snapshot types and centralize persistence and epoch-summary handling.
-- **Protocol dependency validation:** Modern-era transaction handling is more reliable because protocol dependencies were updated and regression tests now guard transaction size behavior.
-- **Safer default containers:** Default containers are safer because the main Docker image now runs as a non-root `dingo` user.
-
-### 🔧 Fixes
-
-- **Resilient background monitoring:** Long-running monitoring is more rock-solid because the stall checker now recovers from panics instead of crashing its background loop.
-- **Robust block fetch batching:** Block fetch serving is more robust because batching now handles iterator errors and connection closes correctly.
-- **Clearer unexpected event handling:** Event processing is easier to debug because chain-sync and block fetch now log unexpected event payload types instead of failing silently.
-- **Reliable shutdown error reporting:** Shutdowns are easier to troubleshoot because node and metrics server shutdown now propagates errors instead of exiting abruptly.
-- **Clear tx-submission failures:** Transaction submission fails more clearly because the tx-submission handlers now return an explicit error when no mempool consumer exists.
-
-### 📋 What You Need to Know
-
-- **Docker volume permissions:** If you run Dingo in Docker with mounted volumes, make sure the data directory is writable by the `dingo` user inside the container.
-- **API integrations:** If you integrate with follow-tip or KES APIs, give your client code a quick check for the updated reset/rollback and period semantics.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.27.2 (March 16, 2026)
-
-**Title:** Snapshot events and safer services
-
-**Date:** March 16, 2026
-
-**Version:** v0.27.2
-
-Hi folks! Here’s what we shipped in v0.27.2.
-
-### ✨ What's New
-
-- **Snapshot event publishing and clean shutdown:** Relay operation is more reliable because the relay now publishes events from snapshots and shuts down cleanly without dropping in-flight work.
-
-### 💪 Improvements
-
-- **HTTP timeouts for public APIs:** Network-facing services are more resilient under slow or stalled connections thanks to new write/read/idle timeouts on the Bark, Blockfrost, and UTxO RPC HTTP servers.
-- **Streamlined peer and connection management:** Peer and connection management is faster and uses fewer resources on constrained machines thanks to quicker inbound host lookups, tighter Badger cache defaults, and expanded benchmarks and sizing guidance.
-- **More consistent key-period handling:** Block production key period handling is more consistent across configurations thanks to improved key-period calculations with added validation and tests.
-- **Race detection in CI:** Test runs catch concurrency bugs earlier because the Linux test job now runs with the Go race detector enabled.
-
-### 🔧 Fixes
-
-- **Safer concurrent chain reads:** Reads are more consistent under load because primary chain and protocol-parameter access are now protected with read locks.
-- **Validated epoch nonce reuse:** Nonce reuse is safer because cached epoch nonce entries are now validated against the nonce provided for the current run before reuse.
-- **Graceful invalid hash handling:** Malformed block metadata no longer crashes encoding because previous-hash length issues now return errors instead of panicking.
-- **SQLite VACUUM actually runs:** Database maintenance now completes as intended because SQLite VACUUM is now executed rather than only prepared.
-
-### 📋 What You Need to Know
-
-- **Build provenance updates:** Supply-chain attestations are easier to verify because build provenance now uses `actions/attest` and updated Docker Hub image subjects.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.27.1 (March 16, 2026)
-
-**Title:** Smoother reconnects and safer chain-sync
-
-**Date:** March 16, 2026
-
-**Version:** v0.27.1
-
-Hi folks! Here’s what we shipped in v0.27.1.
-
-### ✨ What's New
-
-- **Better chain-sync intersection:** Resuming sync is easier and faster because chain-sync uses a denser, wider set of intersect points to improve `ChainSync` intersection behavior.
-
-### 💪 Improvements
-
-- **Inbound connection reuse and `TxSubmission`:** Networking is more rock-solid on reconnect because peer reuse and governance now normalize exact peer addresses, require client-capable connections for reuse, and start `TxSubmission` on duplex inbound connections.
-- **Stake snapshot and epoch summary upserts:** Data storage is more consistent across supported databases because write paths now upsert across DB backends and report errors more clearly.
-- **More robust delegation parsing:** Delegation reads are more reliable because parsing now handles multiple account encodings with expanded tests.
-
-### 🔧 Fixes
-
-- **Dependency refresh:** Upgrades are less error-prone because Go modules were refreshed (including AWS SDK v2/S3, `golang.org/x/*`, `plutigo` v0.0.27, `go-ethereum` v1.17.1, and `google.golang.org/api` v0.271.0).
-
-### 📋 What You Need to Know
-
-- **Go module sync (some builds):** You’re all set for most setups, but if you vendor dependencies or run reproducible builds you may need to re-sync Go modules (update `go.mod`/`go.sum`) to pick up refreshed versions.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.27.0 (March 15, 2026)
-
-**Title:** S3-backed CI tests and embedded network configs
-
-**Date:** March 15, 2026
-
-**Version:** v0.27.0
-
-Hi folks! Here’s what we shipped in v0.27.0.
-
-### ✨ What's New
-
-- **S3-backed CI storage tests:** Storage testing is more rock-solid because CI now spins up a MinIO S3-compatible service and runs coverage across all supported storage backends, including S3.
-- **Embedded network config bundles:** Getting started is easier because preview, preprod, mainnet, and devnet network configs are now embedded and loaded via `EmbeddedConfigFS`.
-
-### 💪 Improvements
-
-- **Snapshot epoch transitions:** Snapshot handling is more reliable because the snapshot manager now processes every epoch transition event during rapid chain progress.
-- **Tip ingestion fast paths:** Sync near the chain tip is sleeker because blockfetch and block insertion reuse queued header data and caller-supplied points to cut redundant work.
-
-### 🔧 Fixes
-
-- **No fixes:** No user-facing fixes shipped in this release.
-
-### 📋 What You Need to Know
-
-- **Compact block metadata format (Badger):** Disk usage can be smaller because you can opt into an optional Badger setting that stores block metadata in a compact binary format.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.26.0 (March 14, 2026)
-
-**Title:** Trusted Mithril downloads and tuned peers
-
-**Date:** March 14, 2026
-
-**Version:** v0.26.0
-
-Hi folks! Here’s what we shipped in v0.26.0.
-
-### ✨ What's New
-
-- **End-to-end Mithril verification:** Mithril downloads are more rock-solid because Dingo now verifies the full certificate chain and signatures using genesis keys from your Cardano configuration.
-
-### 💪 Improvements
-
-- **Peer governor tuning:** Peer connectivity is easier to tune because you can now adjust peer-governor settings, including hot-peer promotion behavior and its defaults.
-
-### 🔧 Fixes
-
-- **No fixes:** No user-facing fixes shipped in this release.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.25.1 (March 13, 2026)
-
-**Title:** Configurable storage and smoother sync
-
-**Date:** March 13, 2026
-
-**Version:** v0.25.1
-
-Hi folks! Here’s what we shipped in v0.25.1.
-
-### ✨ What's New
-
-- **Configurable data directory:** Running in different environments is easier because you can now choose where the node stores its data on disk with `--data-dir`.
-- **Built-in Mithril bootstrap:** Containerized bootstrapping is simpler because Dingo can now spin up Mithril sync without an external client.
-- **Expanded architecture docs:** Understanding the system is easier because `ARCHITECTURE.md` now includes clearer diagrams and explanations.
-
-### 💪 Improvements
-
-- **Idle connection stability:** Long-running connections are more rock-solid because idle sessions are less likely to be dropped unexpectedly.
-- **Resilient sync across reconnections:** Sync is more rock-solid because chainsync and blockfetch handle connection switches more reliably.
-- **Blockfetch overhead:** Observability is sleeker because blockfetch avoids extra work when no one is listening for events.
-- **Dependencies:** Builds are more solid because dependencies were refreshed for consistency.
-
-### 📋 What You Need to Know
-
-- **Upgrade:** You’re all set—no required configuration changes for this release.
-- **Custom storage path:** If you want to store node data somewhere else, pass `--data-dir <path>` at startup.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.25.0 (March 12, 2026)
-
-**Title:** Trusted replay verification and peer counts
-
-**Date:** March 12, 2026
-
-**Version:** v0.25.0
-
-Hi folks! Here’s what we shipped in v0.25.0.
-
-### ✨ What's New
-
-- **Trusted chain verification:** Startup and recovery runs are more rock-solid because your node can now verify the chain from a trusted, immutable replay path.
-
-### 💪 Improvements
-
-- **Peer metrics accuracy:** Peer limits and metrics are more accurate because local client connections are now tracked separately.
-
-### 🔧 Fixes
-
-- **Mithril key defaults (Docker):** Docker deployments are less error-prone because the correct Mithril genesis verification key is now picked up automatically when you don’t provide one.
-
-### 📋 What You Need to Know
-
-- **Peer counts:** If you rely on peer-count metrics or peer-limit tuning, expect local client connections to no longer be included in those counts.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.24.1 (March 12, 2026)
-
-**Title:** Stability and polish
-
-**Date:** March 12, 2026
-
-**Version:** v0.24.1
-
-Hi folks! Here’s what we shipped in v0.24.1.
-
-### 💪 Improvements
-
-- **Deeper rollback scanning:** Sync is more rock-solid because deep rollbacks are only enabled when needed, and block fetch can scan a wider window to find the data it needs.
-
-### 🔧 Fixes
-
-- **Shutdown reliability:** Shutdowns are more rock-solid because node and ledger shutdown paths are less likely to hang, and logs now show how long shutdown took.
-- **Epoch cache consistency checks:** Diagnosing cache issues is easier because epoch cache validation is stricter and catches inconsistencies earlier.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.24.0 (March 11, 2026)
-
-**Title:** Peer sharing controls and import visibility
-
-**Date:** March 11, 2026
-
-**Version:** v0.24.0
-
-Hi folks! Here’s what we shipped in v0.24.0.
-
-### ✨ What's New
-
-- **Peer sharing controls:** Networking is easier to lock down because you can now explicitly enable or disable peer sharing.
-- **CLI help text:** Running the tool is easier because the root command now includes clearer Short and Long help text.
-- **Import progress reporting:** Large data setup runs feel less like a black box because Mithril and ledger/UTxO imports now emit rate-limited progress updates.
-- **Benchmark suite:** Performance testing is more consistent because the benchmark tooling now includes a baseline and detailed ingestion benchmarks.
-
-### 💪 Improvements
-
-- **Docs:** Evaluating Dingo is safer because the README now includes expanded usage, deployment, and DevNet guidance plus a clear “not for production” warning.
-- **Dev mode:** Local runs are less surprising because dev mode now forces storage mode to API and logs when it overrides your configured value.
-- **Connection manager:** Peer connectivity is more rock-solid because inbound connections are treated as the bidirectional link and expected transition timeouts are handled without tearing down peers.
-- **Storage tuning and logging:** Troubleshooting storage is easier because cache defaults were reset and configured cache sizes are now logged on open, with additional Badger and SQLite tuning.
-- **Era-aware validation:** Cross-era validation is more accurate because protocol parameter extraction is now era-aware and governance-state decoding uses raw-element parsing.
-- **Overlay-aware acceptance:** Transaction validity is more consistent because ledger and mempool validation now uses a temporary UTxO overlay with descendant pruning.
-- **CI and publishing:** Releases are more repeatable because CI and publishing workflows were refreshed with Node.js 24.x and newer pinned Docker and GitHub Actions.
-- **Dependencies:** Compatibility is better because key dependencies were updated, including OpenTelemetry Go and gouroboros.
-- **Go toolchain:** Builds are more up to date because the minimum Go version is now 1.25 and CI was updated to match.
-
-### 🔧 Fixes
-
-- **Connection cleanup tests:** Network tests are less flaky because keepalive timeouts are deterministic and connection cleanup is safer.
-- **Block caching and reconciliation:** Sync is more reliable because block caching now uses fixed-size typed hash keys and reconciliation compares hashes consistently.
-
-### 📋 What You Need to Know
-
-- **Go version:** If you build from source, you’ll need Go 1.25 or newer.
-- **Dev mode:** If you run dev mode, Dingo will force storage mode to the API option.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.23.1 (March 11, 2026)
-
-**Title:** Rock-solid Docker publishing
-
-**Date:** March 11, 2026
-
-**Version:** v0.23.1
-
-Hi folks! Here’s what we shipped in v0.23.1.
-
-### 💪 Improvements
-
-- **Docker publishing (Antithesis image):** Publishing is more consistent because the build pipeline now builds, tags, pushes, and generates an attestation for a Linux amd64-only Antithesis Docker image variant.
-
-### 🔧 Fixes
-
-- **No fixes:** No user-facing fixes shipped in this patch.
-
-### 📋 What You Need to Know
-
-- **Upgrade:** You’re all set—no required configuration changes for this release.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.23.0 (March 10, 2026)
-
-**Title:** Overlay-aware validation and a smoother dev mode
-
-**Date:** March 10, 2026
-
-**Version:** v0.23.0
-
-Hi folks! Here’s what we shipped in v0.23.0.
-
-### ✨ What's New
-
-- **Transaction validation:** Transaction validation is more accurate because ledger and mempool checks now account for pending, in-flight changes with a temporary UTxO overlay.
-
-### 💪 Improvements
-
-- **Docs:** Setup is easier because `README.md` now includes expanded usage, deployment, and DevNet guidance plus a clear “not for production” warning.
-- **Publish workflow:** Publishing is more rock-solid because the release workflow now targets Node.js `24.x` and pins key GitHub Actions versions.
-
-### 🔧 Fixes
-
-- **Connection cleanup:** Connection-related tests are less flaky because keepalive timeouts are deterministic and connection cleanup is safer.
-
-### 📋 What You Need to Know
-
-- **Dev mode:** If you run dev mode, Dingo will automatically switch the storage mode to API, so check logs if you expected a different mode.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.22.1 (March 8, 2026)
-
-**Title:** Stability updates and polish
-
-**Date:** March 8, 2026
-
-**Version:** v0.22.1
-
-Hi folks! Here’s what we shipped in v0.22.1.
-
-### 💪 Improvements
-
-- **Transaction validation:** Transaction validation is more consistent because Conway UTxO validation now runs even when a transaction is marked invalid, while script evaluation is still skipped.
-- **Epoch processing:** Epoch processing recovers more gracefully because nonce recomputation falls back to recomputing from epoch start when an anchor block nonce is missing.
-- **Queue handling:** Queue handling is more solid under load because the main event queue size increased from 1,000 to 10,000 and the header queue size is now clamped to at least the default.
-- **Implausible-tip checks:** Implausible-tip checks are safer across edge cases because the logic now uses peer-based reference blocks with overflow-safe arithmetic.
-- **Publish workflow login:** Publishing is more rock-solid because the publish workflow was tweaked to log in using `docker/login-action@v4`.
-- **Publish workflow runtime:** Automation stays more up to date because Node.js `24.x` was rolled out for the publish workflow.
-
-### 🔧 Fixes
-
-- **Epoch cache rollbacks:** Epoch cache handling is safer during concurrent rollbacks because `advanceEpochCache` now guards against empty caches and validates the tail before appending a new epoch.
-- **Test timing:** Tests are less flaky on slower machines because `TestSchedulerRunFailFunc` timing parameters were relaxed.
-
-### 📋 What You Need to Know
-
-- **API bind address:** Config validation no longer defaults the API bind address to `0.0.0.0`, so set it explicitly if you need it.
-- **CI and publishing scripts:** If you maintain custom publishing or CI scripts, give them a quick check for compatibility with Node.js `24.x` and `docker/login-action@v4`.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----
-
-## v0.22.0 (March 7, 2026)
-
-**Title:** Mithril bootstrap, built-in APIs, and block production
-
-**Date:** March 7, 2026
-
-**Version:** v0.22.0
-
-Hi folks! Here’s what we shipped in v0.22.0.
-
-### ✨ What's New
-
-- **Mithril bootstrap:** Node operators can now bootstrap a Dingo node from a Mithril snapshot and have the ledger state imported automatically (see “Fast Bootstrapping with Mithril” in `README.md`).
-- **Built-in HTTP APIs:** You can run Dingo with built-in, configurable HTTP APIs for common ecosystem compatibility.
-- **Block production:** Block production is now supported with Praos leader election and keystore-backed key management.
-- **Lifecycle events:** The node now emits richer on-chain lifecycle events that applications can subscribe to.
-- **Conway governance metadata:** Governance and Conway-era features are now available in the on-chain metadata pipeline.
-- **Leios mode:** A new “leios” mode is available for early experimentation with Leios protocols.
-- **Stake snapshots:** Stake snapshots and stake distribution are now available with persistence and querying.
-
-### 💪 Improvements
-
-- **Faster catch-up validation:** Syncing is now faster and safer by reducing unnecessary validation during initial catch-up.
-- **Tiered storage and caching:** Block and transaction storage can now be tuned for performance and cost with tiered storage and caching options.
-- **Rollback and resync:** Rollback and resync behavior is more robust under forks and stalled peers.
-- **Peer management:** Network and peer management now scales more predictably under load.
-- **Mempool resilience:** Transaction processing is more resilient and configurable under pressure.
-- **Observability:** Observability has been expanded across sync, forging, and storage.
-- **Time and nonce handling:** Epoch, slot, and nonce handling better matches Cardano semantics and edge cases.
-- **Docs:** Developer and operator documentation has been significantly expanded.
-
-### 🔧 Fixes
-
-- **Chainsync stability:** Chainsync is more reliable around header/block fetching and coordination.
-- **Concurrency safety:** Several concurrency and event-delivery deadlocks and goroutine leak risks have been eliminated.
-- **Security hardening:** Security hardening has been added for configuration, filesystem usage, and key material.
-- **Protocol validation:** Cryptographic and protocol-validation correctness has been tightened across eras.
-- **Object-store key encoding:** Storage key encoding issues in object stores have been resolved.
-
-### 📋 What You Need to Know
-
-- **Event consumers:** If you rely on event type strings, update consumers to match the renamed event type strings.
-- **API storage backfill:** If you enable API storage or new tiered storage modes, run a metadata backfill so queries return complete results.
-- **Forging setup:** If you enable forging, double-check VRF/KES/OpCert key paths and permissions first.
-
-### 🙏 Thank You
-
-Thank you for trying!
-
----