Base

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

Growth is infinite. Work is worship.

/vv /opepen /checks

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

Building Chonks, /contractreader, /dropframe and basepaintbot.xyz| Solidity & full stack dev | https://gallery.so/backseats

tldr better to deploy with create2 always?

solidity & product. i interview crypto builders @ web3galaxybrain.com

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

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

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