supernode: Clear Verifications and Denied Blocks on L1 Reorg #19245
Description
L1 consistency is currently handled two ways in the supernode:
- Virtual Nodes handle their L1 chain independently and will discover reorgs and react naturally
- Interop Activity watches the "CurrentL1" of all chains
But this is insufficient.
If the L1 reorgs, there are two groups of data which need to be pruned:
- denylist: previously denied blocks may become valid with new L1
- verification and logs: previously approved blocks may become invalid with new L1
During the consistency check phase, we need to detect L1 reorg and prune this data.
We should also consider who owns this signaling. If every Verification Activity did it on its own, this would be be very noisy. Maybe there should be an L1 watcher for activities...