Commit 35499637 authored by mergify[bot]'s avatar mergify[bot] Committed by GitHub

Merge pull request #3696 from ethereum-optimism/jg/docs

specs: Remove outdated portions
parents be1cb549 97b0d79b
...@@ -299,9 +299,8 @@ Batcher transactions are encoded as `version_byte ++ rollup_payload` (where `++` ...@@ -299,9 +299,8 @@ Batcher transactions are encoded as `version_byte ++ rollup_payload` (where `++`
| 0 | `frame ...` (one or more frames, concatenated) | | 0 | `frame ...` (one or more frames, concatenated) |
Unknown versions make the batcher transaction invalid (it must be ignored by the rollup node). Unknown versions make the batcher transaction invalid (it must be ignored by the rollup node).
All frames in a batcher transaction must be parseable. If any one frame fails to parse, the all frames in the
The `rollup_payload` may be right-padded with 0s, which will be ignored. It's allowed for them to be transaction are rejected.
interpreted as frames for channel 0, which must always be ignored.
> **TODO** specify batcher authentication (i.e. where do we store / make available the public keys of authorize batcher > **TODO** specify batcher authentication (i.e. where do we store / make available the public keys of authorize batcher
> signers) > signers)
......
...@@ -101,6 +101,11 @@ The `noTxPool` is optional as well, and extends the `transactions` meaning: ...@@ -101,6 +101,11 @@ The `noTxPool` is optional as well, and extends the `transactions` meaning:
into the payload, after any of the `transactions`. This is the default behavior a L1 node implements. into the payload, after any of the `transactions`. This is the default behavior a L1 node implements.
- If `true`, the execution engine must not change anything about the given list of `transactions`. - If `true`, the execution engine must not change anything about the given list of `transactions`.
If the `transactions` field is present, the engine must execute the transactions in order and return `STATUS_INVALID`
if there is an error processing the transactions. It must return `STATUS_VALID` if all of the transactions could
be executed without error. **Note**: The state transition rules have been modified such that deposits will never fail
so if `engine_forkchoiceUpdatedV1` returns `STATUS_INVALID` it is because a batched transaction is invalid.
[rollup-driver]: rollup-node.md [rollup-driver]: rollup-node.md
### `engine_newPayloadV1` ### `engine_newPayloadV1`
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment