bootnode: lighthouse --allow-insecure-genesis-sync - #4
Merged
Merged
Conversation
…house host Without it lighthouse refuses to start a fresh datadir from the genesis state once now > deneb_time + the blob availability window (builder.rs), so a future wipe or re-provision of the bootnode would fail to boot. Review follow-up on #3. Claude-Session: https://claude.ai/code/session_017oM6BuiHivCb3CXVx2kboG
![redpandabot[bot]](https://avatars.githubusercontent.com/in/3749543?s=60&v=4){kind=small}
There was a problem hiding this comment.
Adds --allow-insecure-genesis-sync to the bootnode's lighthouse args, matching the exact flag and placement every lighthouse host already uses in group_vars/lighthouse.yaml. The change is minimal, consistent with the repo's own pattern, and there is nothing else in the diff to evaluate.
Reviewed 1 changed file(s) @ 4e4682f6 — no blocking issues found.
"Good enough is good enough."
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to the review on #3.
Every lighthouse host in
group_vars/lighthouse.yamlpasses--allow-insecure-genesis-sync, but the new bootnode lighthouse config didn't. Without it, lighthouseunstable-4b1f3c2refuses to start a fresh datadir from the genesis state oncenow > deneb_time + blob availability window(beacon_node/client/src/builder.rs:343). Gloas at genesis puts Deneb at epoch 0, so that window starts at genesis.This only adds the flag. It takes effect the next time the ethereum_node role runs for
bootnode-1(a beacon restart), so there's no need to run it before genesis. ansible-lint (CI command) passes.https://claude.ai/code/session_017oM6BuiHivCb3CXVx2kboG