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

Anchor Network-Aware Configuration #38

Open
Tracked by #25
AgeManning opened this issue Oct 23, 2024 · 0 comments
Open
Tracked by #25

Anchor Network-Aware Configuration #38

AgeManning opened this issue Oct 23, 2024 · 0 comments
Labels

Comments

@AgeManning
Copy link
Member

There are often multiple networks with various configurations.

For example, mainnet and current and future testnets.

These networks contain their own settings and sets of bootstrap nodes.

They are often defined by a configuration file. We should check to see these configurations in SSV. Perhaps we can piggy back off the beacon node to define which SSV network to connect to.

We need to be SSV-network aware, so that we can connect to the required peers for the given network.

@jking-aus jking-aus mentioned this issue Oct 28, 2024
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant