[OP Stack Deployment] <Testnet rollup errors with batcher and proposer>

[Ezra-Labs]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

Running my own rollup according to tutorial, am seeing two distinct types of errors showing up.

The first, in op-batcher:

WARN [01-25|18:24:25.497] nonce too low service=batcher tx=3758f0..4f748a nonce=394 gasTipCap=4,641,005 gasFeeCap=223,000,949 gasLimit=292,144 err="nonce too low: next nonce 395, tx nonce 394"

I am also seeing a nonce issue error on the Alchemy dashboard.

Second type of errors showing up, in op-proposer, typically look something like this:

WARN [01-25|18:26:03.336] Failed to create a transaction, will retry service=proposer err="failed to estimate gas: execution reverted: L2OutputOracle: block hash does not match the hash at the expected height"
WARN [01-25|18:26:05.924] Failed to create a transaction, will retry service=proposer err="failed to estimate gas: execution reverted: L2OutputOracle: block hash does not match the hash at the expected height"
WARN [01-25|18:26:08.808] Failed to create a transaction, will retry service=proposer err="failed to estimate gas: execution reverted: L2OutputOracle: block hash does not match the hash at the expected height"
ERROR[01-25|18:26:08.808] Failed to send proposal transaction err="failed to create the tx: operation failed permanently after 30 attempts: failed to estimate gas: execution reverted: L2OutputOracle: block hash does not match the hash at the expected height" l1blocknum=5,112,070 l1blockhash=6c3576..487595 l1head=5,154,820

Any ideas how to correct this? I noticed the problem did not happen during the first time initializing, but now happens every time.

Logs

WARN [01-25|18:24:25.497] nonce too low service=batcher tx=3758f0..4f748a nonce=394 gasTipCap=4,641,005 gasFeeCap=223,000,949 gasLimit=292,144 err="nonce too low: next nonce 395, tx nonce 394"

WARN [01-25|18:26:03.336] Failed to create a transaction, will retry service=proposer err="failed to estimate gas: execution reverted: L2OutputOracle: block hash does not match the hash at the expected height"
WARN [01-25|18:26:05.924] Failed to create a transaction, will retry service=proposer err="failed to estimate gas: execution reverted: L2OutputOracle: block hash does not match the hash at the expected height"
WARN [01-25|18:26:08.808] Failed to create a transaction, will retry service=proposer err="failed to estimate gas: execution reverted: L2OutputOracle: block hash does not match the hash at the expected height"
ERROR[01-25|18:26:08.808] Failed to send proposal transaction err="failed to create the tx: operation failed permanently after 30 attempts: failed to estimate gas: execution reverted: L2OutputOracle: block hash does not match the hash at the expected height" l1blocknum=5,112,070 l1blockhash=6c3576..487595 l1head=5,154,820

Additional Information

No response

Feedback

No response

[opfocus]

maybe because your op-node is not yet synchronized up to the present time. Just wait until it is.

[Ezra-Labs]

ERROR[01-26|20:03:55.368] Failed to send proposal transaction err="failed to create the tx: operation failed permanently after 30 attempts: failed to estimate gas: execution reverted: L2OutputOracle: block hash does not match the hash at the expected height" l1blocknum=5,113,593 l1blockhash=1ef68c..0647c6 l1head=5,161,659

Noting the difference between l1head and l1blocknum, the difference is shrinking, though very very slowly. For sure this did not happen during first time starting everything up. Is there a cause I should know about and is there a way to shorten the time?

[opfocus]

Generally speaking, restarting op-geth and op-node will delay time. The fastest way is to quickly start op-geth and op-node after building op stack rollup, and then start batcher and proposer.

[Ezra-Labs]

Noted. I appreciate the responses, this is all new to me. Is there a way for a cloud-based deployment of the OP stack on Sepolia?

[sbvegan]

Yes. If you've done it locally, you can do it on the cloud as well. If you have a specific additional question, please open a new thread with the details and we'll do our best to help :)

[Ezra-Labs]

Yes, thanks so much, will do. I am very appreciative of your response!

[github-actions[bot]]

Hey @Ezra-Labs, 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.