Content
@
0 reply
0 recast
2 reactions
Sergey Potekhin
@fastfourier.eth
If you're using openzeppelin-foundry-upgrades, you may know that it does not support deterministic proxy deployment (only when using openzeppelin defender). Here's a little PoC on how you can do it yourself, while keeping the rest of the functionality. https://github.com/pimlicolabs/magic-spend/blob/main/src/MagicSpendFactory.sol#L16
2 replies
3 recasts
33 reactions
Mo
@meb
Question; What do you mean by deterministic proxy deployment, and what's the use case?
1 reply
0 recast
1 reaction
Sergey Potekhin
@fastfourier.eth
Hey, it means that we want our proxy contract address to be determined not by the deployer's nonce, but by it's code. For instance, that's how I can deploy it to the same address across many chains.
1 reply
0 recast
0 reaction
Mo
@meb
Ok thanks! That's what I thought, but so much happens in crypto, you never know!
0 reply
0 recast
0 reaction