Giters

0xFableOrg / roll-op

The simplest way to spin your own dev / prod rollup, fully configurable.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Make roll-op fully functional on testnets

norswap opened this issue · comments

commented

Right now we have at least one issue: the proposer never proposes.

This also happens locally when the proposer --allow-non-finalized flag is false (the default).
Locally, this probably happens because we use a clique L1 whose RPC never marks blocks as finalized.

On testnets (I tried Goerli), blocks should finalize, so it's unclear what the issue is.

Ideas:

  • spin a PoS L1 node so we can investigate locally more easily
  • try playing with the --l1-rpc-kind of the L2 node to see if it changes anything.
commented

So, the issue had nothing to do with allow-non-finalized. I was using goerli as a deployment name for the goerli deployment and that caused the script to reuse the existing (bundled in with the monorepo) Goerli deploy config file, along with incorrect chain ID etc.

A clue (besides the incorrect chain ID...) was that the op-node didn't sync properly (it never showed "found next batch" in its logs).