Add CFI EIPs #447
Add CFI EIPs #447
Conversation
Signed-off-by: Tim Beiko <[email protected]>
|
|
||
| * [EIP-3540: EVM Object Format (EOF) v1](https://eips.ethereum.org/EIPS/eip-3540) | ||
| * [EIP-3670: EOF - Code Validation](https://eips.ethereum.org/EIPS/eip-3670) | ||
| * [EIP-3860: Limit and meter initcode](https://eips.ethereum.org/EIPS/eip-3860) | ||
|
|
There was a problem hiding this comment.
I think also 3855 was part of that, at least some client devs referred to it, but would need to listen to the recording for confirmation.
There was a problem hiding this comment.
Right, I am actually unclear about this one.
There was a problem hiding this comment.
@holiman @MariusVanDerWijden @tkstanczak @yperbasis @shemnon @garyschulte if we could get a 👍 / 👎 from each of your teams on including PUSH0, it'd be helpful so we don't have to wait until the next call.
If you feel like we need more discussion before making a call, that's fine too. Just signal it here and we can merge these 3 and cover PUSH0 next ACD.
There was a problem hiding this comment.
👍 Implementing PUSH0 is easy, the harder (but still easy) part is ensuring it doesn't leak into pre-Shanghai execution (a well trodden path with ops like chainid).
The real work is in reference tests and upstream use by solidity and friends.
That extends to all EVM work, good reference tests are more work than client implementations typically.
There was a problem hiding this comment.
For the record, Ipsilon has tests for most of these EIPs (not for 3670 yet): https://github.com/ethereum/tests/pulls/gumb0
There was a problem hiding this comment.
👍 for EIP-3855 from besu mainnet team also
There was a problem hiding this comment.
Thanks all for the rapid responses! Will add and merge.
Signed-off-by: Tim Beiko <[email protected]>
On ACD131, we agreed to move EIPs 3540, 3670 and 3860 to CFI.