-
Notifications
You must be signed in to change notification settings - Fork 105
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
- Loading branch information
Showing
4 changed files
with
40 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
## Pallet Multisig | ||
|
||
The issue with the `multisig` pallet is that every Multisig is scoped to a specific call hash. It is | ||
not possible to just create a Multisig between Alice and Bob - it must always be scoped to a | ||
specific call hash. A Multisig is only valid for its specific call hash. | ||
|
||
Now, migrating call hashes from the relay to AH is dangerous. The preimage data of that hash either | ||
does not decode anymore (best case) or decodes to something else (worse case). We can therefore not | ||
migrate the pure state of the `multisig` pallet. The only thing that goes amiss are previous | ||
approvals on a specific call hash by the Multisig members. | ||
|
||
One thing to consider is that Multisigs are constructed from account IDs. In order to allow the same | ||
Multisigs to be re-created, it is paramount to keep all account IDs that were accessible on the | ||
relay still accessible, hence: https://github.com/polkadot-fellows/runtimes/issues/526. Otherwise it | ||
could happen that a Multisig cannot be re-created and loses funds to its associated accounts. | ||
|
||
Note: I considered an XCM where the call is sent back to the relay to execute instead of executing | ||
on AH. This would allow to migrate Multisigs, but we either need to create a new pallet for this or | ||
change the existing one. Both probably not worth it for us now. | ||
### Actionable | ||
|
||
The only thing that we should do is to unlock the deposits on the AH since they were migrated to AH | ||
with the account state. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters