Mimir
  • Product Introduction
    • 💡Mimir Introduction
    • 💰Multisig Introduction
    • Proxy Introduction
  • 🪢Omni UX
    • 🔙Switch to Solo mode
    • 💬Address Format And Identity
  • 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
  • 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 1 month ago

📥