From f7a143aa57c3fa7388871c7a6cd654fa01bddc5b Mon Sep 17 00:00:00 2001
From: Lars Lubkoll <11710767+lubkoll@users.noreply.github.com>
Date: Thu, 5 Sep 2024 09:21:12 +0000
Subject: [PATCH] Update dev guidelines

---
 DEV_GUIDELINES.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/DEV_GUIDELINES.md b/DEV_GUIDELINES.md
index 7a6689813..1889a48fd 100644
--- a/DEV_GUIDELINES.md
+++ b/DEV_GUIDELINES.md
@@ -28,8 +28,8 @@ The following steps are required to release smart contracts:
     * Make sure you have the latest state: `git checkout main && git pull`
     * Create a tag: `git tag -a "<TAG>" -m"<DESCRIPTION>"` (TAG should be of the form v[0-9]+.[0-9]+.[0-9]+)
     * Push tag: `git push origin <TAG>`
-2. Upload code through multisig (requires `osmosisd`):
-    * Create signed message: `bash scripts/generate_signed_upload_tx.sh <WASM_FILE> <DEPLOYER>`, where <DEPLOYER> is the name of your key registered with `osmosisd`.
+2. Upload code through multisig (This can only be done by the multisig-members: @magiodev, @arhamchordia @LaurensKubat, please sync with them):
+    * Create signed message: `bash scripts/generate_signed_upload_tx.sh <WASM_FILE> <DEPLOYER> <MULTISIG>`, where <DEPLOYER> and <MULTISIG> are the names of your key, resp. the multisig key, registered with `osmosisd`.
     * Collect signed messages from coworkers, when you have enough: `bash scripts/upload_through_multisig.sh "<SIGNED_TX_1> <SIGNED_TX_2>"`
 3. Create proposal to instantiate or migrate contracts on [DAODAO](https://daodao.zone/dao/osmo12ry93err6s2ekg02ekslucwx8n3pxm3y7zxz3l6w8zuhex984k5ss4ltl6/proposals).
 4. After the proposal did receive enough votes, it can be executed.