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

Simple test where we revert multiple CALL's in succession #1172

Open
OlivierBBB opened this issue Sep 12, 2024 · 0 comments · May be fixed by #1775
Open

Simple test where we revert multiple CALL's in succession #1172

OlivierBBB opened this issue Sep 12, 2024 · 0 comments · May be fixed by #1775
Assignees
Labels

Comments

@OlivierBBB
Copy link
Collaborator

OlivierBBB commented Sep 12, 2024

Write a simple test like so

  • ROOT (which is B) performs successive CALL's to contracts
    • A with value 1
    • B with value 2 (selfcall)
    • A with value 3
    • C with value 4
    • B with value 5 (selfcall)
    • A with value 6
  • finish with a REVERT (optionally)

The next level of testing would have A be callable either with a simple transfer function or with a tipTheSender function where A performs a CALL to its caller address and gives back half the money it got i.e. half of the CALLVALUE.

Also the ROOT should have the option to use a sendAll method where it sends its entire balance. The target should be allowed to be any of the above.

Furthermore we want the choice between using normal CALL's and CALLCODE's.

Also, run the same test not from ROOT but from one level above ROOT twice in a row (in the same transaction, covering all 4 possibilities of reverting, e.g., first reverting and second not).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants