Skip to content

Release Notes - v0.220.2

Title: Improve protocol compatibility and input validation

Release date: 2026-11-15

Version: v0.220.2

This release improves protocol compatibility, protects decoders from oversized or malformed data, expands era-specific ledger compatibility, updates local state query APIs, and refreshes dependencies.

  • Improved transaction submission safety by adding Config.MaxTxSize and WithMaxTxSize, bounding ReplyTxs bodies before ledger decoding, and checking ReplyTxIds advertisements against the fixed MaxTxSizeBytes limit of 65,540 bytes. The configured limit applies only to ReplyTxs bodies.
  • Strengthened rational validation by checking raw components before decoding, limiting rational arrays to 10 items, and bounding Euclidean reduction to 96 steps.
  • Corrected IPv6 peer sharing by encoding and decoding address words in big-endian order in the v11/v12 and v13+ CBOR layouts. IPv4 encoding remains unchanged.
  • Matched the node’s GetGovState wire encoding for local state queries.
  • Preserved the last amount for duplicate pre-Conway withdrawal reward accounts while retaining strict duplicate rejection for Conway and Dijkstra.
  • Rejected null or undefined values in required block collections by validating auxiliary-data sets as maps and invalid-transaction collections as arrays. Empty definite and indefinite collections remain valid, and standalone transaction auxiliary data may still be null.
  • Changed GetNonMyopicMemberRewards to use typed NonMyopicMemberRewardsKey inputs and return NonMyopicMemberRewardsResult values with coin and credential keys in canonical node-compatible CBOR order.
  • Refreshed the Plutigo dependency to v0.12.1.
  • Updated the x/crypto dependency to v0.59.0.
  • Enabled last-value-wins handling for duplicate Babbage auxiliary-data indexes while retaining strict duplicate rejection in Conway.

Full Changelog: v0.220.1…v0.220.2

Release: v0.220.2


Doc Holiday logo

Docs authored by Doc Holiday

Edit page

Last updated: