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

[proposal] require proposer signature for getHeader request #108

Open
0xalpharush opened this issue Dec 7, 2024 · 1 comment
Open

[proposal] require proposer signature for getHeader request #108

0xalpharush opened this issue Dec 7, 2024 · 1 comment

Comments

@0xalpharush
Copy link

It has been shown that the getHeader API end point leaks information about unconfirmed blocks via its log bloom. I propose not allowing requests from anyone but the proposer by requiring a signature from the proposer's pubkey. If it’s profitable, searchers and builders have an incentive for block proposal to be as delayed as possible (flashbots/mev-boost#111).

In Flashbot's implementation, the signature would be verified here:
https://github.com/flashbots/mev-boost-relay/blob/cf6fd5bdba0df0ef50b3f4afb0bb7162bcf09b8a/services/api/service.go#L1162

@metachris
Copy link
Contributor

Relevant historic thread with more context: flashbots/mev-boost#112

Many relays nowadays support a top-bid websocket stream, which would still keep bids public even if the getHeader endpoint requires a signature.

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

No branches or pull requests

2 participants