Mimir
CtrlK
  • Product Introduction
    • πŸ’‘Mimir Introduction
    • πŸ’°Multisig Introduction
    • Proxy Introduction
  • πŸͺ’Omni UX
    • πŸ”™Switch to Solo mode
    • πŸ’¬Address Format And Identity
  • Notice
    • Asset Hub Migration
  • Basic
    • πŸ’³Accounts
      • Advanced - Nested Multisig
      • Advanced - Time Delayed Proxy
    • πŸ“Dapps
    • 🏧Transaction
  • Advanced
    • πŸ‘€Watchlist
    • πŸ’ΌBatch
    • πŸ—£οΈProposer
    • Call Template
    • πŸ›οΈMulti-Sig Governance in Polkadot
    • πŸ’ΉParticipate Polkadot Native Staking
  • πŸ“ΆCustomize RPC
  • πŸ›œRemote Proxy
  • Step by step
    • 🟒Create Multisig
      • Create Nested Multisig
    • 🟒Create Proxy
      • Create Pure Proxy
    • πŸ“₯Import Multisig
    • πŸ› οΈInitiate Transactions
    • βš–οΈManage Transactions
      • ⏳Manage Delayed Proxy Transactions
  • Safety
    • πŸ”Call Data Verification
    • πŸš›Transaction Simulation
  • πŸ› οΈDeveloper
    • Batch API
    • πŸ–₯️Mimir SDK
      • PolkadotJS App
      • Polkadot API(PAPI)
      • ReactiveDOT/DOTConnect
  • FAQs
    • ❓FAQs
Powered by GitBook
On this page
  1. Step by step

πŸ“₯Import Multisig

Mimir will synchronize the multisigs associated with the Extension Wallets you've authorized locally.

However, during this process, there may be some edge cases that require you to manually import the multisig.

Import through creation

If you wish to recover a Static Multisig and you remember all the member addresses and the threshold, you can directly create a Static Multisig with the same parameters to recover that multisig.

PreviousCreate Pure ProxyNextInitiate Transactions

Last updated 5 months ago