chore: Add changes needed for optional execution proofs #515
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kevaundray
commented
Nov 3, 2025
Comment on lines
+14
to
+16
| {{ if eq $proof.ProofId 0 }}(SP1+Reth) | ||
| {{ else if eq $proof.ProofId 1 }}(Risc0+Geth) | ||
| {{ else if eq $proof.ProofId 2 }}(SP1+Geth) |
Author
There was a problem hiding this comment.
These labels are hardcoded, but will be changed
kevaundray
commented
Nov 3, 2025
| Endpoint string `yaml:"endpoint" envconfig:"BEACONAPI_ENDPOINT"` | ||
| Endpoints []EndpointConfig `yaml:"endpoints"` | ||
| EndpointsURL string `yaml:"endpointsUrl" envconfig:"BEACONAPI_ENDPOINTS_URL"` | ||
| ClientIndex int `yaml:"clientIndex" envconfig:"BEACONAPI_CLIENT_INDEX"` |
Author
There was a problem hiding this comment.
Hack that we use to fix the node we want to always connect to.
Note: The alternative here would be to not put Dora in the kurtosis config and just running it separately connecting to the specific node we care about.
barnabasbusa
added
the
build-docker-image
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Opening here for visibility
With optional execution proofs, certain nodes will no longer need an EL. They will instead receive proofs over a subnet and that serves as a replacement for validating the execution payload.
Current hacks
When I refresh Dora, it randomly chooses a node from the kurtosis config. However, since "normal nodes" won't necesarily have proofs, I added a hack to allow me to select a specific node each time Dora is refreshed. In the Kurtosis config, I add a "Index" lets say 3, then while setting up Dora, it only keeps the node at index 3.
Another way would be to pass a beacon chain end point, and have that overwrite the other beacon chain endpoints.