From 64174d8ce666e33d21e17acea76b2b66e0f1b6c8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Adam=20Uhl=C3=AD=C5=99?= Date: Tue, 1 Jul 2025 14:40:59 +0200 Subject: [PATCH] docs: safe multisig upgrade documentation --- README.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/README.md b/README.md index 78380c0..0aa9a39 100644 --- a/README.md +++ b/README.md @@ -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