Tony D’Addeo
@deodad
questions about OP Stack re-orgs: - can unsafe blocks be re-orged by the sequencer? - if so, how often are unsafe blocks re-orged? - in practice how many confirmations before block become safe? - is there a way to view historical re-orgs? - (bonus) what's the best way to detect a re-oreg?
4 replies
4 recasts
15 reactions
Roberto Bayardo 🎩
@bayardo.eth
Yes, unsafe blocks can potentially be reorged, but most deployments of OP Stack (e.g. Base's) try REALLY REALLY hard to avoid this in order to allow a tx receipt to be treated as an effective tx confirmation. So reorgs are extremely unlikely. I don't think Base has ever had one.
1 reply
0 recast
7 reactions
zain
@zain
Related to safe, you can see the data in seconds here by chain: https://dune.com/oplabspbc/op-stack-chains-l1-activity#submission-frequency
2 replies
0 recast
1 reaction
shazow
@shazow.eth
[Deleted my original cast as I'm thinking through it] My original intuition was that we shouldn't have to worry about reorgs with a single sequencer (ie. non-based rollups), but then I remembered that the L2 might have access to L1 state which would force it to re-interpret outcome based on reorgs. Thanks for asking this question, looking forward to reading more replies.
0 reply
0 recast
2 reactions
zain
@zain
One thing to add which seems to be missed in below discussion: L2s (unsafe and safe) data can still be reorged due to L1 reorgs. L2s outsource their consensus to L1, so until L1 is finalized, you cant have nonzero L2 finality. (sidebar this is why CCTP waits 16min for L2 cross chain sends)
1 reply
0 recast
1 reaction
