EIP7702 Test Ideas

[winsvega]

7702 thoughts:

• pointer to contract to pointer to contract loop
• pointer to pointer
• push pointer bytes to memory and try to create/create2/tx deploy (btw push eof bytes and create?)
• pointer to precompile/sys
• pointer to contract that revert/oog/suicide/return/errors with exception
• pointer to eof
• pointer to static, check static context activated
• static call to pointer to contract check static context is active
• same as above but with reentry to first contract
• contract with storage calls pointer to some contract, check storage modifications. Check tstore modificstions.
• same as above but with reentry check storage/tstorage and no loop (reentry stops)

More from Marius:

• Tests for 7702 with pre-deployed delegations that are not of the correct size (should never happen, but we should have tests for it)

[winsvega]

From @MariusVanDerWijden

• We should have a test for signature malleability in 7702
• Also 7702 will change the speed of extcodesize, we should test whether this will be a problem

We should have a test, where a contract calls a delegation that delegates to a delegation and we check the gas of that. In our gas calculation, we only check for the delegation prefix

So we should charge for the resoulution of the second delegation, even if the second delegation will fail. I'm wondering if there can be consensus issues there

same for extcodecopy, extcodesize, extcodehash