Release Notes - v0.202.5
v0.202.5 (September 2, 2026)
Section titled “v0.202.5 (September 2, 2026)”Title: Refine ledger validation and protocol reliability
Date: September 2, 2026
Version: v0.202.5
This release improves era-specific transaction validity, validates Conway and Dijkstra ledger state more strictly, preserves protocol results during shutdown, and rejects duplicate encoded data.
💪 Improvements
Section titled “💪 Improvements”-
Improved transaction time limits: Transactions with only an upper validity limit now treat that limit as exclusive in Conway and later eras, while Alonzo and Babbage continue to treat it as inclusive.
-
Updated transaction information APIs:
StrictValidityUpperBoundForTransactionidentifies transactions that use strict upper validity limits. TheNewTxInfoV1andNewTxInfoV2signatures changed, so applications that call these constructors must update their arguments. -
Strengthened ledger deposit accounting: Conway and Dijkstra certificate deposits and refunds now match recorded ledger state through
StakeCredentialDepositState, so the ledger rejects inconsistent deposit values. -
Corrected withdrawal and deregistration accounting: Withdrawals must leave a zero reward balance, and legacy stake credential deregistration now uses the recorded deposit amount.
-
Refined committee and constitutional voter checks: Conway now rejects committee certificate and constitutional voter validation when committee records are unavailable or empty, or when a lookup fails. The checks preserve typed credential identity and include the related context in errors.
-
Enhanced Plutus script spending checks: Babbage, Conway, and Dijkstra now require a spend redeemer for every input at a Plutus script address, whether the script comes from transaction witnesses or a CIP-33 reference script. Missing redeemers return
MissingRedeemerForScriptError. -
Preserved block fetch outcomes during shutdown: When shutdown races with block fetching, the service returns each result that fetching determined, each block it delivered, and errors for incomplete ranges; it does not replace those outcomes with
ErrProtocolShuttingDown. -
Rejected duplicate encoded entries: While reading CBOR encoded data, Conway and Dijkstra certificates plus pointer-backed maps for withdrawals, governance, and move instantaneous rewards now reject duplicate logical entries and return structured duplicate errors.
Recommended Network Compatibility ⚠️
Section titled “Recommended Network Compatibility ⚠️”| Network | Compatible |
|---|---|
| mainnet | ⛔ |
| preprod-testnet | ✅ |
| preview-testnet | ✅ |
| musashi | ✅ |
Release: v0.202.5
Compare: v0.202.4…v0.202.5
Docs authored by Doc Holiday