-
Notifications
You must be signed in to change notification settings - Fork 231
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
allow
--external-beacon-api-url
to fallback to genesis if viable (#…
…5998) When using `--external-beacon-api-url`, one has to accompany it with either `--trusted-block-root` or `--trusted-state-root`. If neither is specified, we can fallback to a deeply finalized noncontroversial block root. For networks that started post Altair, e.g., Holesky, the genesis block root fulfills that requirement, as in, it is implicitly trusted. Therefore, if only `--external-beacon-api-url` is provided without any `--trusted-block-root` or `--trusted-state-root`, use genesis block root if it is a viable starting point (post-Altair). ``` build/nimbus_beacon_node \ --network=holesky \ --data-dir="$HOME/Downloads/nimbus/data/holesky" \ "--external-beacon-api-url=http://unstable.holesky.beacon-api.nimbus.team" \ --tcp-port=9010 --udp-port=9010 \ --rest --log-level=DEBUG \ --no-el ```
- Loading branch information
1 parent
2c924bc
commit 89d9dc2
Showing
1 changed file
with
93 additions
and
69 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters