logos-storage/logos-storage-contracts-eth
1
0
Fork 0
mirror of https://github.com/logos-storage/logos-storage-contracts-eth.git synced 2026-01-19 05:23:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: safe multisig upgrade documentation

Browse Source
This commit is contained in:
Adam Uhlíř 2025-07-01 14:40:59 +02:00
parent 03b5227356
commit 64174d8ce6
No known key found for this signature in database
GPG Key ID: 1D17A9E81F76155B
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
README.md
View File

@ -104,6 +104,17 @@ Once the new feature upgrade is planned, the first step when drafting this new v
the upgrade's changes (if there were any) back into the `Marketplace` contract and any modified subcontract
on the new feature branch.
#### Safe Multisig Upgrade
When the `Proxy`'s owner is set to Safe's Multisig Wallet, the upgrade process needs to be modified. The upgrade
deployment module cannot create the `upgradeAndCall` call directly; hence, the deploy module needs only to deploy the
upgraded implementation logic.
Then, the `upgradeAndCall` call needs to be created through the Safe Wallet UI using the "Transaction Builder," where it
is recommended to input the `ProxyAdmin` ABI, which helps to easily create the `upgradeAndCall` call. The `proxy`
parameter is the Marketplace's Proxy address, the `implementation` parameter is the address of the new upgraded
implementation, and the `data` can be left empty (`0x`).
## Marketplace overview
The Codex storage network depends on hosts offering storage to clients of the