Why this dashboard exists
Gnosis Chain canonical bridges are integrating the fast confirmation rule as a block processing rule, allowing bridging time to be much faster. This dashboard serves as public information and for monitoring.
It watches whether any block confirmed under the fast confirmation rule is later reorged out — the failure mode that faster bridging depends on not happening.
Links
- Fast confirmation rule documentation docs.gnosischain.com
- Gnosis Chain bridge bridge.gnosischain.com — to bridge
- EEZ eez.io — Ethereum Economic Zone
Alert cases explained
The fast confirmation rule keeps a pointer at the most recent block it is willing to
call confirmed — that pointer is what the execution client reports as its
safe block. It moves forward as confidence grows, and it is designed
to fall back to the last finalized block whenever it cannot stand behind its earlier
claim. A backwards move is therefore normal and not on its own a problem. Only one
thing is: a block that was confirmed and then left the chain.
Confirmation advances
no recordThe ordinary state. Every slot the rule confirms a little more of the chain and the safe pointer creeps toward the head, normally staying one or two slots behind it. Nothing is recorded.
Confirmation holds still
no recordNot enough attestations have landed for the rule to be sure about the next block, so the safe pointer stays put while the head moves on. Harmless by itself — but if it lasts about an epoch it turns into case D.
Confirmation re-anchors forward
no recordAt an epoch boundary the rule can re-anchor onto the freshly justified checkpoint, which is ahead of where it was stuck. The safe pointer jumps forward. This move is always forward, never back.
Stale, so it falls back
recorded, no alertThe rule confirmed nothing for more than an epoch, so it gives up its position and returns to the last finalized block. Every block it had confirmed is still on the chain — only the claim about them was withdrawn. This is case B left running.
A confirmed block is reorged out
alertsThe chain switched to a different branch and took a block the rule had already confirmed with it. That block is gone. This is the failure the dashboard exists to catch, and the only case here that pages.
Confirmation cannot be re-proved
recorded, no alertAt each epoch boundary the rule re-checks its earlier conclusion against the new validator set and balances. If the support behind any block it had confirmed no longer clears the safety margin, it withdraws to the finalized block. The blocks are still on the chain; only the confidence in them changed.
The confirmed block is no longer known
alertsFinality advanced along a branch that did not contain the block the rule had confirmed, so that block was dropped from the fork tree altogether. This almost always means a confirmed block was lost; the dashboard treats it as case E once the finalization check corroborates it.