Synchronization lag between Bor execution and Heimdall consensus layers

Bor and Heimdall Coordination

The Polygon PoS architecture relies on the Bor client for block production and the Heimdall layer for validator coordination and state truth. Under conditions of high network congestion, a synchronization lag can occur between these two layers.

Consistency Constraints

When the Bor execution layer falls behind the Heimdall consensus layer, the timing of block proposals and the validation of the current validator set may become decoupled. This creates uncertainty regarding how the Bor client handles block production when the underlying coordination layer has progressed beyond the execution state.

• Version assumption: Current Bor/Heimdall stable releases.
• Constraint: High transaction throughput leading to increased block processing time.

Does the Bor client implement a specific timeout or fallback mechanism to reconcile state when the Heimdall layer is significantly ahead? How is the impact of this lag measured against the risk of validator slashing for uptime failures?