refactor(xatu): merge execution and consensus boot-node cron jobs#641
Draft
refactor(xatu): merge execution and consensus boot-node cron jobs#641
Conversation
Combine the two separate cron jobs that fetched execution and consensus node records into a single job. This reduces duplicated code, ensures both node types are always refreshed together, and allows the boot-node list to be updated atomically.
Savid
approved these changes
Sep 1, 2025
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
2 participants
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.
The discovery component had two separate cron jobs that were competing to update the same DiscV5 instance with different boot nodes:
Both jobs ran on the same schedule, causing a race condition where the consensus job would overwrite the execution boot nodes (or vice versa). This meant DiscV5 was only ever using boot nodes from one type of network at a time.