Release Notes - v0.202.6
v0.202.6 (September 3, 2026)
Section titled “v0.202.6 (September 3, 2026)”Title: Improve block delivery and ledger validation
Date: September 3, 2026
Version: v0.202.6
This release improves raw block delivery when a typed decoder cannot represent a block format, limits script data hash checks to scripts needed by transaction purposes, gates selected checks for transactions that fail phase-two validation, and validates explicitly supplied treasury values.
💪 Improvements
Section titled “💪 Improvements”-
Improved raw block delivery: BlockFetch now falls back to delivering the original block bytes to
BlockRawFuncwhen typed decoding cannot represent the block format. Block validation, range matching against points and previous hashes, continuity checks, and typed consumer behavior remain intact. A typed nil decode result no longer causes a panic. This supports Conway-tagged Dijkstra-shaped blocks, including Musashi payloads. -
Refined script data hash validation: Alonzo, Babbage, Conway, and Dijkstra now build Plutus language views only from scripts needed by transaction purposes, rather than from all reachable witness and reference scripts. Unresolvable spent inputs defer to bad-input validation, while reference-input failures remain part of script data hash validation, so inert reference scripts do not cause canonical transactions to fail.
-
Clarified phase-two transaction checks: Certificate and governance validation now skips transactions that fail phase-two validation, while UTXOW, collateral, redeemer, and structural checks remain active. Dijkstra also skips per-transaction reference-script-size validation for these transactions. Explicit rule grouping preserves validation rule positions.
-
Strengthened current treasury validation: Conway and Dijkstra compare explicitly supplied current treasury values, including explicit zero, with
LedgerState.TreasuryValue; mismatches and provider failures surface as validation errors. Partial script views preserve relevant checks when input resolution fails, and stable validation rule IDs support downstream matching.
Recommended Network Compatibility ⚠️
Section titled “Recommended Network Compatibility ⚠️”| Network | Compatible |
|---|---|
| mainnet | ⛔ |
| preprod-testnet | ✅ |
| preview-testnet | ✅ |
| musashi | ✅ |
Release: v0.202.6
Compare: v0.202.5…v0.202.6
Docs authored by Doc Holiday