[OP Stack Deployment] How to setup the proposer L2 output proposals interval (and batcher ) Using op-contracts(

[seromenho]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

I’m deploying an OP Stack chain using op-contracts/v1.8.0 and op-deployer/v0.0.13.
I’ve configured the op-proposer with the --proposal-interval flag, as per the official documentation, but it seems the flag is being ignored — the proposer continues submitting new proposals at a different interval.
I am looking for the equivalent of the old l2OutputOracleSubmissionIntervalused for the L2OO

Expected Behavior:
The proposer should only post a new L2 output to L1 once every --proposal-interval seconds.

Actual Behavior:
The op-proposer is currently creating a new dispute game (posting a new output root) approximately every 1.5 hours, despite the --proposal-interval being set to 86400 seconds (24 hours).

Thank you

Logs

No response

Additional Information

No response

Feedback

No response

[hash1go]

Could you please provide the entire configuration for op-proposer? (Feel free to mask sensitive information if necessary.)

[Chomtana]

Do you see "Duration since last game not past proposal interval" in the op-proposer log?

[seromenho]

I was playing with intervals less than 90 minutes, which wasn't working. But now I have tried with 2h and it's working. I am now testing 24h.
Why wouldn't proposal intervals less than 90 minutes work?

I'll report back after testing again.
Thank you

[opfocus]

That's a really good observation

[seromenho]

I have confirmed. Values smaller than 90 minutes don't work. Bigger than that works fine. Might be related to some other chain configurations?

[joohhnnn]

Hi, after going through the code, I didn’t find anything related to a 90-minute limit.
However, I can suggest an approach for deeper analysis: try adding logging during the ProposalInterval process to output the transaction hash of the createGame call after signing.
This way, you can determine whether the issue is with a component in ProposalInterval failing to send the transaction, or if the transaction is successfully sent but fails due to some on-chain contract settings.

[opfocus]

#789
Please pay attention to this discussion. It seems that the --proposal-interval configuration works in other versions. I guess it uses a version later than op-deployer/v0.3.0