Deploy multicall v3 in private chain with the same address. about multicall

[mds1]

You'll have to place the Multicall3 bytecode at the specified address manually, since you can't deploy it without the deployer's private key. I'm not sure of the specifics of your chain, but something like anvil, hardhat, or tenderly all support this

[noyyyy]

You'll have to place the Multicall3 bytecode at the specified address manually, since you can't deploy it without the deployer's private key. I'm not sure of the specifics of your chain, but something like anvil, hardhat, or tenderly all support this

Got it. Suppose a tool contract is deployed with the create2 factory. Different developers can deploy it with the same address and don't have to control the same private key. For Multicall3, I have to get another address on a private chain.

[mds1]

A create2 factory wasn't used here because there is no create2 factory at the same address on 50+ chains. So you still have the same problem of getting that create2 factory at the same address on each chain, including your private chain

[noyyyy]

A create2 factory wasn't used here because there is no create2 factory at the same address on 50+ chains. So you still have the same problem of getting that create2 factory at the same address on each chain, including your private chain

It doesn't matter if the create2 factory address is the same. Once the input args of create2 are deterministic(mainly contract bytes code), the outcome address will be the same.

[mds1]

It doesn't matter if the create2 factory address is the same. Once the input args of create2 are deterministic(mainly contract bytes code), the outcome address will be the same.

This is incorrect, the deployer address (the create2 factory) is a factor in the resulting contract address. From EIP-1014:

Behaves identically to CREATE (0xf0), except using keccak256( 0xff ++ address ++ salt ++ keccak256(init_code))[12:] instead of the usual sender-and-nonce-hash as the address where the contract is initialized at.

Where address is the address of the contract using the CREATE2 opcode 🙂

[noyyyy]

It doesn't matter if the create2 factory address is the same. Once the input args of create2 are deterministic(mainly contract bytes code), the outcome address will be the same.

This is incorrect, the deployer address (the create2 factory) is a factor in the resulting contract address. From EIP-1014:

Behaves identically to CREATE (0xf0), except using keccak256( 0xff ++ address ++ salt ++ keccak256(init_code))[12:] instead of the usual sender-and-nonce-hash as the address where the contract is initialized at.

Where address is the address of the contract using the CREATE2 opcode 🙂

Sorry, I misunderstood the create2🥲. Thanks for your correction.

[mds1]

No worries, will close this now 👌