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. Omni UX

Address Format And Identity

PreviousSwitch to Solo modeNextAccounts

Last updated 1 month ago

Address display depends on the network, but under the Omni UX, your address presentation and on-chain identity still rely on a specific chain. In Mimir, by setting a default address format, you can control which address and Identity you want to display.

Set Default Address Format

Click the copy button to open the address selection sidebar for copying.

Click the 🌟 to set the address you want to display as the defaultβ€”you can update it anytime from here later.

If you select system parachains or the Relay Chain, Mimir will ensure that the People Chain remains connected. This is to retrieve Identity data for better account display. Unless you have a specific reason, we recommend keeping it connected.

πŸͺ’
πŸ’¬