norswap
norswap
cf. [this comment](https://github.com/ethereum-optimism/optimistic-specs/pull/223/files/6ce85c622da6b4015a18721fb8fa9ff19628d1b0#r823879894) Essentially, make the explanation a bit nicer.
Our execution engine implementation is at https://github.com/ethereum-optimism/reference-optimistic-geth/ (I would like to rename this repository. Possible to `execution-engine`. Is that okay? If so, I'll open another issue to track.) We need...
cf. https://github.com/ethereum-optimism/optimistic-specs/issues/141 for the general idea The downloader is the other piece of the implementation (besides sync) that is more tricky, so it would be good to have a written...
We should have some kind of writing markdown artifact that explains the sync algorithm in-practice. This can be separate from "the specification" — to specify the correct behaviour we do...
We should specify the contents of the genesis block somewhere (probably in the execution engine specification), and link to the json file used in the reference implementation. Mainly,` we need...
cf. https://github.com/ethereum-optimism/optimistic-specs/issues/141 for the general idea We should have a general overview of the different components of the implementation written up.
Making this a single milestone for now, but we might want to split it off. Each of those is its own smaller milestone, though there isn't enough details to really...
- The challenger agent is started by a verifier when he computes different output roots than the one the sequencer posted to L1. It is reponsible for playing the challenge...
I seem to recall that the memory available to the MIPS version of Cannon is limited (2GB? 4GB?). We should check this, and make sure it's not possible to craft...
Currently the code does not pass `go fmt`. We should ensure it does, then add that check to the CI. We should also do this in the minigeth repo.