Deterministic Deployments Can't Work With Library Due To Gas Limit

[xBalbinus]

Description:
https://github.com/Arachnid/deterministic-deployment-proxy is one of the most popular EVM deployment tools for deploying smart contracts to a canonical address across all chains in a permissionless way. Unfortunately it has a hard-coded gasLimit (on the README) and FVM’s gasLimit is an order of magnitude higher. Drips.network and other EVM teams currently cannot use this popular proxy to deploy their contracts to their canonical addresses on FVM due to differences in our gasLimit.
• Current https://filfox.info/en/stats/gasFVM gasLimit>s from Filfox vs 100000 required by the deterministic-deployment-proxy
• Here’s the explanation of how the deterministic deployer deployment transaction works: ZeframLou/create3-factory#4 (comment)
• The Arachnid deterministic deployer is used to CREATE2 the CREATE3Factory, which is used to create a DripsDeployer which then deploys all the Drips contracts using CREATE3

Source:
https://filecoinproject.slack.com/archives/C0745JU645A/p1723119353808849?thread_ts=1723119353.808849&cid=C0745JU645A

[longfeiWan9]

@xBalbinus Can you please review this pain-point and add potential solution for it?

[xBalbinus]

A current solution right now is to use Safe's singleton factory for deterministic deployments, see

import { getSingletonFactoryInfo } from "@safe-global/safe-singleton-factory";

const deterministicDeployment = (network: string): DeterministicDeploymentInfo => {
    const info = getSingletonFactoryInfo(parseInt(network));
    if (!info) {
        throw new Error(`
        Safe factory not found for network ${network}. You can request a new deployment at https://github.com/safe-global/safe-singleton-factory.
        For more information, see https://github.com/safe-global/safe-contracts#replay-protection-eip-155
      `);
    }
    return {
        factory: info.address,
        deployer: info.signerAddress,
        funding: BigNumber.from(info.gasLimit).mul(BigNumber.from(info.gasPrice)).toString(),
        signedTx: info.transaction,
    };
};

And include deterministicDeployment in your hardhat config.

In the future, we should probably look to fork the Arachnid library, or even create a deployment factory contract example for people to fork off of.

[trruckerfling]

https://github.com/Arachnid/deterministic-deployment-proxy adding this that @longfeiWan9 shared. So does that mean that we will need to provide a custom deployment repo for both foundry and hardhat or just one?

[trruckerfling]

Resolved with docs guide filecoin-project/filecoin-docs#2309

[trruckerfling]

@xBalbinus you solved this issue with adding of deterministic deployment. close this issue? #82 is assigned to me to finish up

[xBalbinus]

Cool. Let’s close.

…

On Mon, Dec 16, 2024 at 12:27 PM Sarah Thiam ***@***.***> wrote: @xBalbinus <https://github.com/xBalbinus> you solved this issue with adding of deterministic deployment. close this issue? #82 <#82> is assigned to me to finish up — Reply to this email directly, view it on GitHub <#45 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASH4FPRXDPXCGXWW2FAL7632F4ZTLAVCNFSM6AAAAABMGTNW4CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBWGY2TOOJSGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>