Skip to content

Release Notes - v0.213.5

Title: Bound block fetching and expand ledger evaluation

Version: v0.213.5

This release bounds block fetch resource use, requires explicit ownership release for fetched results, updates ledger validation for Plutigo v0.9.6, and keeps large ledger data outside the structural UPLC node limit.

  • Added cumulative block count and encoded byte limits for each block fetch range through MaxBlocksPerRange and MaxRangeBytes, plus a non-renewing RangeTimeout. Oversized or long-running ranges now return ErrRangeBlockLimit, ErrRangeByteLimit, or ErrRangeTimeout. Receiving a result through Results() or DrainResults() releases its raw CBOR reservation automatically; consumers must call BlockItem.Release() after processing each result to clear the data they own. Configure the overall retained raw CBOR budget with PipelineConfig.MaxRawCborBytes or WithMaxRawCborBytes; protocol read-buffer accounting also includes retained bytes.Buffer capacity.
  • Corrected phase two and Dijkstra validation fixtures with valid redeemer data and UTxO output addresses while preserving compatible constant-size traversal for supported Plutigo evaluation.

  • Hardened pooled machine handling for panics and unknown caller-built terms, switched constant traversal to syn.Value.Entries(), and updated Plutigo to v0.9.6.

  • Kept datum, redeemer, and script context as trusted Plutigo data for Plutus V1, V2, V3, and V4 evaluation, so large ledger-derived contexts, including inline datums over 1,000,000 nodes, no longer count against the UPLC structural node limit.

Full Changelog: v0.213.4…v0.213.5

Release: v0.213.5

Edit page

Last updated: