ethereum-optimism / ethereum-optimism/specs
"Standard config" spec should not reference pre-fault-proofs contracts
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 178
- Forks
- 205
- Avg merge
- 5d 2h
- Merged PRs (30d)
- 6
Description
There is at least one example here:
The L2OutputOracle is not used in Fault Proof systems, and standard chains must be on Fault Proofs.
I think in this case the parameter is defined off-chain in the rollup config.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read specs/protocol/configurability.md around lines 55-56 and compare the standard config example with the statement that L2OutputOracle is not used in Fault Proof systems. Verify how the parameter is defined for standard chains; done means the example no longer references pre-fault-proof contracts and reflects the correct configuration source.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100