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

Deployment tests: trivial deployments #1600

Open
4 of 9 tasks
OlivierBBB opened this issue Dec 2, 2024 · 0 comments · May be fixed by #1572
Open
4 of 9 tasks

Deployment tests: trivial deployments #1600

OlivierBBB opened this issue Dec 2, 2024 · 0 comments · May be fixed by #1572

Comments

@OlivierBBB
Copy link
Collaborator

Definitions

Trivial CREATE's are those CREATE's that are

  • unexceptional
  • don't abort
  • don't raise the failure condition F
  • but deploy with empty initialization code

Parameters

In terms of the parameters we can play with we find:

  • level
    • root level
    • higher level
  • CREATE vs CREATE2
  • zero value vs nonzero value
  • WILL_REVERT vs WONT_REVERT
  • zero size
    • 'zero size, huge offset' shenanigans
  • nonzero size

We could also consider collisions via CREATE2 or through multi transactions and SELFDESTRUCT's.
This will be the focus of other tests. We should also measure the interaction that these trivial deployments have with EXTCODEHASH.
Furthermore, we should see how these deployments squash any return data (if present.) And then there is obviously the question of deployment numbers, deployment statuses.

  • EXTCODEHASH before and after
  • squashing of return data and RETURNDATASIZE
  • warmth post deployment (EXTCODEXXX + BALANCE + CALL's + SELFDESTRUCT heir + ...)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants