Skip to content

Make Dora Happy#16441

Merged
terencechain merged 4 commits intodevelopfrom
gloas/payload_endpoint
Mar 4, 2026
Merged

Make Dora Happy#16441
terencechain merged 4 commits intodevelopfrom
gloas/payload_endpoint

Conversation

@potuz
Copy link
Copy Markdown
Contributor

@potuz potuz commented Feb 27, 2026

  • This PR adds the execution_payload_envelope Beacon API endpoint supporting both JSON and SSZ
  • It add the execution_payload_available event stream

it also adds as a stub without a trigger the execution_payload_bid event stream.

These are the minimum necessary to get Dora happy on Kurtosis. Haven't reviewed this PR yet, so opening it as draft. Only check was in Kurtosis against Dora.

Screenshot 2026-02-27 at 7 18 01 PM

potuz and others added 2 commits February 27, 2026 19:22
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@potuz potuz marked this pull request as ready for review March 2, 2026 16:43
@potuz potuz enabled auto-merge March 2, 2026 16:44
@james-prysm james-prysm self-requested a review March 2, 2026 22:09
ExecutionPayloadTopic = "execution_payload_available"
// ExecutionPayloadBidTopic represents a new execution payload bid event topic.
// This topic is currently not triggered but is recognized to avoid client subscription errors.
ExecutionPayloadBidTopic = "execution_payload_bid"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we need some tests for this events.go file

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you can take it from this pr #16323

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we don'tneed payload_attestation_message for dora to be happy?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not for now, payloads and the payload event are enough to show the green/yellow status of payloads.

if !ok {
return errors.New("expected `totalDifficulty` field in JSON response")
}
e.TotalDifficulty, _ = decoded["totalDifficulty"].(string)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why doesn't this need to be handled? i think this change is unrelated

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is no longer there in newer blocks it seems, proably something from v5? I honestly do not know but without this it panics on devnet0, so I made it optional


// ReconstructExecutionPayloadEnvelope --
func (e *EngineClient) ReconstructExecutionPayloadEnvelope(
_ context.Context, envelope *ethpb.SignedBlindedExecutionPayloadEnvelope,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need context if it's not used?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is in the mock, the original function uses it.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks just noticed that didn't realize in initial review

httputil.HandleError(w, "block_root is required in URL params", http.StatusBadRequest)
return
}
rootBytes, err := hexutil.Decode(blockRoot)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this could use this helper instead of having the 2 checks

root, err := bytesutil.DecodeHexWithLength(req.BlockRoot, 32)
if err != nil {
	httputil.HandleError(w, "Could not decode block root: "+err.Error(), http.StatusBadRequest)
	return
}

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 8187f4a

@potuz potuz added this pull request to the merge queue Mar 3, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Mar 3, 2026
@terencechain terencechain added this pull request to the merge queue Mar 3, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Mar 4, 2026
@terencechain terencechain added this pull request to the merge queue Mar 4, 2026
Merged via the queue into develop with commit f7ead02 Mar 4, 2026
18 checks passed
@terencechain terencechain deleted the gloas/payload_endpoint branch March 4, 2026 01:41
github-merge-queue bot pushed a commit that referenced this pull request Mar 13, 2026
…h/v1/beacon/execution_payload_envelope/{block_id} defined in beacon apis (#16521)

**What type of PR is this?**

 Bug fix

**What does this PR do? Why is it needed?**

missed this in review

we should have /eth/v1/beacon/execution_payload_envelope/{block_root} as
/eth/v1/beacon/execution_payload_envelope/{block_id} defined in beacon
apis


https://github.com/ethereum/beacon-APIs/blob/master/apis/beacon/execution_payload/envelope_get.yaml

missed in #16441

**Which issues(s) does this PR fix?**

Fixes #

**Other notes for review**

**Acknowledgements**

- [x] I have read
[CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md).
- [x] I have included a uniquely named [changelog fragment
file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd).
- [x] I have added a description with sufficient context for reviewers
to understand this PR.
- [x] I have tested that my changes work as expected and I added a
testing plan to the PR description (if applicable).
syjn99 pushed a commit to syjn99/prysm that referenced this pull request Mar 27, 2026
…h/v1/beacon/execution_payload_envelope/{block_id} defined in beacon apis (OffchainLabs#16521)

**What type of PR is this?**

 Bug fix

**What does this PR do? Why is it needed?**

missed this in review

we should have /eth/v1/beacon/execution_payload_envelope/{block_root} as
/eth/v1/beacon/execution_payload_envelope/{block_id} defined in beacon
apis


https://github.com/ethereum/beacon-APIs/blob/master/apis/beacon/execution_payload/envelope_get.yaml

missed in OffchainLabs#16441

**Which issues(s) does this PR fix?**

Fixes #

**Other notes for review**

**Acknowledgements**

- [x] I have read
[CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md).
- [x] I have included a uniquely named [changelog fragment
file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd).
- [x] I have added a description with sufficient context for reviewers
to understand this PR.
- [x] I have tested that my changes work as expected and I added a
testing plan to the PR description (if applicable).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants