Does This Work on Rollup Chains (Optimism, Arbitrum)?

[PaulRBerg]

Pardon me for opening an issue for a simple question (may be worth it to enable discussions on this repo?)

I'm currently using the deterministic-deployment-proxy to deploy contracts deterministic addresses across chains. One of the issues with that it can't be used on Arbitrum and Optimism..

Is xdeployer able to deploy to rollup chains as well?

[pcaversaccio]

@PaulRBerg good point: I enabled discussions here.

Regarding your question: yes xdeployer is able to deploy on rollup chains. Currently, however, only the testnets are supported (I will add later the prod networks):

• optimismtestnet
• arbitrumtestnet

For testing purposes, I just deployed a mock ERC20 including constructors on both rollup chains:

• optimismtestnet: MyToken
• arbitrumtestnet: MyToken

Also (just for testing) I also transferred the tokens and it worked smoothly:

However, you must increase the gasLimit significantly to deploy on Arbitrum as it seems. Also, in case interested check here for the standard Arbitrum ERC-20 interface.

[PaulRBerg]

I enabled discussions here.

Note that you can convert this issue to a discussion. There's a button on the right-hand side of the screen.

However, you must increase the gasLimit significantly to deploy on Arbitrum as it seems

Yes, we have to do that because of the way the rollup chain txs are batched. That was actually my fear, that bumping the gas limit would break xdeployer.

[pcaversaccio]

Note that you can convert this issue to a discussion. There's a button on the right-hand side of the screen.

Thanks, done 😀.

Yes, we have to do that because of the way the rollup chain txs are batched. That was actually my fear, that bumping the gas limit would break deployer.

No, it does not break xdeployer. Currently, there is an upper acceptable gasLimit of 15m (due to the Ethereum mainnet) that the plugin checks for. If this threshold is exceeded, the plugin will not start any deployment. You can set your own gasLimit via the xdeployer configuration. Let me know if you think 15m is not enough for your application.

[0xD006F00D]

Hi @pcaversacci, the proxy Paul linked is actually just to deploy the create2 contract itself and he stated the gasLimit is influencing the deployment address. So to ask the question differently - How did you deploy the create2 contract itself?

[pcaversaccio]

I have a section in the README on how this works. In order to save the deployment of the CREATE2 helper contract itself, I deployed the helper smart contract on all EVM chains supported. Here is the repository: create2deployer. This will save deployment costs for anyone that uses this plugin as well as keeps the complexity low. Please see here for certain design decisions regarding governance modifiers.

[0xD006F00D]

So you just used the deploy script to deploy the create2deployer contract to every chain? Was the deployment nonce always the same when you deployed it or how come the create2deployer address is the same across networks?

[pcaversaccio]

Yes exactly using my deployer address 0x554282Cf65b42fc8fddc6041eb24ce5E8A0632Ad with the same nonce on all chains. It's similar to the approach taken at multicall.