feat: Canyon hardfork behind optimism feature flag

[clabby]

Overview

Adds the Canyon hardfork behind the optimism feature flag, and adds a macro to define the SpecId enum to separate the ordering of hardforks between L1 and optimism.

The Canyon hardfork does not implement any EVM changes, though it does implicitly enable Shanghai.

More information about Canyon can be found in the upstream tracking issue: ethereum-optimism/optimism#7452

[rakita]

I like the idea of having a separate SpecId structure, but it isn't best to wrap it inside macro.

You could do:

        /// Specification IDs and their activation block.
        /// 
        /// See: [Ethereum Execution Specs](https://github.com/ethereum/execution-specs)
        #[cfg(feature = "optimism")]
        #[repr(u8)]
        #[derive(Debug, Copy, Clone, PartialEq, Eq, Hash, Ord, PartialOrd, enumn::N)]
        #[cfg_attr(feature = "serde", derive(serde::Serialize, serde::Deserialize))]
        pub enum SpecId {
            ...
        }

[clabby]

Pulled it back out

[rakita]

nice!

[rakita]

Just to note here, I created this change on the top of the 1609e07 commit. This "parent" commit is used inside reth and the idea is to freeze revm as there are some breaking revm changes so it would be less painful.