1. had to check the way multix does it on relay chain


2. then had to construct the same call on peoples chain

**Encoded call data:**

0x2901030014b81b76cbf4a9031028a71b14c4740c2970710044cb1e145cbb77948132300d755a2160296c65f838252b9da9f51b9691950ece465e1a71b444d286d91316dd24726ef17b500f436cf596935acac782c71a423d35a959f3e6831f13c34db9d71d427639925d379eb016660a025b9bd639bffa555a4f4e03f4a503fccda32b0d4d683cebcfbd11d233f661f486374fd519d43069406ad06ece972181155341722e000000fc4d756c746978206372656174696f6e20316e747259767a37676d6435395176316e67646377417570563463593844504d6b4d4a4269504132595569565876450000

**Encoded call hash:**

0x6a8534e9c370ad2db248995a32c67a0cb73bb12bdaf983e7d83d90e7f4c5ab7c

**Encoding details:**

callindex
2901
threshold
0300
othersignatories
14
b81b76cbf4a9031028a71b14c4740c2970710044cb1e145cbb77948132300d75
5a2160296c65f838252b9da9f51b9691950ece465e1a71b444d286d91316dd24
726ef17b500f436cf596935acac782c71a423d35a959f3e6831f13c34db9d71d
427639925d379eb016660a025b9bd639bffa555a4f4e03f4a503fccda32b0d4d
683cebcfbd11d233f661f486374fd519d43069406ad06ece972181155341722e
maybetimepoint
00
callindex
0000
remark
fc 4d756c746978206372656174696f6e20316e747259767a37676d6435395176316e67646377417570563463593844504d6b4d4a426950413259556956587645
reftime
00
proofsize
00


Failure:


Good, fixed this now that I learnt what the `SenderInSignatories` error was:


Fixed in call data:

**New encoded call data:**

0x2901030010683cebcfbd11d233f661f486374fd519d43069406ad06ece972181155341722e427639925d379eb016660a025b9bd639bffa555a4f4e03f4a503fccda32b0d4d726ef17b500f436cf596935acac782c71a423d35a959f3e6831f13c34db9d71d5a2160296c65f838252b9da9f51b9691950ece465e1a71b444d286d91316dd24000000fc4d756c746978206372656174696f6e20316e747259767a37676d6435395176316e67646377417570563463593844504d6b4d4a4269504132595569565876450000

**Call hash:**

0x27a9895f47499a614ca6696a6239e9b97d9d3b2f0629ac5ad91b35d9316d4bf0

It failed again. Error: `SignatoriesOutOfOrder`.

I presume this means that the order from the original Multix creation matters, makes sense depending on the equation to generate the new address (shamir secret sharing algorithms stuff). This was the original order:


Let's try again.

Roman constructed a new call for him to submit, here's the encoded call data used:

0x2901030010726ef17b500f436cf596935acac782c71a423d35a959f3e6831f13c34db9d71db81b76cbf4a9031028a71b14c4740c2970710044cb1e145cbb77948132300d75427639925d379eb016660a025b9bd639bffa555a4f4e03f4a503fccda32b0d4d683cebcfbd11d233f661f486374fd519d43069406ad06ece972181155341722e000000fc4d756c746978206372656174696f6e20316e747259767a37676d6435395176316e67646377417570563463593844504d6b4d4a4269504132595569565876450000

Turns out the order from multix was wrong. Looking into the chain state its actually this:


... also turns out it's in reverse indexed order, kinda silly! lol

Okay.. so the question now is what is the deposit for creating the multisig? Let's just take it from Multix.

Okay it worked. Blocked because insufficient funds error. Hmm.. maybe its the 0.7 DOT missing on the multisig account.

## Sign Multisig txns with Polkadot JS apps

1. Go to: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc-people-polkadot.luckyfriday.io#/accounts
1. Check you have some DOT to sign txns.
2. Teleport if not
3. Add the Webzero V3 multisig address to your address book: `1ntrYvz7gmd59Qv1ngdcwAupV4cY8DPMkMJBiPA2YUiVXvE`
4. Go to the multisig icons to sign the calls pending there (see screenshot below)


Block success: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc-people-polkadot.luckyfriday.io#/explorer/query/0x964880d87fd94a7a4eb35fdb9533b39f077f5b48c0b9858ef330a9ee9a313bb2