Ensure Plutus V4 scripts can be deserialised by cardano-cli #1448

Activity

1. Jimbo4350

   assigned

   carbolymer

   on Sep 23, 2026
2. carbolymer commented on Sep 25, 2026

   

   carbolymer

   on Sep 25, 2026

   Last edited by carbolymer

   Contributor

   More actions

   The cardano-cli part is straightforward.
   Since cardano-api 11.7.0.0 the script readers are version agnostic, so every --*-script-file option already accepts a PlutusScriptV4 text envelope.
   The --*-plutus-script-v4 flags for the six reference script witness kinds (spending, minting, withdrawal, certificate, vote, proposal) come with golden coverage for a Dijkstra transaction build-raw that uses them and for hashing a V4 envelope:

   • Complete Plutus V4 support and remove Conway hardcodes #1452

   Update, 9 October.

   The ledger blocker is gone.
   cardano-ledger-dijkstra 0.4.0.0 on CHaP carries the Plutus V4 field of the Dijkstra transaction witness set, and cardano-api master builds against it since index-state 2026-10-06:

   • Add a field for PlutusV4 scripts to transaction_witness_set CDDL cardano-ledger#5403

   cardano-api now fails instead of silently dropping a script the era does not support:

   • Fail instead of silently dropping Plutus scripts the era does not support cardano-api#1363

   Plutus V4 in the legacy transaction API for Dijkstra, which --tx-out-reference-script-file and auxiliary scripts go through, is pending in:

   • Add Plutus V4 support in the Dijkstra era cardano-api#1359

   One ledger gap remains.
   cardano-ledger-dijkstra 0.4.0.0 reads auxiliary scripts back only up to Plutus V3, so a V4 auxiliary script is dropped on read-back until a release with:

   • Set Dijkstra's eraMaxLanguage to PlutusV4, fix tests cardano-ledger#6109

   Cost model: the ledger seeds a Plutus V4 cost model at the Dijkstra upgrade with the same parameter names as V3, and cardano-api's Dijkstra genesis defaults include it, so transaction build is not blocked by it.
   Fixtures: an always-succeeds validator compiled against PlutusLedgerApi.V4 produces the same bytes as the relabelled V3 fixture, so the golden fixture is a genuine V4 build.

   The acceptance criteria stay as written.
   The direct-witness golden through transaction build-raw in Dijkstra is no longer deferred and goes into #1452 once #1359 lands.
3. SuganyaAK

   added

   enhancementFor improvements or extensions to existing functionality.For improvements or extensions to existing functionality.

   on Oct 6, 2026
4. carbolymer

   linked a pull request that will close this issueComplete Plutus V4 support and remove Conway hardcodes #1452on Oct 14, 2026
5. carbolymer

   closed this as completedin #1452on Oct 16, 2026