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

feat(network/config): pass custom ssv config & get beacon config from node & remove hardcoded network values #1308

Open
wants to merge 64 commits into
base: stage
Choose a base branch
from

Conversation

nkryuchkov
Copy link
Contributor

@nkryuchkov nkryuchkov commented Feb 6, 2024

Closes #1687, #1865

Changes:

  • split networkconfig.NetworkConfig into networkconfig.SSV and networkconfig.Beacon
  • pass custom SSV network config (networkconfig.SSV) in yaml
  • get beacon config (networkconfig.Beacon) from beacon node
  • script for custom SSV (networkconfig.SSV) config generation
  • refactor code around the networkconfig package
  • get rid of BeaconNetwork interface as it's hard to work with
  • use network values from config instead of hardcoded ones as a preparation for local testnet

olegshmuelov
olegshmuelov previously approved these changes Mar 19, 2024
@nkryuchkov nkryuchkov force-pushed the override-spec-beacon-config branch from 02bff36 to 2ac7d3d Compare November 11, 2024 17:00
@nkryuchkov nkryuchkov marked this pull request as ready for review November 20, 2024 00:52
@nkryuchkov nkryuchkov changed the title feat(network/config): pass custom ssv config & get beacon config from node feat(network/config): pass custom ssv config & get beacon config from node & remove hardcoded network values Nov 20, 2024
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

Successfully merging this pull request may close these issues.

Remove hardcoded slots/epoch numbers Pass custom network config and beacon options
3 participants