Skip to content

meta: make Foundry ready for Fusaka #11428

@zerosnacks

Description

@zerosnacks

Related to: #11348

Most of this is handled by Revm but we need to make sure the integration points are also ready

  • https://eips.ethereum.org/EIPS/eip-7892, make sure codebase adheres to the BPO hardforks, ref: feat: add bpos alloy-rs/hardforks#40. Can be handled by updating
    /// Derive the blob base fee update fraction based on the chain and timestamp by checking the
    /// hardfork.
    pub fn get_blob_base_fee_update_fraction(chain_id: ChainId, timestamp: u64) -> u64 {
    let hardfork = EthereumHardfork::from_chain_and_timestamp(Chain::from_id(chain_id), timestamp)
    .unwrap_or_default();
    if hardfork >= EthereumHardfork::Prague {
    BLOB_BASE_FEE_UPDATE_FRACTION_PRAGUE
    } else {
    BLOB_BASE_FEE_UPDATE_FRACTION_CANCUN
    }
    }
    /// Returns the blob base fee update fraction based on the spec id.
    pub fn get_blob_base_fee_update_fraction_by_spec_id(spec: SpecId) -> u64 {
    if spec >= SpecId::PRAGUE {
    BLOB_BASE_FEE_UPDATE_FRACTION_PRAGUE
    } else {
    BLOB_BASE_FEE_UPDATE_FRACTION_CANCUN
    }
    }
    .

No updates further required, update was handled in https://github.com/foundry-rs/foundry/pull/11477/files

Ideally we have a way to run the same test suite easily against a range of EVM versions (such as the repro's and cheat suites): #11436

This can be handled when the Osaka migration actually occurs, it is currently a big hassle to change the default in a revm patch as all dep crates need patches too.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

Status

Ready For Review

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions