A place for talking about the Ethereum Virtual Machine on Farcaster.

Is anybody aware of an existing generic create2 factory that serves as the create2 msg.sender? 

I believe that would allow for deployment to deterministic address agnostic of who is actually initiating the deploy, which would be quite nice for enabling a team to deploy as needed across networks.

building /hatsprotocol | 
proudly mid-curving it since 1995

alternatively, whats the best way to share a deployer account within a dev team?

Daimo Pay. Build once, distribute everywhere

Likely due to the metadata hash, which can vary by machine due to different filepaths. I recommend setting it to ‘none’ to ensure identical bytecode -> same address, regardless of who builds the contracts

great! this is what I use for all my contracts. For some reason I feel like I and another team member have been getting different deployment addresses, but perhaps we were doing something else different as well. Will re-test

Arachnid/0age factory is the default in Foundry

All u need is a deploy script with
vm.broadcast();
new MyContract{salt: 0}();

Works on all major evm chains

Lead developer of ENS & Ethereum Foundation alum. Certified rat tickler. he/him.

I'm on Mastodon: https://cryptodon.lol/@weka

I'm on bluesky: nick.eth.limo

I work at the posts office

terminally.online

Good point. Luckily nearly all the contracts im deploying these days are owned by hat ids not addresses 😉

You do have to be careful about anything that uses msg.sender as an implicit default, like OZ Ownable. If you deploy using a CREATE2 factory in production, make sure you also do it in your tests—If you're not careful, the factory may end up as the owner of your contract.

@nick.eth's deterministic deployment proxy (the forge script default) and @0age's ImmutableCreate2Factory (my personal preference) both work like this: the factory contract is the CREATE2 sender, not the deployer EOA address. They're useful for exactly the reason you describe.