# Mutable multisig

**URL:** https://forum.algorand.co/t/mutable-multisig/2919
**Category:** General
**Tags:** asa, rekeying
**Created:** [March 31, 2021, 9:32am UTC](https://forum.algorand.co/t/mutable-multisig/2919 "2021-03-31T09:32:22Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![robert](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/robert/32/666_2.png) [@robert](https://forum.algorand.co/u/robert)
#### Post date: [March 31, 2021, 9:32am UTC](https://forum.algorand.co/t/mutable-multisig/2919/1 "2021-03-31T09:32:22Z")

</div>

It seams it’s not possible to modify the multisig key participants.  
I have the following use case: For ASA `manager` address I would like to have a multisig key which we can modify.

Here is one idea how to do it:

1. Create the initial multisig: `acc_ms1`
2. Create a normal account (single public-private key): `acc_1`
3. Create ASA and set `manager` address to `acc_1` address.
4. Rekey `acc_1` to `acc_ms1`.

Later, when we need to update the participants of the multisig, we:

1. create a new multisig: `acc_ms2`
2. Rekey `acc_1` to `acc_ms2`. Note for the readers: it will still require a valid `acc_ms1` signature for that operation.

### Question

Is there a better way to do it? What would you recommend?

---

<div class="post-metadata">

### Author: ![ryanRfox](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/ryanrfox/32/364_2.png) [@ryanRfox](https://forum.algorand.co/u/ryanRfox)
#### Post date: [March 31, 2021, 1:54pm UTC](https://forum.algorand.co/t/mutable-multisig/2919/2 "2021-03-31T13:54:19Z")

</div>

Yes, that looks like the proper process to rotate the `auth-addr` of `acc_1` from `acc_ms1` to `acc_ms2`. What have you attempted and where is it failing?

---

<div class="post-metadata">

### Author: ![robert](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/robert/32/666_2.png) [@robert](https://forum.algorand.co/u/robert)
#### Post date: [March 31, 2021, 1:57pm UTC](https://forum.algorand.co/t/mutable-multisig/2919/3 "2021-03-31T13:57:28Z")

</div>

Oh, I forgot to add the question. I’ve updated the post.

---

<div class="post-metadata">

### Author: ![michel](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/michel/32/3176_2.png) [@michel](https://forum.algorand.co/u/michel)
#### Post date: [March 31, 2021, 3:35pm UTC](https://forum.algorand.co/t/mutable-multisig/2919/4 "2021-03-31T15:35:51Z")

</div>

The better way to do it is to wait till MyAlgo releases its upcoming ASA Manager where you will be able to create the ASA directly in MyAlgo with a multisig account and have everyone sign the transaction in an intuitive way.

---

<div class="post-metadata">

### Author: ![fabrice](https://avatars.discourse-cdn.com/v4/letter/f/5fc32e/32.png) [@fabrice](https://forum.algorand.co/u/fabrice)
#### Post date: [March 31, 2021, 5:26pm UTC](https://forum.algorand.co/t/mutable-multisig/2919/5 "2021-03-31T17:26:35Z")

</div>

Why do you first use `acc_1` as manager instead of `acc_ms1`?

---

<div class="post-metadata">

### Author: ![robert](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/robert/32/666_2.png) [@robert](https://forum.algorand.co/u/robert)
#### Post date: [April 1, 2021, 10:06am UTC](https://forum.algorand.co/t/mutable-multisig/2919/6 "2021-04-01T10:06:48Z")

</div>

To keep the same address, and use rekey to change the signature keys.

---

<div class="post-metadata">

### Author: ![fabrice](https://avatars.discourse-cdn.com/v4/letter/f/5fc32e/32.png) [@fabrice](https://forum.algorand.co/u/fabrice)
#### Post date: [April 1, 2021, 1:27pm UTC](https://forum.algorand.co/t/mutable-multisig/2919/7 "2021-04-01T13:27:08Z")

</div>

I might have misunderstood the use case, but I am not sure why you don’t directly set the manager address to `acc_ms1`.

Then you can still rekey `acc_ms1` to `acc_ms2`.  
And then `acc_ms2` to `acc_ms3` and so on.

---

<div class="post-metadata">

### Author: ![fabrice](https://avatars.discourse-cdn.com/v4/letter/f/5fc32e/32.png) [@fabrice](https://forum.algorand.co/u/fabrice)
#### Post date: [April 1, 2021, 3:00pm UTC](https://forum.algorand.co/t/mutable-multisig/2919/8 "2021-04-01T15:00:31Z")

</div>

Note that for the specific case of ASA manager, instead of rekeying, you can just update the address of the manager: [Algorand Developer Docs](https://developer.algorand.org/docs/features/asa/#modifying-an-asset)

---

<div class="post-metadata">

### Author: ![robert](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/robert/32/666_2.png) [@robert](https://forum.algorand.co/u/robert)
#### Post date: [April 2, 2021, 11:45am UTC](https://forum.algorand.co/t/mutable-multisig/2919/9 "2021-04-02T11:45:38Z")

</div>

This sounds good. I didn’t know you can rekey multisig.

---

<div class="post-metadata">

### Author: ![robert](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/robert/32/666_2.png) [@robert](https://forum.algorand.co/u/robert)
#### Post date: [April 2, 2021, 11:46am UTC](https://forum.algorand.co/t/mutable-multisig/2919/10 "2021-04-02T11:46:47Z")

</div>

> instead of rekeying, you can just update the address of the manager.

I know, but I wanted to keep the same address.

---

<div class="post-metadata">

### Author: ![fabrice](https://avatars.discourse-cdn.com/v4/letter/f/5fc32e/32.png) [@fabrice](https://forum.algorand.co/u/fabrice)
#### Post date: [April 2, 2021, 2:07pm UTC](https://forum.algorand.co/t/mutable-multisig/2919/11 "2021-04-02T14:07:41Z")

</div>

You can actually rekey any account, including smart contract account.
