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.

Sign up for GitHub

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

Jump to bottom

Sequencer Authentication #14

Closed
avalonche opened this issue Aug 23, 2024 · 2 comments · Fixed by #20
Closed

Sequencer Authentication #14

avalonche opened this issue Aug 23, 2024 · 2 comments · Fixed by #20

Comments

@avalonche
Copy link

Authenticate the sequencer request to get payload on the builder.
@dmarzzz
Copy link
Member

dmarzzz commented Aug 23, 2024

I would keep it simple for now, preconfigure the sequencer signing address on the block builder CLI configuration side, and then make some minimal modification to the op-node sequencer, to sign their block-builder request with the unsafe-block signing key.

@dmarzzz
Copy link
Member

dmarzzz commented Aug 23, 2024

We could make this an array to store a backup key somewhere in event the sequencer needs to switch quickly, but after talking to some L2s they said they have never had to change and if they did it, it would incur down time anyways.

@dmarzzz dmarzzz mentioned this issue Aug 28, 2024
Open
@avalonche avalonche mentioned this issue Sep 4, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add proposer authentication to builder payload flashbots/op-geth
2 participants
@dmarzzz @avalonche