Release Notes - v0.213.5
v0.213.5
Section titled “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.
Breaking Changes
Section titled “Breaking Changes”- Added cumulative block count and encoded byte limits for each block fetch range through
MaxBlocksPerRangeandMaxRangeBytes, plus a non-renewingRangeTimeout. Oversized or long-running ranges now returnErrRangeBlockLimit,ErrRangeByteLimit, orErrRangeTimeout. Receiving a result throughResults()orDrainResults()releases its raw CBOR reservation automatically; consumers must callBlockItem.Release()after processing each result to clear the data they own. Configure the overall retained raw CBOR budget withPipelineConfig.MaxRawCborBytesorWithMaxRawCborBytes; protocol read-buffer accounting also includes retainedbytes.Buffercapacity.
Bug Fixes
Section titled “Bug Fixes”-
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