Add EIP: Delayed execution #9376
Conversation
File
|
eth-bot
added
e-consensus
github-actions
bot
added
c-new
EIPS/eip-7886.md
Outdated
| ) | ||
| ``` | ||
|
|
||
| By signing over the header, the `COINBASE` address explicitly accepts responsibility for the upfront inclusion costs *of this block*. Therefore, the recovered address MUST equal the block's `COINBASE`. The `COINBASE`'s commitment is protected from replay attacks, because the header is a commitment to the block, so the signature only serves as an authorization for the exact block for which the `COINBASE` has agreed to take responsibility. |
There was a problem hiding this comment.
Little bit more rationale in here. I'm going to stop commenting on this; you get the idea.
EIPS/eip-7886.md
Outdated
|
|
||
| ### Static block validation | ||
|
|
||
| We split up a block's validation from its execution. In the ethereum/execution-specs, static validation is done in `validate_block`, after which a block is guaranteed to be valid and can be attested to, while execution remains within `apply_body`. In `validate_block`, we do some formal checks, as well as: |
There was a problem hiding this comment.
In the ethereum/execution-specs, static validation is done in
validate_block[...]
You should link explicitly to lines in a specific commit, in case things move around or are refactored in EELS.
EIPS/eip-7886.md
Outdated
|
|
||
| ### Block execution | ||
|
|
||
| This logic is implemented into the ethereum/execution-specs, in `apply_body`. |
There was a problem hiding this comment.
Again, specific link is preferred.
|
The commit a89b74d (as a parent of 37db202) contains errors. |
EIP-7623: Fix linter issues EIP-7623: Fix linter issues EIP-7623: Fix linter issues EIP-7623: Fix linter issues
nerolation
force-pushed
the
delayed-exec-eip
branch
from
d4ced7b to
ce96421
Compare
| class Header: | ||
| parent_hash: Hash32 | ||
| ommers_hash: Hash32 | ||
| coinbase: Address |
There was a problem hiding this comment.
should we exclude the coinbase from header?
| chain_id, | ||
| header.parent_hash, | ||
| header.ommers_hash, | ||
| header.coinbase, |
| The final header structure then is: | ||
|
|
||
| ```python | ||
| class Header: |
There was a problem hiding this comment.
Deferred comment on the field is a little bit confusing given that these parent_* fields are validated immediately
|
|
||
| ## Abstract | ||
|
|
||
| This proposal makes (execution) blocks statically verifiable through minimal checks that only require the previous state, but no execution of the block's transactions, allowing validators attest to a block's validity without completing its execution. We allow transactions to be skipped when invalid at execution time, without invalidating the whole block. To ensure that even skipped transactions pay for their resources, the `COINBASE` pays for all inclusion costs upfront (base cost, calldata and blobs), and recovers the costs only when transactions are successfully executed. |
There was a problem hiding this comment.
one unmentioned consideration here is that this will require EL clients to bring back or introduce signer management for local payload building
This PR proposes delayed execution as described in this ethresearch post:
https://ethresear.ch/t/delayed-execution-and-skipped-transactions/21677
Find Specs here:
ethereum/execution-specs@master...fradamt:execution-specs:delayed-exec-basic