protolambda

Not a flake, looks like something changed in develop since the original changes here were made, and the same set of tests consistently fails. We'll need to investigate / resolve.

Rebased on latest `develop` and fixed the exit-error behavior covered by the test cases that @ajsutton commented about before the holidays.

Hmm, still seeing weird test failures in CI. Local debugging shows that it's the file-poller of cannon timing out on reading data from the op-program in server-mode. So I think...

Regarding Besu log index: see the errors in the screenshot in https://github.com/ethereum-optimism/developers/discussions/59#discussioncomment-7519611

@ajsutton that issue is a year old, it must have regressed, or the user wouldn't be able to sync the latest L1 chain with it.

Looks like this was fixed in Besu. Can we close this issue? @ajsutton

fixed in https://github.com/ethereum-optimism/optimism/pull/8235 and https://github.com/ethereum-optimism/optimism/pull/8040

The deploy config (the template that then becomes the config) has `finalizationPeriodSeconds: 2`, while the L1 time is 3s, and L2 time is 2s. The proposer is synchronously proposing and...

Ah yes, I had the wrong variable; `finalizationPeriodSeconds` configures how long it takes for an onchain output to become "final" (i.e. what would be 7 days in real networks). `l2OutputOracleSubmissionInterval`...

Keeping this PR open just to preserve the branch at this point, so I can look at it when experimenting with Cannon/Asterisc in new domains, soon hopefully, once higher priority...