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

Document high-availability setups #3417

Open
zah opened this issue Feb 18, 2022 · 2 comments
Open

Document high-availability setups #3417

zah opened this issue Feb 18, 2022 · 2 comments

Comments

@zah
Copy link
Contributor

zah commented Feb 18, 2022

Nimbus is compatible with the Blox staking SSV validator node which can be used to create highly-available redundant setups (where 1 out of 3 or 2 out 5 are allowed to fail, for example). In the future, it will also be compatible with the Charon middleware client from the Obol project. We need to document these configurations in a new "High-availability Setup" section in the Nimbus guide.

Besides fault-tolerance, these setups can bring all the advantages discussed in #3416.

@stefantalpalaru
Copy link
Contributor

all the advantages

And the risk of getting slashed if there's a bug in your middleware, right?

@arnetheduck
Copy link
Member

A related feature is the possibility to run several beacon nodes in a trusted mesh - this ensures that blocks and attestations get published via multiple touch-points in the mesh, and each node can independently be taken up and down - ie the idea is that we form private connections between these nodes and they each independently form public connections with the network.

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

3 participants