fix: keep FCU timestamps at or ahead of wall clock#180
Merged
Conversation
The previous 2-second threshold allowed timestamps to drift behind wall clock on slow CI runners, causing the builder to compute zero flashblocks and produce empty blocks. Use max(now, lastTimestamp) so timestamps never fall behind.
Collaborator
✅ Heimdall Review Status
|
wlawt
approved these changes
May 12, 2026
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
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.
Summary
max(now, lastTimestamp)so FCU timestamps never fall behind wall clockbasic-benchmarksCI flake where the builder sees "FCU arrived too late" on every block, produces empty blocks (0 flashblocks), and thetransferonlyworker times out waiting for a receiptRoot Cause
Each block cycle (FCU → build → getPayload → newPayload) takes slightly >1s of real time on slow CI runners. The timestamp increments by exactly 1s per block (
lastTimestamp + 1), so it gradually drifts behind wall clock. The builder'scalculate_flashblockssubtracts a leeway from the target timestamp, sees no remaining time, and builds 0 flashblocks — producing blocks with only the deposit tx and no pool transactions.The old 2-second guard never triggered because the per-block drift is <2s, but it accumulates over many blocks.