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

Deliberate Failure Condition F triggering with CREATE2 #1087

Open
OlivierBBB opened this issue Sep 4, 2024 · 0 comments
Open

Deliberate Failure Condition F triggering with CREATE2 #1087

OlivierBBB opened this issue Sep 4, 2024 · 0 comments
Assignees
Labels

Comments

@OlivierBBB
Copy link
Collaborator

OlivierBBB commented Sep 4, 2024

Failure condition F

image

The first line is triggered at the onset of the CREATE(2). The other stuff is only visible at the end of the deployment.

Test scenarios

We should write the following tests:

# Recursive CREATE2
Contract A does a CREATE2
    contract B starts deploying
    running the initialization code of B leads to Calling A
        A (attempts to) re-execute the same CREATE2

and

# Sequential CREATE2
Contract A does a CREATE2
    contract B starts deploying and deploys successfully
contract A resumes execution
contract A attempts the same deployment again (and fails with failure condition F)

Purpose

We could have two contracts recursiveCreate2TriggeringFailureCondition and sequentialCreate2TriggeringFailureCondition that become part of the framework.

Part of this is tested in arithmetization/src/test/java/net/consensys/linea/zktracer/instructionprocessing/createTests/failure/.

@OlivierBBB OlivierBBB changed the title Deliberate Failure Condition F triggering Deliberate Failure Condition F triggering with CREATE2 Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants