-
Notifications
You must be signed in to change notification settings - Fork 216
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
Trusted peer setup #3458
Comments
7 tasks
One way to test this: run two nodes, one without bootnodes/discovery and one "normal" - have them trust each other - both nodes should follow the chain. bonus: add a third node connected only to the first node. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
One problem in ethereum is the public proposer election and the ability to map validator to IP and thus DoS all proposers one by one. Also, when upgrading, all peers are lost and it takes time to build up a healthy mesh.
Both these problems can be mitigated by running several beacon nodes in a trusted setup - there are several pieces needed to achieve this:
We currently have the
--direct-peer
option - it bits and pieces of the above but needs more workThe text was updated successfully, but these errors were encountered: