-
-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🥹 Base Mainnet Deployment; EDIT: As of xdeployer
v3.0.0
, baseMain
Deployments Are Possible 🍻!
#164
Comments
Ouffffff this is so sad :((( What would be the alternatives to how to deploy on Base? |
Well I got good news for you: ethereum-optimism/op-geth#126. It will be added as predeploy to Base. This might take however until January most probably. |
By the way, question. If you will include an option to Would it pose any security risks? I guess it would not, right? Then maybe you could add it in the new version so that if similar problems happen in the future, they are not so huge. |
There will be no |
As of |
xdeployer
v3.0.0
, baseMain
Deployments Are Possible 🍻!
xdeployer
v3.0.0
, baseMain
Deployments Are Possible 🍻!xdeployer
v3.0.0
, baseMain
Deployments Are Possible 🍻!
Awesome!!!!!!!!!! ❤️ |
UPDATE: The predeploy of
Create2Deployer
is live on Base:0x13b0D85CcB8bf860b6b79AF3029fCA081AE9beF2
.cast code 0x13b0D85CcB8bf860b6b79AF3029fCA081AE9beF2 --rpc-url https://mainnet.base.org
Returned bytecode:
The above bytecode that is predeployed got verified here: https://etherscan.io/address/0xF49600926c7109BD66Ab97a2c036bf696e58Dbc2#code. You can compare the compiled runtime bytecode and it will match.
TL;DR: Unfortunately, it is not possible to deploy the
Create2Deployer
contract on the Base production network.Background
When bridging the funds to the Base mainnet, Base applied a recently introduced (but unfortunately unexpected) behaviour in the Bedrock upgrade that essentially sends a
self
transfer on L2. I.e. the nonce of the deployer account0x554282cf65b42fc8fddc6041eb24ce5e8a0632ad
was increased by 1 before deploying theCreate2Deployer
contract. Unfortunately, this means that I can no longer deploy the contract to0x13b0D85CcB8bf860b6b79AF3029fCA081AE9beF2
. If the demand for this chain is high enough, I might consider redeploying theCreate2Deployer
contract to a new address including the Base mainnet.The text was updated successfully, but these errors were encountered: