Release Notes - v0.77.0

v0.77.0

Title: Strengthen governance, synchronization, and API reliability

Date: 2026-10-02

Version: v0.77.0

Release: v0.77.0

Dingo v0.77.0 improves governance processing, forging safety, reward handling, API compatibility, synchronization, and validation. It also adds operational metrics and expands regression coverage across Conway and Dijkstra behavior.

Recommended Network Compatibility ⚠️

Network	Compatible
mainnet	⛔
preprod-testnet	✅
preview-testnet	✅
musashi	✅

Governance and rewards

• Corrected Conway governance processing so RATIFY actions occur before ENACT actions when both apply at an epoch boundary.

• Expanded Conway voting power to include active proposal deposits, giving governance decisions the intended stake representation.

• Refined Conway UpdateCommittee threshold handling so committee updates use the correct approval and quorum rules.

• Covered Dijkstra child governance with regression tests that verify child proposals follow the correct governance path.

• Strengthened Dijkstra regression coverage for duplicate governance proposal identifiers.

Forging and validation

• Secured forging decisions by checking primary chain ancestry before selecting a chain tip.

• Limited forging to at most two unapplied blocks, reducing the chance of extending an unsafe local tip.

• Corroborated peer height reports before using them to guide synchronization and forging decisions.

• Removed the ForgePrimaryChainTipToleranceSlots setting because forging now applies the primary chain ancestry and unapplied block safeguards directly.

Rewards and data validation

• Applied the enacted CIP-50 maxPledgeLeverage value when calculating Dijkstra rewards.

• Handled negative leader rewards explicitly so reward calculations do not produce invalid results.

• Persisted negative leader reward outcomes consistently across restart and state restoration paths.

• Rejected malformed fixed-width hashes immediately instead of allowing invalid values to continue through processing.

API compatibility

• Introduced an optional Kupo API compatible with Kupo v2.12 for deployments that need Kupo access.

• Required API mode to use the API storage tier, making storage selection explicit when enabling the Kupo API.

• Documented future-slot behavior for the Kupo API so responses remain predictable when a requested slot has not arrived.

• Included the expiry boundary in Blockfrost DRep handling, allowing a DRep to remain active through its exact expiry slot.

Synchronization and operational reliability

• Reused Plutus machines through gouroboros v0.208.5, reducing repeated setup during script evaluation.

• Streamlined blockfetch processing by reusing cryptographic verification results for each queued header.

• Restored startup replay handling when networking is unavailable, allowing local recovery work to proceed without a network connection.

• Measured the tip gap during catch-up so operators can observe how far the node remains behind the network tip.

• Rebuilt reward live stake safely around write-ahead log snapshots so recovery does not use an inconsistent state view.

• Preserved reward cache handling during live stake rebuilds, keeping cached values consistent with the rebuilt state.

Testing and quality

• Hardened benchmark scenarios around synchronization and ledger processing to make performance checks more dependable.

• Extended regression coverage for cross-component concurrency and boundary conditions that protect the corrected behavior.

---

Docs authored by Doc Holiday