Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(sidecar): build valid fallback payload #89

Merged
merged 1 commit into from
Jun 24, 2024

Conversation

merklefruit
Copy link
Collaborator

No description provided.

@merklefruit merklefruit added C: bolt-sidecar Component: bolt-sidecar T: feature Type: Feature labels Jun 17, 2024
@@ -113,6 +113,8 @@ impl<T: ConstraintsApi, P: PayloadFetcher + Send + Sync> BuilderProxyServer<T, P
{
Ok(Ok(header)) => {
tracing::debug!(elapsed = ?start.elapsed(), "Returning signed builder bid: {:?}", header);
// TODO: verify proofs here. If they are invalid, we should fall back to locally built block
Copy link
Contributor

Choose a reason for hiding this comment

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

We don't need to verify proofs again imo. We can assume mev-boost & relay have already done this. If mev-boost verification fails it will just return no bid

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Makes sense, just thought it would be low cost, plus as a reminder for #24 which is still open

@merklefruit merklefruit marked this pull request as ready for review June 24, 2024 07:26
@mempirate mempirate marked this pull request as ready for review June 24, 2024 07:26
@mempirate mempirate merged commit ca1b391 into feat/sidecar/builder-api Jun 24, 2024
@mempirate mempirate deleted the feat/create-fallback-block branch June 24, 2024 07:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: bolt-sidecar Component: bolt-sidecar T: feature Type: Feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants