-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add EIP: Delayed execution #9376
Conversation
✅ All reviewers have approved. |
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
d4ced7b
to
ce96421
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
very cool. would also be great to see in the consideration section what potential challenges there are with increasing the delay window (coinbase balance decrease and gas limit are two that immediately come to mind)
|
||
## 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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one unmentioned consideration here is that this will require EL clients to bring back or introduce signer management for local payload building
|
||
#### Coinbase signature over the header | ||
|
||
We include a signature from `COINBASE` over the rest of the header in the header , so that the `COINBASE` address can authorize the upfront payment of inclusion costs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We include a signature from `COINBASE` over the rest of the header in the header , so that the `COINBASE` address can authorize the upfront payment of inclusion costs. | |
We include a signature from `COINBASE` over the rest of the header in the header, so that the `COINBASE` address can authorize the upfront payment of inclusion costs. |
|
||
We include a signature from `COINBASE` over the rest of the header in the header , so that the `COINBASE` address can authorize the upfront payment of inclusion costs. | ||
|
||
The final header structure then is: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The final header structure then is: | |
The final header structure is then: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All Reviewers Have Approved; Performing Automatic Merge...
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