`ops-bedrock` and `ops` dockerized blockchains behave differently

[chrismin]

Describe the bug The dockerized Optimism + Ethereum in ops executes transactions, processes crosschain messages, etc. ASAP. The dockerized Optimism + Ethereum in ops-bedrock appears to introduce a delay more similar to the production blockchains.

How can we configure and adjust this delay?

To Reproduce Steps to reproduce the behavior:

1. Run the commands in the Makefile of ops
2. Run the commands in the Makefile at root of repo (to run ops-bedrock

Expected behavior ops and ops-bedrock produce comparable dockerized blockchains.

Screenshots If applicable, add screenshots to help explain your problem.

System Specs:

• OS: M1 macOS Monterey 12.2.1 (21D62)
• Package Version (or commit hash): commit hash 1f134ba1dc69201e2d0cf3b0921c580cfb9d7574

Additional context Add any other context about the problem here.

[tynes]

Bedrock has an assumption of consistent block production for L1. This makes it not possible to do just in time block production like what hardhat does. Perhaps you can fork the L1 node with hh/anvil if you want that kind of setup

[chrismin]

Got it, thank you!

For context, my goal is to speed up the execution of tests that involve crosschain message passing between L1 and Optimism. Beyond what you've written above, any suggestions on how to get crosschain message passing to run faster in local environments?

[tynes]

The devnet config for this is found here: https://github.com/ethereum-optimism/optimism/blob/46a7f1f08017c878751e7639b1d415997ff8bb65/packages/contracts-bedrock/deploy-config/devnetL1.json#L16

Perhaps try changing l1Blocktime to 2 and l2Blocktime to 1

It looks like the L1 blocktime is 3 seconds

[tynes]

Closing this as its a known thing