Release Notes - v0.66.0
Este contenido aún no está disponible en español.
v0.66.0 (July 19, 2026)
Section titled “v0.66.0 (July 19, 2026)”Title: Advance epoch reward processing and tighten service defaults
Date: July 19, 2026
Version: v0.66.0
This release advances epoch reward handling from calculation through application, adds asynchronous reward precomputation, improves bootstrap recovery for reward data, expands reward-related metadata access, and hardens external APIs and service defaults. It also tightens Blockfrost routing behavior, adds PostgreSQL conformance coverage, and aligns Leios support with Musashi prototype w29.
Recommended Network Compatibility ⚠️
Section titled “Recommended Network Compatibility ⚠️”| Network | Compatible |
|---|---|
| mainnet | ⛔ |
| preprod-testnet | ✅ |
| preview-testnet | ✅ |
| musashi | ✅ |
✨ Highlights
Section titled “✨ Highlights”-
Improved epoch reward calculation and application so nodes prepare reward updates during epoch transitions, keep bootstrap handling aligned with current reward data, and delay the first application until that data is ready.
-
Added asynchronous reward precomputation so reward work starts earlier and the node can apply the prepared results when processing reaches the required point.
-
Expanded reward stake snapshots and reward-related metadata APIs so external integrations can inspect the refreshed reward state and keep the data needed for later reward handling.
-
Fixed Blockfrost unmatched routes to return
404responses so unsupported paths fail with the expected status. -
Enforced TLS 1.2 as the minimum for UTxORPC and Bark servers so older client connections must upgrade before reconnecting.
-
Introduced PostgreSQL conformance coverage so automated checks validate reward behavior across that data store.
-
Synced Leios support with Musashi prototype w29 so supported deployments stay aligned with the latest synchronization behavior.
Full Changelog: v0.65.1…v0.66.0