Backseats 🎩 on Warpcast

Content pfp

0 reply

26 recasts

26 reactions

Backseats 🎩 pfp

I've open sourced how @marka, @jalil, and I were able to deploy a Withdraw contract to the same address on a different network (Mainnet then Base) to withdraw and return 9.13 ETH that was accidentally sent to that address during the mint. Hope it's helpful to someone https://github.com/backseats/createrescue

6 replies

3 recasts

44 reactions

nicholas 🧨 pfp

tldr better to deploy with create2 always?

1 reply

0 recast

0 reaction

Backseats 🎩 pfp

Hadn’t thought about that actually

1 reply

0 recast

0 reaction

nicholas 🧨 pfp

@bbbdeals 2 will heed

1 reply

0 recast

0 reaction

Backseats 🎩 pfp

Thought about this more and yes, it is. Most obvious thing if one chain is ahead of the other, funds can get stuck. Biggest gotcha with CREATE2 is just making sure you haven't changed the bytecode at all between chains which can be mitigated with good commits and tagging but still a bit of a risk

1 reply

0 recast

1 reaction

nicholas 🧨 pfp

I wonder. If you're planning to change bytecode but want same addresses, maybe EOA deploy is better

1 reply

0 recast

0 reaction

Backseats 🎩 pfp

I'm just thinking maybe you removed an import that you didn't need but left in or fixed a typo or made some small gas efficiency tinkering with your already deployed contract. Something innocuous but would lead to different bytecode and hence a new address

1 reply

0 recast

0 reaction

Backseats 🎩 pfp

Also you should be creating a new deployer wallet for every new project as it is, the risk is your mainnet deployer wallet nonces being mismatched if you're going for this. So I'd say CREATE deploys for testnet, CREATE2 for mainnet, I think

1 reply

0 recast

1 reaction