Simple script provided either on disk or as a reference input. Shared across all script contexts since simple scripts have no context-specific fields.

Plutus script requirements for spending. Spending is the only context that carries an optional datum (CIP-69).

Plutus script requirements for minting. Minting requires a PolicyId so the CLI can validate that every policy being minted has a corresponding script witness and vice versa (see createTxMintValue). For on-disk scripts the PolicyId is computed from the script hash; for reference scripts the user must supply it because the script bytes aren't available locally.

Plutus script requirements for non-asset contexts (certificates, voting, withdrawals, proposals). These contexts need neither a datum nor a policy id, so they share a single type.

A spending script witness — simple or Plutus.

A minting script witness — simple or Plutus. Simple minting scripts are split into on-disk and reference variants because the PolicyId for on-disk scripts is computed from the script hash at read time, while reference scripts require the user to supply it via the CLI.

A non-asset script witness — simple or Plutus. Used for certificates, voting, withdrawals, and proposals.