Update EVM Tests to Support Cancun about plonky2 HOT 5 OPEN

This should be fairly simple, starting from 0xPolygonZero/evm-tests#37 we will just have to update the target/filters from Shanghai to Cancun.

from plonky2.

This should be fairly simple, starting from 0xPolygonZero/evm-tests#37 we will just have to update the target/filters from Shanghai to Cancun.

We should do this on the feat/cancun branch so CI on that runs against Cancun.

from plonky2.

I'm not sure I understand. Do you want to run the CI against ALL Cancun related tests? (That's a lot, i.e. several days of compute, probably several hours if we select only the Cancun folder).

Or do you want to have a few selected tests from each EIP in serialized format (cf. https://github.com/topos-protocol/evm-tests-suite-parsed) and test against those within a new local integration test?

from plonky2.

from plonky2.

Another approach to this (on the plonky2 side, as we would still want to update the test runner at some point), would be to have unit tests with the official test vectors for each of these new opcodes.
For now they have only been tested externally through the test-runner.

from plonky2.