Content
@
0 reply
0 recast
0 reaction
✳️ dcposch on daimo
@dcposch.eth
what's the best-practice way to hold ownership of an upgradeable contract? ideally i'd want a multisig, plus a clean process for us to sign an upgrade transaction together.
4 replies
0 recast
21 reactions
Samuel ツ
@samuellhuber.eth
why use upgradeable contracts? I am always wondering whats the one reason one can not migrate to a different contract address. (genuinly curious, haven't used them so far)
2 replies
0 recast
0 reaction
Archethect
@archethect.eth
* Basically to keep the existing state while you want to change how your contract works + to preserve composability with other apps. * On the frontend you don't want to change the contract address the app connects to every time the contract implementation changes.
1 reply
0 recast
1 reaction
Daniel Lombraña
@teleyinex.eth
This. And also fees. Imagine moving thousands of tokens.
1 reply
0 recast
0 reaction
Samuel ツ
@samuellhuber.eth
so how do you keep state? meaning you can't change state variables and maybe add some functions but in general just change the actual logic implementation but not the interface of the contract? will have to read more into that. Any good guides?
2 replies
0 recast
0 reaction
alex
@alexgrover.eth
Not fully understanding your question, but this series of posts might help https://docs.openzeppelin.com/upgrades-plugins/1.x/writing-upgradeable
1 reply
0 recast
0 reaction
Samuel ツ
@samuellhuber.eth
thank you! going through it next week
0 reply
0 recast
0 reaction
