This is a fork of Arachnid/deterministic-deployment-proxy with improved security by hashing user's address with salt in the factory contract itself.
All npm dependencies have been updated to latest versions.
If you encounter 'invalid opcode' error then downgrade the EVM version from shanghai to paris in scripts/compile.ts:
compilerInput.settings.evmVersion = 'paris'
A much better way to deploy a contract these days is using a keylessly-deployed CREATE3 factory. See SKYBIT Keyless Deployment.
This is a proxy contract that can be deployed to any chain at the same address, and can then in turn deploy any contract at a deterministic location using CREATE2. To use, first deploy the contract using the one-time-account transaction specified in output/deployment.json (or grab last known good from bottom of readme), then submit a transaction to the address specified in output/deployment.json (or grab last known good from bottom of readme). The data should be the 32 byte 'salt' followed by your init code.
yarn install
yarn build
./scripts/test.shSee scripts/test.sh (commented). Change JSON_RPC environment variable to the chain of your choice (requires an unlocked wallet with ETH). Notice that the script works against any chain! If the chain already has the deployer contract deployed to it, then you can just comment out the deployment steps (line 20 and 23) and everything else will still function as normal. If you have already deployed your contract with it to the chain you are pointing at, the script will fail because your contract already exists at its address.
This repository contains a simple contract that can deploy other contracts with a deterministic address on any chain using CREATE2. The CREATE2 call will deploy a contract (like CREATE opcode) but instead of the address being keccak256(rlp([deployer_address, nonce])) it instead uses the hash of the contract's bytecode and a salt. This means that a given deployer address will deploy the same code to the same address no matter when or where they issue the deployment. The deployer is deployed with a one-time-use-account, so no matter what chain the deployer is on, its address will always be the same. This means the only variables in determining the address of your contract are its bytecode hash and the provided salt.
Between the use of CREATE2 opcode and the one-time-use-account for the deployer, we can ensure that a given contract will exist at the exact same address on every chain, but without having to use the same gas pricing or limits every time.
0xaf45f86eb0bbf0536fa770b699b806f22496d875
0xbf53a2647649ccd539e8f7e6864447bb7fb14ada
0xf8858085174876e800830186a08080b4602a80600a5f395ff3fe5f33815280356020526034600c20601f19360180602084378234f5908115602757526014600cf35b80fd1ba02222222222222222222222222222222222222222222222222222222222222222a02222222222222222222222222222222222222222222222222222222222222222
0xf8888085174876e800830186a08080b7602b80600c6000396000f3fe600033815280356020526034600c20601f19360180602084378234f5908115602857526014600cf35b80fd1ba02222222222222222222222222222222222222222222222222222222222222222a02222222222222222222222222222222222222222222222222222222222222222
0x790bec4474aff8686ab85225584988f9622efff5
0x3c1af275c75fb2d5556cf85bcfed36bfc2552890
100 nanoeth (gwei)
100000
Note: The actual gas used is 62,264, but that can change if the cost of opcodes changes. To avoid having to move the proxy to a different address, we opted to give excess gas. Given the gas price, this may result in notable expenses, but since this only needs to be deployed once per chain that is acceptable.