Probabilistic Finality Reorgs in Bor Layer Consensus

Transaction Reversion Prior to Ethereum Checkpointing

Polygon's architecture separates transaction execution on the Bor layer from validator coordination on the Heimdall layer. While the Bor layer provides rapid block production, state finality is only absolute once a checkpoint is successfully submitted and confirmed on the Ethereum mainnet.

In high-congestion scenarios or during validator synchronization issues, the network may experience chain reorganizations. This behavior can result in transactions being reverted if the chain shifts to a longer valid branch before the current state is anchored to Ethereum.

Given the probabilistic nature of finality between checkpoints, what is the optimal confirmation threshold for high-value transactions to mitigate reorg risk? How does the system handle block production timeouts when a proposer fails to submit within the allotted slot time?