Skip to content
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

Update EIP-4762: unconditionnal account write during contract init #8867

Merged
merged 1 commit into from
Sep 10, 2024

Conversation

gballet
Copy link
Member

@gballet gballet commented Sep 6, 2024

In the current state of the spec, there are a few instances where the basic leaf can be created but not the code hash leaf.

This unconditionally write-touch all leaves upon contract initialization, as this will result in an account no matter what happens. The only difference is that the value of the code hash will either be the hash of the contract code, or the empty hash, but that does not impact the gas costs.

@github-actions github-actions bot added c-update Modifies an existing proposal s-draft This EIP is a Draft t-core labels Sep 6, 2024
@eth-bot
Copy link
Collaborator

eth-bot commented Sep 6, 2024

🛑 Auto merge failed. Please see logs for more details, and report this issue at the eip-review-bot repository.

@eth-bot eth-bot changed the title eip4762: unconditionnal account write during contract init Update EIP-4762: unconditionnal account write during contract init Sep 6, 2024
@eth-bot eth-bot enabled auto-merge (squash) September 6, 2024 12:59
Copy link
Collaborator

@eth-bot eth-bot left a 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...

@gballet gballet marked this pull request as draft September 6, 2024 13:04
auto-merge was automatically disabled September 6, 2024 13:04

Pull request was converted to draft

@@ -132,11 +132,6 @@ When a contract creation is initialized, process these write events:

```
(contract_address, 0, BASIC_DATA_LEAF_KEY)
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if "creation is initialized" is well defined. As in: after collision check.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thinking the same thing, also we should clarify the TouchAndChargeContractCreateCheck change that was done in geth. It is not obvious and may result in a few errors in implementation?

Copy link
Contributor

@g11tech g11tech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@tanishqjasoria
Copy link

lgtm

@gballet gballet marked this pull request as ready for review September 10, 2024 09:56
@lu-pinto
Copy link

lgtm too - we were already doing this in a way

@g11tech g11tech merged commit 05e03f5 into ethereum:master Sep 10, 2024
25 of 26 checks passed
holiman pushed a commit to ethereum/go-ethereum that referenced this pull request Sep 13, 2024
Implementation of [this EIP-4762
update](ethereum/EIPs#8867).

---------

Signed-off-by: Guillaume Ballet <3272758+gballet@users.noreply.github.com>
Co-authored-by: Tanishq Jasoria <jasoriatanishq@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c-update Modifies an existing proposal s-draft This EIP is a Draft t-core
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants