Release Notes - v0.205.7

v0.205.7

Title: Improve validation, compatibility, and resource safety

Version: v0.205.7

This release improves ledger validation, era compatibility, cryptographic handling, public API error reporting, and limits on pending network data.

Bug Fixes

• Hardened Leios and Dijkstra validation: signer bitfields now accept at most 8,192 bytes, and Dijkstra bodies reject a Leios certificate when transactions are also present under CIP-0164.

• Stabilized the ChainSync Stop test assertion: the test no longer depends on a racy timing assumption, and production behavior remains unchanged.

• Made malformed ledger inputs fail predictably: malformed Byron inputs, nil Byron headers, over-range governance IDs, and malformed verification hex now return errors or deterministic sentinel output. The public ledger.NewByronTransactionInput function now returns (value, error).

• Strengthened KES secret handling: zeroization now provides stronger cleanup, and evolve-chain tests provide clearer diagnostics when they fail.

• Corrected Alonzo output and collateral validation: min-UTxO sizing now accounts for each output, the decoder rejects removed CBOR key 15, collateral ceiling calculations round correctly, and overflow guards block invalid calculations. The alonzo.MinCoinTxOut function now accepts TransactionOutput.

• Rejected invalid multiasset encodings in Conway and Dijkstra: zero quantities and empty multiasset values now fail according to each era’s rules, while pre-Conway behavior remains unchanged.

• Enforced DRep and governance action limits: DRep values now follow the required CBOR shapes, credentials now require 28 bytes, and governance action indices cannot exceed 65,535.

• Blocked invalid Conway and Dijkstra pointer addresses: out-of-range pointer address components now fail validation, while older eras retain their previous lenient behavior.

• Bounded pending network data: TxSubmission now limits pending bytes, outstanding requests, and callback returns, while connection-wide multiplexer reassembly buffers use a default 16 MiB cap and derive MaxPendingMessageBytes as 721,424.

Release: v0.205.7

Compare: v0.205.6…v0.205.7

---

Docs authored by Doc Holiday