Skip to content

add multisig protection for subnet ownership #539

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

Closed
MichaelTrestman opened this issue Mar 26, 2025 · 0 comments · Fixed by #534
Closed

add multisig protection for subnet ownership #539

MichaelTrestman opened this issue Mar 26, 2025 · 0 comments · Fixed by #534

Comments

@MichaelTrestman
Copy link
Collaborator

add this use case to the new multisig doc.

Initialize the multisig transaction: create a subnet

Next, use one of the signatory wallets to initiate the multisig transaction. Since we are triggering this transaction externally, it's referred to as an 'extrinsic' transaction. In this example, we'll create a subnet.

  1. Ensure that the wallet has sufficient (test) TAO to pay the fee. If you have testTAO in another wallet, use btcli wallet transfer. You can see the current burn cost for creating a subnet by running btcli subnet burn-cost.

  2. As that signatory go to the Polkadot-JS app extrinsics page.

  3. Under using the selected account, select the multisig.

  4. Under submit the following extrinsic, select subtensorModule and registerNetwork.

  5. Copy out the encoded call data and encoded call hash. Other signatories must have the encoded call data in order to sign the transaction.

  6. Click Submit Transaction, which will open up the transaction signing modal.

  7. Under multisig signatory, select the wallet you wish to use, which must have

Complete the mustisig transaction

use the call data from before...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant