0age pfp
0age
@0age
common challenge for protocols & smart wallets: how to best deploy an owned contract to the same address on multiple chains while supporting ownership changes? keystore rollups are cool but still need a safe way to access the state best way to support long-tail chains i’ve got is a hardcoded set of deployers 😑
1 reply
6 recasts
43 reactions

Gmgmgmgm pfp
Gmgmgmgm
@gmgmgmgm
What’s the core challenge? Create2 works different on different chains or something?
1 reply
0 recast
2 reactions

0age pfp
0age
@0age
it’s that when you need to change the owner, you don’t have a way to change it for the undeployed / counterfactual contracts (without deploying it first at least)
2 replies
0 recast
4 reactions

will pfp
will
@w
what about eip 6551 / TBAs? I believe it's set up so that the NFT holder controls the same address on every chain (via LZ I think). Rather than updating ownership on any/every chain, you just transfer the NFT (on the base chain). Love any gut reactions / critical feedback you might have here
1 reply
0 recast
1 reaction

Gmgmgmgm pfp
Gmgmgmgm
@gmgmgmgm
Interesting idea. But the lock-in concerns related to LZ I’d concur with. And to do it outside of LZ would seemingly require you to deploy an NFT contract first on each chain which why not just deploy the wallet then.
0 reply
0 recast
0 reaction