feat(test-consume): add engine-witness simulator for witness verification

[spencer-tb]

🗒️ Description

Fully vibe coded experimental.

Adds a new consume engine-witness Hive simulator that drives Amsterdam blockchain-engine fixtures through a witness-emitting Engine API endpoint and verifies the client-generated ExecutionWitness against the
fixture's expected witness.

Supports two transports on a single simulator:

Mode	Endpoint	Witness encoding	Clients today
Default (no flag)	JSON-RPC engine_newPayloadWithWitnessVX	RLP	go-ethereum
--ssz	REST POST /new-payload-with-witness	SSZ	Ethrex feat/zkengine-http prototype only

Both paths converge on a shared NewPayloadWithWitnessResponse dataclass and the same assert_witness_matches helper. Clients that do not implement the chosen transport skip cleanly:

• REST: HTTP 404 / 405 raises EngineWitnessEndpointNotImplementedError
• JSON-RPC: -32601 Method not found is caught and turned into pytest.skip

The simulator also skips whole fixtures with no executionWitness on any payload (i.e. pre-Amsterdam forks).

Usage

Still to test!

# Fill witness-bearing fixtures
uv run fill tests/amsterdam/ --fork=Amsterdam --output=fixtures_witness

# Hive in dev mode (separate shell)
./hive --dev --client go-ethereum
export HIVE_SIMULATOR=http://127.0.0.1:3000

# Default: JSON-RPC + RLP (Geth)
uv run consume engine-witness --input=fixtures_witness

# Alternative: REST + SSZ (Ethrex zkengine-http branch)
uv run consume engine-witness --input=fixtures_witness --ssz

🔗 Related Issues or PRs

• Consumes fixture infrastructure from feat(zkevm): add execution witness support to other fixture formats #2667 (jsign-support-blockchain-test-engine), already merged on projects/zkevm.
• REST+SSZ endpoint spec: execution-apis#773.
• JSON-RPC endpoint it targets by default: go-ethereum#30069.

✅ Checklist

• All: Ran fast static checks to avoid unnecessary CI fails, see also Code Standards and Enabling Pre-commit Checks:

  just static

• All: PR title adheres to the repo standard - it will be used as the squash commit message and should start type(scope):.
• All: Considered updating the online docs in the ./docs/ directory.
• All: Set appropriate labels for the changes (only maintainers can apply labels).

[jsign]

Should this new name be added to

execution-specs/packages/testing/src/execution_testing/cli/pytest_commands/plugins/consume/simulators/base.py

Lines 28 to 42 in 560d632

	@pytest.fixture(scope="function")
	def check_live_port(test_suite_name: str) -> Literal[8545, 8551]:
	"""Port used by hive to check for liveness of the client."""
	if test_suite_name == "eels/consume-rlp":
	return 8545
	elif test_suite_name in {
	"eels/consume-engine",
	"eels/consume-enginex",
	"eels/consume-sync",
	}:
	return 8551
	raise ValueError(
	f"Unexpected test suite name '{test_suite_name}' while setting "
	"HIVE_CHECK_LIVE_PORT."
	)

?

[jsign]

Is this missing an else and some check payload.validation_error?

[github-actions]

This PR has had no recent activity and has been marked as stale.

[JackCC703]

Hey, I’m interested in helping move this forward.

I noticed this PR’s REST+SSZ path is based on the earlier ethereum/execution-apis#773 design:

• POST /new-payload-with-witness
• JSON request body
• custom NewPayloadWithWitnessResponse SSZ container

Since the newer REST-SSZ Engine API draft in ethereum/execution-apis#793 has moved toward /engine/v1/... with Eth-Execution-Version, and MariusVanDerWijden/execution-apis#1 folds the witness route into POST /engine/v1/payloads/witness with PayloadStatusWithWitness, would it be useful if I worked on a small follow-up to compare/update this simulator against the current draft?

I’m thinking of starting narrowly with the REST+SSZ branch :
update the endpoint assumptions and the SSZ response container shape

[jsign]

Hey, I’m interested in helping move this forward.

I noticed this PR’s REST+SSZ path is based on the earlier ethereum/execution-apis#773 design:

• POST /new-payload-with-witness
• JSON request body
• custom NewPayloadWithWitnessResponse SSZ container

Since the newer REST-SSZ Engine API draft in ethereum/execution-apis#793 has moved toward /engine/v1/... with Eth-Execution-Version, and MariusVanDerWijden/execution-apis#1 folds the witness route into POST /engine/v1/payloads/witness with PayloadStatusWithWitness, would it be useful if I worked on a small follow-up to compare/update this simulator against the current draft?

I’m thinking of starting narrowly with the REST+SSZ branch : update the endpoint assumptions and the SSZ response container shape

This PR actaully should be closed, since it is already merged (with some fixes in projects/zkevm). I think your point of updating REST+SSZ still applies reg new formats. Maybe you can try doing a PR against projects/zkevm if youre interested in the update?

I'll close this PR to avoid confusion!

[JackCC703]

Hey, I’m interested in helping move this forward.
I noticed this PR’s REST+SSZ path is based on the earlier ethereum/execution-apis#773 design:

• POST /new-payload-with-witness
• JSON request body
• custom NewPayloadWithWitnessResponse SSZ container

Since the newer REST-SSZ Engine API draft in ethereum/execution-apis#793 has moved toward /engine/v1/... with Eth-Execution-Version, and MariusVanDerWijden/execution-apis#1 folds the witness route into POST /engine/v1/payloads/witness with PayloadStatusWithWitness, would it be useful if I worked on a small follow-up to compare/update this simulator against the current draft?
I’m thinking of starting narrowly with the REST+SSZ branch : update the endpoint assumptions and the SSZ response container shape

This PR actaully should be closed, since it is already merged (with some fixes in projects/zkevm). I think your point of updating REST+SSZ still applies reg new formats. Maybe you can try doing a PR against projects/zkevm if youre interested in the update?

I'll close this PR to avoid confusion!

OK, thanks! I will do it in projects/zkevm.

[jsign]

cc @developeruche ^ fyi