-
Notifications
You must be signed in to change notification settings - Fork 211
Add support for Plume Mainnet (v2) #369
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
Comments
@mds1 Let me know if you're able to help here! |
Hey @mds1, is this something you can help out with? We're unable to deploy using the pre-signed transaction on Arbitrum Orbit chains. |
As mentioned in the REAMDE I am no longer supporting manual deployments. I would recommend asking the Arbitrum team or the Plume team to place Multicall3 as a preinstall on all chains, which is what the OP Stack does: https://docs.optimism.io/operators/chain-operators/features/preinstalls |
Somehow even though |
I manually deployed Multicall3.sol on a new deployment of Plume mainnet, but the gas usage is 1.2m because of how Arbitrum Orbit chains calculate L1 fees: https://phoenix-explorer.plumenetwork.xyz/tx/0x9a7a728978417e5f0967148d0197d4dd1632a80bed7641e6b8083d03eb7a5730
Would you be able to send me a new pre-signed transaction with e.g.
gasLimit = 5_000_000
that I can use to deploy multicall3? I'm purposefully keeping the RPC URL secret so the attacker doesn't have a chance to steal the $1 in gas I'll send to the account before deploying the contract.The text was updated successfully, but these errors were encountered: