Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
N
nebula
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
exchain
nebula
Commits
35499637
Unverified
Commit
35499637
authored
Oct 20, 2022
by
mergify[bot]
Committed by
GitHub
Oct 20, 2022
Browse files
Options
Browse Files
Download
Plain Diff
Merge pull request #3696 from ethereum-optimism/jg/docs
specs: Remove outdated portions
parents
be1cb549
97b0d79b
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
7 additions
and
3 deletions
+7
-3
derivation.md
specs/derivation.md
+2
-3
exec-engine.md
specs/exec-engine.md
+5
-0
No files found.
specs/derivation.md
View file @
35499637
...
@@ -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)
...
...
specs/exec-engine.md
View file @
35499637
...
@@ -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`
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment