specs
specs copied to clipboard
Adds a new legacy section and moves the L2 Output Oracle spec into the new section. Replaces current Proposals doc with a temporary pointer to the fault proofs doc.
**Description** Glossary was stating that the default Sequencer Window Size was measured in "epochs" instead of blocks **Tests** N/A **Additional context** N/A **Metadata** N/A
The idea of specifying a wildcard event-index, to defer the exact connection to initiating-event to the sequencer, was drafted here: https://github.com/ethereum-optimism/specs/pull/108 This needs to be updated to account for executing-messages...
There is at least one example here: https://github.com/ethereum-optimism/specs/blob/dfa8ea9568b0e35827be763fa8e6a2eeb9d90704/specs/protocol/configurability.md?plain=1#L55C1-L56C1 The L2OutputOracle is not used in Fault Proof systems, and standard chains must be on Fault Proofs. I think in this case...
I think the second and third sentences of this paragraph is incorrect. https://github.com/ethereum-optimism/specs/blob/8efc7a3fe800367bb8f407ab4fe284570a18ebc9/specs/protocol/messengers.md?plain=1#L73-L80 It should read: > When going into L2 from L1, the user does not need to call...
**Is your feature request related to a problem? Please describe.** When it comes to updating the L2, the `L1Block` is regularly called to update its' state values, including the L1...
 The diagram describes how L2 blocks are derived from L1 blocks.I am puzzled about B1 in the diagram. Does 'B1' here stand for batch data? It seems in the...
Alt da servers (I.e, generic commitment types) are expected to encode the type byte prefix as per the server side generated commitment for the client to decode when querying. Additionally...
@benjaminion mentioned that this [MIP.sol](https://docs.optimism.io/stack/protocol/fault-proofs/mips) page in the docs might be better suited in the specs. The page can be cut down to the core specs parts and added. The...
The OP Stack is designed such that there is a [single batcher key](https://github.com/ethereum-optimism/optimism/blob/c4226bf4a809006adaa7087477db466e2eda2030/packages/contracts-bedrock/src/L1/SystemConfig.sol#L104) in the L1 `SystemConfig` contract. This EOA is controlled by the [op-batcher](https://github.com/ethereum-optimism/optimism/tree/develop/op-batcher), which is responsible for publishing...