Skip to content

Release Notes - v0.212.4

Title: Require canonical ledger tuple encoding

Version: v0.212.4

Ledger CBOR decoding now rejects fixed-shape tuple values that use indefinite-length arrays or include trailing CBOR bytes.

  • Improved ledger decoding to accept only definite-length CBOR arrays for fixed-shape tuple fields and to reject trailing CBOR bytes. The check covers execution units, redeemer keys and values, voting procedures, governance IDs and anchors, Conway proposal procedures, the Conway protocol-parameter execution-costs field, and Mary transaction output values. Dijkstra voting procedures remain permissive for indefinite-length arrays, and selected protocol-parameter execution-unit tags remain permissive. Transaction and block parsing can now reject previously accepted non-canonical encodings.

Release: v0.212.4


Doc Holiday logo

Docs authored by Doc Holiday

Edit page

Last updated: