[Core Protocol] Need to add L1 confirmation checker. #95
-
Issue DescriptionOn Arbitrum , there's a useful service: L1 confirmation checker. Here's an important use case: Additional InformationNo response |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 1 reply
-
That is a helpful tool! I'm not aware of a similar one we have at the moment. The root of what you're looking for is the different block tags (
This is information I gathered from our specs. So to get the behavior you're looking for, you can check what block the transaction is in and then compare that against the block tags. |
Beta Was this translation helpful? Give feedback.
-
Thanks @sbvegan , Will Optimism official team develop such service? Or I need to develop it myself? |
Beta Was this translation helpful? Give feedback.
-
Got it, thank you @sbvegan |
Beta Was this translation helpful? Give feedback.
-
Hey @maodaishan, We hope your recent question was resolved to your satisfaction. Your feedback is invaluable and helps us improve our support services. Could you spare a moment to fill out a short feedback survey. Thank you for helping us improve our developer community. |
Beta Was this translation helpful? Give feedback.
That is a helpful tool! I'm not aware of a similar one we have at the moment. The root of what you're looking for is the different block tags (
safe
,unsafe
, andfinalized
).safe
means all of the data to derive a L2 block has been included on L1.safe
blocks only reorg if L1 reorg happens.unsafe
means all of the data to derive a L2 block has been included on L1.unsafe
blocks can reorg if the L1 reorgs or there was an issue sequencer.finalized
means all of the data to derive a L2 block has been finalized on L1. No finalized block can be reorged.This is information I gathered from our specs.
So to get the behavior you're looking for, you can check what block the transaction is in and t…