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

Use conductor API to bypass p2p syncing of unsafe head #6

Open
jinmel opened this issue Jul 17, 2024 · 1 comment
Open

Use conductor API to bypass p2p syncing of unsafe head #6

jinmel opened this issue Jul 17, 2024 · 1 comment

Comments

@jinmel
Copy link

jinmel commented Jul 17, 2024

P2P gossip channel has undetermined latency for broadcasting unsafe head to the builders. Conductor API has an admin method to receive unsafe head via http request.

@dmarzzz
Copy link
Member

dmarzzz commented Jul 30, 2024

on auth: "jwt auth, from what i recall there is not but should not be hard to add. if you dont want to modify the code there, you can think to wrap/unwrap via a simple reverse proxy. otoh its not hard to had there as well, just add the middleware and protect only that rpc method example. honestly id go with the nginx+sidecar approach."

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