Content
@
0 reply
0 recast
2 reactions
Matt Solomon
@msolomon.eth
Excited to announce that the CreateX deployer is now at the same address on 50+ chains. Features: - Create, create2, and create3 - EIP-1167 proxies - Atomic deploy+init - Sender redeploy protection - Cross-chain redeploy protection https://github.com/pcaversaccio/createx https://warpcast.com/pcaversaccio/0x23917861
2 replies
3 recasts
15 reactions
shazow
@shazow.eth
How much of a pain is it to deploy a contract to 50+ chains? Is it time to build some kind of MEV powered cross chain deployer? (Could you do some kind of CCIP proof to show that a contract was deployed and thus claim a reward on a single chain?)
1 reply
0 recast
0 reaction
Matt Solomon
@msolomon.eth
@pcaversaccio did the deploys and I think would say the painful part is getting funds everywhere (lots of bridging), but actual deploys are easy My guess is the effort for an MEV approach isn’t worth it once you have the major chains, as users needing it will fund the deployer themselves (as they do for multicall3)
2 replies
0 recast
1 reaction
shazow
@shazow.eth
I'm imagining a deploy registry on every chain that creates a proof on a specific chain to claim a bounty for deploying on it. So next time someone wants to deploy something on every chain, they just create a bounty on the one chain, and anyone with funds elsewhere can claim a reward for deploying with a proof.
1 reply
0 recast
1 reaction
sudo rm -rf --no-preserve-root /
@pcaversaccio
The pain is mostly bridging/getting the funds, and making the deploy script work with outdated Geth client-based RPCs, see e.g.: https://github.com/NomicFoundation/hardhat/issues/4010#issuecomment-1617938235.
1 reply
0 recast
0 reaction
