fix: disable custody backfill sync peer penalty for missing columns#48
Merged
eserilev merged 1 commit intoMay 21, 2026
Merged
Conversation
The custody backfill sync was penalizing peers with MidToleranceError for failing to serve columns. This causes false bans in Gloas (ePBS) where peers may not have columns available due to the block/envelope decoupling. Remove the penalty entirely - keep the debug log for visibility.
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.
Problem
The custody backfill sync penalizes peers with
MidToleranceErrorwhen they fail to serve columns ("Bad or missing columns for some slots"). In Gloas (ePBS), peers may legitimately not have columns available due to:This causes score decay and eventual bans in small devnets.
Fix
Remove the peer penalty entirely from the custody backfill sync path. Keep the debug log for visibility.
Testing
Tested on a 6-node Kurtosis devnet (2 Lighthouse, 2 Prysm, 2 Lodestar) with
gloas_fork_epoch: 1andpreset: minimal. Without this fix, Lodestar peers get penalized immediately at epoch 5. With this fix, the network runs for 80+ epochs with zero peer score degradation.