Hardhat and foundry, contract bytecode different

Question

I'm developing a contract in hardhat project. But now I want to write test by foundry. My problem is I'm using create2, but when running contract by hardhat and foundry they gave different addresses. I found the reason is the bytecode of contract from hardhat and foundry are different (10 ~ 20 bytes close the end). Here is my hardhat config + foundry toml.

hardhat.config.js

 config = {
  solidity: {
    version: "0.8.18",
    evmVersion: "london",
    settings: {
      optimizer: {
        enabled: true,
        runs: 200,
      },
    },
  },
...
}

foundry.toml

evm_version = 'london'
optimizer = true
optimizer_runs = 200
solc_version = '0.8.18'
via_ir = false

This is how they different, they have the same length, but different near the end What reasons affect to bytecode?

Answer 1

Foundry CREATE2 setup

this is what's happening when you CREATE2 from a script root:

    // Prepare CREATE2 Deployer
    let addr = Address::from_str("0x4e59b44847b379578588920ca78fbf26c0b4956c").unwrap();
    let code = hex::decode("7fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffe03601600081602082378035828234f58015156039578182fd5b8082525050506014600cf3").expect("Could not decode create2 deployer init_code").into();
    api.anvil_set_code(addr, code).await.unwrap();

Byecode Hash Output configuration settings

Foundry related Solidity compiler configs that can change bytecode hash output also include (besides optimizer runs and optimization settings/viaIR):

# {@see {@link https://github.com/foundry-rs/foundry/issues/4060} }
auto_detect_remappings = false
# Whether to store the referenced sources in the metadata as literal data. Helps with verification
use_literal_content = true
# The metadata hash is machine dependent. By default, this is set to none to allow for deterministic code.
# {@see {@link https://docs.soliditylang.org/en/latest/metadata.html} }
bytecode_hash = "none"
cbor_metadata = false
# Only the required contracts/files will be selected to be included in solc's output selection.
sparse_mode = true
ast = false
isolate = false
create2_library_salt = "0x0000000000000000000000000000000000000000000000000000000000000000"
prague = false
unchecked_cheatcode_artifacts = false

Customizing CREATE2 in Foundry

You cannot currently customize the foundry CREATE2 factory, see my issue on GitHub for the ongoing discussion: https://github.com/foundry-rs/foundry/issues/2638

Foundry cross-posted Issue

Additionally, this issue was reposted on GitHub and answered and closed: https://github.com/foundry-rs/foundry/issues/5559#issuecomment-1673454231