Release Notes - v0.7.2

v0.7.2 (September 21, 2026)

Title: Defer execution checks and align evaluation behavior

Date: September 21, 2026

Version: v0.7.2

Release: v0.7.2

Comparison: v0.7.1…v0.7.2

This release separates reference script storage from execution checks, keeps evaluation behavior consistent, aligns validation with phase two rejection rules, and updates the CBOR decoder for safer map handling.

🔧 Fixes

• Improved script version handling: Applications can now store and decode well-formed reference scripts even when their declared term version lacks execution support. Before evaluation, Plutigo accepts term versions 1.0.0 and 1.1.0 under the existing Van Rossem 1.1.0 and PV11 rule, while decoding checks only ledger language availability and Plutigo rejects unsupported versions. Constructors at version 1.1.0 or later now receive support handling.

• Simplified evaluation behavior: Plutigo now shares immutable definitions for built-in operations by language version, decodes replay cases once during validation, reuses the decoded cases during execution, and uses the nearest binding in nested scopes before restoring the enclosing binding.

• Corrected phase two validation: Plutigo now fills short cost model lists with math.MaxInt64 for missing parameters, so affected builtins exhaust their budget instead of using compiled-in defaults. PV11 rejects constants whose encoded type tag size exceeds 32, and Schnorr verification returns false when r or s falls outside its valid range.

📦 Additional Changes

• Updated CBOR safety: The decoder now uses github.com/fxamacker/cbor/v2 2.9.4, which includes an upstream fix for a potential panic when affected CBOR maps contain key values that cannot be compared.

🙏 Thank You

Thank you for using Plutigo.

---

Docs authored by Doc Holiday