-
Notifications
You must be signed in to change notification settings - Fork 22
Support transfering a multisig from 1 chain to another #555
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
👍 Would love to see that. Having to create it manually is a bit cumbersome, but more importantly it is error prone. |
I'll tackle this in the next weeks. The way I intent to solve this is to replicate any multisig on any system chain, on the other system chains. This is done on the indexer level, and users will not have to do anything.
|
Sounds super good! Something that could be (but is not strictly required) added on top is simplifying sending of the initial remark. |
That remark, is only needed to let the indexer know that the multisig exists. Without this, I'd have to use a DB (as in a permissioned DB), and any other tool looking at the blockchain would not be able to know. |
If a multisig has been created on a chain, it'd be good to create a multisig on another chain in a couple clicks, without having to re-create a multisig.
It should effectively create a Tx on the other chain.
The text was updated successfully, but these errors were encountered: