Difference between revisions of "CRIT Failed to start beacon node"
Jump to navigation
Jump to search
Line 3: | Line 3: | ||
May 31 09:44:12.048 [[CRIT]] [[Failed to start beacon node]] reason: Syncing from [[genesis]] is [[insecure]] and incompatible with data availability checks. You should instead perform a checkpoint sync from a trusted node using the [[--checkpoint-sync-url]] option. For a list of public endpoints, see: https://eth-clients.github.io/checkpoint-sync-endpoints/ Alternatively, use [[--allow-insecure-genesis-sync]] if the risks are understood. | May 31 09:44:12.048 [[CRIT]] [[Failed to start beacon node]] reason: Syncing from [[genesis]] is [[insecure]] and incompatible with data availability checks. You should instead perform a checkpoint sync from a trusted node using the [[--checkpoint-sync-url]] option. For a list of public endpoints, see: https://eth-clients.github.io/checkpoint-sync-endpoints/ Alternatively, use [[--allow-insecure-genesis-sync]] if the risks are understood. | ||
+ | == Related == | ||
+ | * [[lighthouse beacon_node]] | ||
− | + | == See also == | |
− | {{lighthouse beacon_node}} | + | * {{lighthouse beacon_node}} |
Revision as of 10:13, 31 May 2024
May 31 09:44:12.048 CRIT Failed to start beacon node reason: Syncing from genesis is insecure and incompatible with data availability checks. You should instead perform a checkpoint sync from a trusted node using the --checkpoint-sync-url option. For a list of public endpoints, see: https://eth-clients.github.io/checkpoint-sync-endpoints/ Alternatively, use --allow-insecure-genesis-sync if the risks are understood.
Related
See also
Advertising: