Chaindrop

If you're running an OP-stack L3 and facing issues with block finalization/reorgs, this might be helpful: https://github.com/ethereum-optimism/optimism/issues/10380

We ran into this problem with one of our customers' chain at /chaindrop and solved it by increasing the finalityLookback value...

op-node assumes a finalization event will happen on the parent chain every 4 * 32 blocks (or sooner), but on an L2 it can take much longer depending on block time & batch submission frequency. As a result....

@mrmemes.eth and I spent hours trying to diagnose the issue and deploying various configurations in a test environment. We finally fixed it by multiplying finalityLookback by 6 (Base is 6 times faster than eth mainnet):

@mrmemes.eth and I spent hours trying to diagnose the issue and deploying various configurations in a test environment. We finally fixed it by multiplying finalityLookback by 6 (Base is 6 times faster than eth mainnet): https://github.com/JoinOrigami/celestia-optimism/commit/6bc5e4fe144c61091d9f1d4f49f50d95e9625fec

- L3 nodes are unable to finalize blocks.
- If op-proposer runs without ALLOW_NON_FINALIZED=false (default), output roots don't get submitted, i.e. withdrawals are blocked
- Restarting op-node will reset the derivation pipeline, and since finazlied block isn't updating it can take a while