Opcode Live Verifier

TL;DR: This project deploys raw EVM probe contracts and verifies through real transactions whether TLOAD, TSTORE, MCOPY, CLZ, BLOBHASH, and BLOBBASEFEE actually execute on a target node. It also includes a zk_gas_spec scenario suite in a "deploy contract + trigger via tx" form.

Contents

• src/OpcodeProbes.sol: probe runtimes, deployer, and verifier
• src/ZkGasTxCases.sol: on-chain trigger case contract for zk_gas_spec
• test/OpcodeVerifier.t.sol: local regression tests
• test/ZkGasTxCases.t.sol: local regression tests for the on-chain trigger cases
• script/VerifyOpcodes.s.sol: broadcast script for real RPC validation
• script/RunZkGasTxCases.s.sol: zk gas trigger script for real RPC validation

Local Tests

forge test --offline -vv

The local config in this repository currently enables:

• TLOAD/TSTORE, MCOPY, CLZ, BLOBHASH, and BLOBBASEFEE

--offline is used to avoid a Foundry crash in this environment when it attempts online signature decoding. This does not affect the project’s local tests themselves.

To run only the zk gas trigger case tests:

forge test --offline --match-path test/ZkGasTxCases.t.sol -vv

Real Node Validation

Prepare:

export RPC_URL=https://your-node
export PRIVATE_KEY=0x...

Then run:

forge script script/VerifyOpcodes.s.sol:VerifyOpcodesScript \
  --rpc-url "$RPC_URL" \
  --broadcast \
  -vvvv

To execute the zk_gas_spec "deploy contract + tx trigger" cases:

forge script script/RunZkGasTxCases.s.sol:RunZkGasTxCasesScript \
  --rpc-url "$RPC_URL" \
  --broadcast \
  -vvvv

The opcode verification script sends real transactions in this order:

1. Deploy OpcodeDeployer
2. Deploy OpcodeVerifier
3. Deploy the TLOAD/TSTORE, MCOPY, CLZ, BLOBHASH, and BLOBBASEFEE probes
4. Send real invocation transactions through OpcodeVerifier

Each verification emits:

ProbeResult(string opcode, address probe, bool success, bytes raw)

Interpretation:

• TLOAD_TSTORE: success = true and decoded raw equals the written value means supported
• MCOPY: success = true and raw equals the input byte string means supported
• CLZ: success = true and returns the leading-zero count means supported
• BLOBHASH: success = true and returns zero for index 0 outside blob-tx context means the opcode executed correctly
• BLOBBASEFEE: success = true and returns a non-zero value means the opcode executed correctly

Reading Results

You can inspect the transaction hash from the script output, then run:

cast receipt <TX_HASH> --rpc-url "$RPC_URL"

Or inspect the ProbeResult event in a block explorer.

Direct RPC Checks

You can also test BLOBHASH and BLOBBASEFEE directly with eth_call state override.

BLOBHASH(0):

curl -sS "$RPC_URL" \
  -H 'content-type: application/json' \
  --data '{
    "jsonrpc":"2.0",
    "id":1,
    "method":"eth_call",
    "params":[
      {"to":"0x000000000000000000000000000000000000dEaD"},
      "latest",
      {
        "0x000000000000000000000000000000000000dEaD":{
          "code":"0x5f35495f5260205ff3"
        }
      }
    ]
  }'

Expected success result outside blob-tx context:

0x0000000000000000000000000000000000000000000000000000000000000000

BLOBBASEFEE:

curl -sS "$RPC_URL" \
  -H 'content-type: application/json' \
  --data '{
    "jsonrpc":"2.0",
    "id":1,
    "method":"eth_call",
    "params":[
      {"to":"0x000000000000000000000000000000000000dEaD"},
      "latest",
      {
        "0x000000000000000000000000000000000000dEaD":{
          "code":"0x4a5f5260205ff3"
        }
      }
    ]
  }'

Expected success result:

• a 32-byte non-zero integer if the opcode is supported
• an execution error such as invalid opcode if it is not supported

ZK Gas Tx Cases

RunZkGasTxCases.s.sol deploys a ZkGasTxHarness and then sends real transactions to trigger these scenarios one by one:

1. TLOAD/TSTORE
2. MCOPY
3. CALL
4. STATICCALL
5. DELEGATECALL
6. CALLCODE
7. identity precompile
8. modexp precompile
9. CREATE
10. CREATE2

Each entrypoint emits:

event CaseExecuted(string caseId, bool success, bytes data, address related);

Where:

• caseId is the scenario name
• data is the ABI-encoded result
• related is the target address or the newly created child contract address

This script does not depend on a fixed network name. It only depends on configuration values:

export RPC_URL=https://your-endpoint
export PRIVATE_KEY=0x...