Remove EOF from Shanghai Spec #676
Conversation
Signed-off-by: Tim Beiko <t.beiko23@gmail.com>
|
Shall we move them to Cancun CFI instead? |
|
@shemnon asked the same thing in the R&D discord. Happy to make that change if Geth + Nethermind also +1 :-) |
|
Would also support moving to Cancun CFI, I guess this will help that the topic stays on the table in a sufficient manner and also helps to serve as a reminder to continuously evolve thoughts on the topic and have necessary in-between discussions and decisions so that we hopefully get to a consistent and holistic plan on this incuding some long-term thinking throughout the months without the need for some last-minute rush where things run the risk to fall under the table. |
|
Merged as-is because other changes are blocked on it. Added an agenda item about Cancun CFI to the next ACD (ethereum/pm#704) given we couldn't get everyone to agree async here. |
…ainer kinds (ethereum#676) * fix(tests): Fix invalid EOF container combos test Make sure the case is invalid only for one reason. * new(tests): Add more cases for invalid subcontainer kind combos * new(tests): Add test for valid subcontainer kinds on a deeper nesting level * new(tests): Add test for valid subcontainer kinds in a non-first code section * Update changelog
…ainer kinds (ethereum#676) * fix(tests): Fix invalid EOF container combos test Make sure the case is invalid only for one reason. * new(tests): Add more cases for invalid subcontainer kind combos * new(tests): Add test for valid subcontainer kinds on a deeper nesting level * new(tests): Add test for valid subcontainer kinds in a non-first code section * Update changelog
Decided on ACD#152