plutus-halo2-verifier-gen

Breaks after HF

Blocked by

• upstream fixblockfrostprotocol-parameters

Waiting on

• blockfrostno-evidence, no verdicttransaction-encoding
• cardano-serialization-lib-cslno-evidence, no verdictera-identitytransaction-rules

Lead decisions

• confirmed· blockfrostprotocol-parameters

  The verifier submitter builds transactions from Blockfrost's latest epoch parameters.

  • aiken-verifier/submitter/src/api.rs:86let url = format!("{}/epochs/latest/parameters", BLOCKFROST_API);

• not-reached· aikenplutus-languageplutus-script-context

  The project compiles its own validators to PlutusV3; existing Plutus versions stay valid after the fork, so only PlutusV4 authoring is blocked.

  • aiken-verifier/aiken_halo2/aiken.toml:1name = "iog/aiken_halo2"

• not-reached· blockfrostera-identity

  The submitter does not call /network/eras.

  • aiken-verifier/submitter/src/api.rs:86let url = format!("{}/epochs/latest/parameters", BLOCKFROST_API);

• not-reached· cardano-serialization-lib-cslplutus-languageblock-encodingprotocol-parametersstake-pool-registrationtransaction-encoding

  The submitter builds its own PlutusV3 transaction; PlutusV4 is additive.

  • aiken-verifier/submitter/src/main.rs:192&Language::new_plutus_v3(),

• not-reached· plutus-plutus-coreplutus-languageplutus-script-context

  The Plinth verifier generator targets existing Plutus versions; PlutusV4 is additive.

  • plinth-verifier/plutus-halo2/plutus-halo2.cabal:52, plutus-ledger-api ^>=1.49