[OP Stack Deployment] L2OutputOracleProxy.latestBlockNumber()(uint256) is stuck #695
Replies: 2 comments 1 reply
-
|
Analysis.
So, not a reorg problem
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Progress
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Did you check the documentation?
Did you check for duplicate questions?
Issue Description
Op stack version:
v1.9.1without alt-daSmart Contract version:
beta.1Status: Successfully tested deposits and withdrawals, and working well for a while.
Block time:
1 secSettlement layer:
Base SepoliaEverything was functioning smoothly for weeks, but recently the op-proposer has become stuck while attempting to update the
L2OutputOracleProxy.latestBlockNumber()(uint256).The system is generating extensive logs similar to the following:
The last transaction occurred two days ago (view on Sepolia BaseScan), and there is no clear indication of the cause, as other logs do not show any issues.
We need to understand how to generally debug this situation and determine how to resolve it.
Logs
sync-status
op-proposer
op-batcher . Also batcher works fine because we can see result here https://sepolia.basescan.org/address/0x256DE50807FDf545d5D311e1a8932C6AB8489Da8
op-node
Full log:
pm2_logs_op-node (1).txt
op-geth
Additional Information
we have restarted the op-node to let it traverse the history and may resolve this issue
Feedback
No response
Beta Was this translation helpful? Give feedback.
All reactions