Skip to content

Release Notes - v0.2.0

Title: Align V4 builtin coverage, replay tooling, and test coverage

Date: July 31, 2026

Version: v0.2.0

This release aligns Plutigo with the current Plutus V4 builtin set, refreshes conformance and CI workflows, improves CEK execution speed, and adds mainnet replay tooling and corpus coverage.

This release expands runtime validation and adds replay support for mainnet script traces so Plutigo can replay real-world execution paths with stronger coverage.

  • Added mainnet script replay runner: The new plutigo-replay CLI loads replay corpora strictly, runs script replays, and produces execution reports for review.
  • Expanded mainnet replay corpus coverage: The checked in replay corpus now adds test coverage, benchmark support, and legacy integer cost model support for Variant D.
  • Aligned V4 builtin coverage: Plutus V4 builtin availability and tags now match the upstream specification, and the related conformance fixtures now mirror the current builtin set.
  • Improved CEK environment lookups: Indexed ancestor lookup and supporting arena management reduce the work needed during execution.

This update corrects execution and validation behavior so conformance checks reflect current runtime rules.

  • Fixed conformance coverage: The updated test suite now reflects PV11 semantics, builtin cost models, parser validation, and crypto behavior more accurately.
  • Replaced keccak_256 implementation: Plutigo now uses the legacy Keccak implementation from x/crypto, removes the go-ethereum dependency, and keeps builtin coverage tests aligned with the new path.

This release keeps release automation current, reduces unnecessary repository automation, and preserves execution and validation alignment.

  • Refreshed Go setup workflow: The Go setup workflow now pins actions/setup-go at v7.0.0, keeping build workflows current.
  • Updated checkout workflow: The checkout workflow now pins actions/checkout at v7.0.1, keeping build workflows current.
  • Simplified CI maintenance: The issue close date automation no longer runs, reducing unnecessary repository automation.
Edit page

Last updated: