Skip to content

build cmd to call isScriptWellFormed phase-1 check #4291

Open
@catch-21

Description

@catch-21

Internal/External
Internal if an IOHK staff member.

Area
Plutus Related to Plutus Scripts (Alonzo).

Summary
When using cli's build cmd there's no feedback when using a plutus script that fails isScriptWellFormed. The MalformedScriptWitnesses error is seen on submit, so this is mostly a UX improvement. This check should be performed before phase-2 script evaluation.

Steps to reproduce
This can probably be recreated by attempting to use malformed script (edit the hex code of a valid script). But I found it this way:

  1. Using a node build that prohibits the use of SECP builtin functions 950c4e2
  2. build a transction with a plutus V2 script that uses one of the SECP functions
  3. Observe phase-2 error "Plutus script evaluation failed"

Expected behavior
Phase-1 error MalformedScriptWitnesses or some other indication of isScriptWellFormed failure

System info
Node version 950c4e2

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions