Skip to content

Comments

Introduce execution provers in participants#1311

Draft
nalepae wants to merge 2 commits intoethpandaops:mainfrom
nalepae:main
Draft

Introduce execution provers in participants#1311
nalepae wants to merge 2 commits intoethpandaops:mainfrom
nalepae:main

Conversation

@nalepae
Copy link
Contributor

@nalepae nalepae commented Feb 11, 2026

Each participant can now use prover_type and prover_image, that will be connected to the corresponding beacon node.

At the moment, the only usable prover is the "dummy prover", that has to be docker built here.

Example of usage:

participants:
  - el_type: geth
    el_image: ethpandaops/geth:master
    cl_type: prysm
    cl_image: prysm-bn-custom-image:latest
    vc_image: prysm-vc-custom-image:latest


participants:
  - el_type: geth
    el_image: ethpandaops/geth:master
    cl_type: prysm
    cl_image: prysm-bn-custom-image:latest
    vc_image: prysm-vc-custom-image:latest
    prover_type: dummy # <------ Here
    prover_image: dummy-prover:latest # <----- And here


additional_services:
  - dora
  - prometheus_grafana

network_params:
  fulu_fork_epoch: 0
  withdrawal_type: "0x02"
  preset: mainnet
  seconds_per_slot: 4

global_log_level: debug

@barnabasbusa
Copy link
Collaborator

this already a thing, just use el_type: dummy

@nalepae
Copy link
Contributor Author

nalepae commented Feb 20, 2026

It's not the same thing. The prover is a new component, used to create a proof.
See the "dummy" implementation of the prover: https://github.com/nalepae/dummy-prover

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants