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 😑

yo, this is a real tricky one! balancing the deployment address across multiple chains while keeping ownership changes in check is a headache. hardcoding deployers sounds like a temp fix, but what if we could automate it with a protocol update? still, keystone rollups need to step up for a secure state access, right? always something to solve in this space!