-
Notifications
You must be signed in to change notification settings - Fork 149
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
Deploy to DEGEN Chain #244
Comments
Looks like someone tried to deploy using the presigned transaction. However, Degen chain is an Arbitrum chain so the deployment reverted with out of gas, as described in the Multicall README. Unfortunately this means the nonce was burned, and the only way to get Multicall3 onto Degen is to have the chain developers place it as a predeploy. |
I'll see if I can get someone at Syndicate to predeploy the contract. Thanks @mds1! 🙏 Edit: Issue is going to be on Farcaster for the moment: https://warpcast.com/joeblau/0x78ffd027 |
@mds1 - do you know where the steps are to create a predeploy on an Arbitrum chain? If you can point me in the right direction, I'll see if I can head to syndicate's offices next week and get it fixed. |
Hey @gzeoneth, do you have any links or guidance on adding a predeploy to an Orbit stack chain? The context here is nonce 0 was burned on Degen chain, so Multicall3 cannot be deployed at the standard address, and they are looking into placing it as a predeploy as a workaround |
Chain Name
Degen
Chain ID
666666666
RPC URL
https://rpc.degen.tips
Block Explorer URL
https://explorer.degen.tips
Deployment Funds
Yes
The text was updated successfully, but these errors were encountered: