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

Customize RPC

PreviousParticipate Polkadot Native StakingNextCreate Multisig

Last updated 1 month ago

Due to factors like region or network conditions, the default RPC connections might occasionally fail—especially with the launch of the Omni UX, where multiple network connections make the issue more noticeable.

To address this, we’ve added a customized RPC setting. You can find the entry at the top right of the network connection page or access it through the settings menu.

Customize RPC

Network

Setting

We've listed some node options for you, but you can still add a custom node directly by entering it into the input field.

📶