Release Notes - v0.197.0
v0.197.0 (August 25, 2026)
Section titled “v0.197.0 (August 25, 2026)”Title: Improve relay and reward validation
Date: August 25, 2026
Version: v0.197.0
This release strengthens relay boundary validation, clarifies reward withdrawal rules across ledger eras, and adds repeatable script view performance benchmarks.
💪 Improvements
Section titled “💪 Improvements”-
Fixed pool relay boundary handling: Pool relays now reject ports above
65535for single host address and name relays, and hostnames longer than128bytes for single host name and multiple host name relays. The rules accept valid boundary values and returnpool relay port must not exceed 65535orpool relay hostname must not exceed 128 bytesfor invalid values. See pool relay boundary details. -
Refined reward withdrawal validation: Transactions from before the Dijkstra era must withdraw the full reward balance. Dijkstra transactions cannot withdraw more than the balance, and partial withdrawals remain available when transactions use no Plutus V1, V2, or V3 scripts. Transactions that use those scripts must withdraw the full balance. Validation now considers scripts in Dijkstra subtransaction witnesses, reports typed
IncorrectWithdrawalAmountErrordetails, and propagates balance lookup failures. Mock fixtures now use versionv0.16.1. See reward withdrawal validation details. -
Added script view performance benchmarks: The test suite now measures construction across transactions with no scripts, a single script spend, and multiple transaction purposes, providing deterministic coverage for performance comparisons. See benchmark details.
Docs authored by Doc Holiday