sam bacha

> @sambacha No decisions have been made on anything related to how packages are fetched outside of supporting git repositories without requiring git. Anything else would obviously require a tarball....

Even defining no optimizations has lead to incorrect settings, leaving it undefined was not the same as explicitly disabling the optimizer

I think this is because I have a modline at the top most of the dapprc file ```shell # -*- shell -*- export ETH_RPC_URL='' export FOUNDRY_CI=0 ```

Especially considering how etherscan represents the current factory, teams may prefer to have their own canonical factory (nothing preventing other people from using it ofc) etc etc

> The main reasons to use another create2 deployer are (1) pass init data to be called after deploy, (2) more leading zeros for cheaper deploy, and I think that's...

> The way we verify contracts or create the transaction depends on the factory we use. So just letting anyone use their own factory implementation is not that straightforward imo....

> This is a good config option to add, e.g. `create2_deployer = 0x123...`. Alternative name ideas: `create2_deployer_contract` or `create2_factory` # FoundryCreate2FactoryV8

> Proposed create2 deployer below, feedback welcome. Interfaces (and the code comments) are largely based on @0age's [create2 deployer](https://etherscan.io/address/0x0000000000FFe8B47B3e2130213B802212439497#code), with a few modifications based on the above. > > ```solidity...

> What chain ID information did you have in mind? > > Another method that hashes your salt with chain ID to prevent redeploying to another chain at the same...

> @mds1 thanks for tagging me - the suggested interface would not be compatible with my [`Create2Deployer.sol`](https://github.com/pcaversaccio/create2deployer/blob/main/contracts/Create2Deployer.sol) code. I use the following semantics: > > ```solidity > /** > *...