Market Cap: $2.6125T 0.59%
Volume(24h): $36.7481B -53.94%
Fear & Greed Index:

36 - Fear

  • Market Cap: $2.6125T 0.59%
  • Volume(24h): $36.7481B -53.94%
  • Fear & Greed Index:
  • Market Cap: $2.6125T 0.59%
Cryptos
Topics
Cryptospedia
News
CryptosTopics
Videos
Top Cryptospedia

Select Language

Select Language

Select Currency

Cryptos
Topics
Cryptospedia
News
CryptosTopics
Videos

How to Switch Networks in Talisman Wallet

Talisman Wallet offers a Substrate-native network selection interface with real-time RPC health checks, parachain-aware address derivation, and XCM-first cross-chain transfers—no EVM support.

Nov 02, 2026 at 01:59 am

Network Selection Interface

1. Talisman Wallet displays a prominent network indicator in the top-right corner of its browser extension popup interface. This indicator shows the currently active chain name and its associated symbol, such as “Polkadot” or “Kusama”.

2. Clicking this indicator opens a dropdown list containing all preconfigured networks supported by the wallet, including Polkadot Relay Chain, Kusama, Astar, Moonbeam, and several parachains integrated via XCM.

3. Each listed network includes a visual icon, status badge (online/offline), and estimated block time. Networks marked with a green dot are confirmed to be syncing and responsive.

4. Hovering over any entry reveals RPC endpoint health metrics—latency, last synced block height, and node provider identity—without requiring manual inspection of configuration files.

Manual Network Configuration

1. Users can add unsupported Substrate-based chains through the “Add Network” option at the bottom of the dropdown menu.

2. The configuration form requires four mandatory fields: network name, chain ID, RPC endpoint URL, and SS58 prefix. Optional fields include token symbol, decimals, and block explorer URL.

3. Unlike EVM wallets, Talisman does not accept arbitrary chain IDs; it validates each ID against known Substrate genesis hashes before saving the configuration.

4. After submission, the wallet initiates a lightweight handshake with the RPC node to verify compatibility with SCALE encoding and metadata version v14 or higher.

Parachain Switching Workflow

1. When switching to a parachain like Acala or Parallel Finance, Talisman automatically detects whether the relay chain connection is active and initiates cross-chain account derivation if needed.

2. Account addresses change based on the selected parachain’s SS58 format, and the wallet overlays a visual warning if the current account has zero balance on that chain.

3. Asset balances are fetched only after successful chain context switch—not preemptively—to reduce API load and prevent stale cache issues.

4. Transfers initiated from a parachain interface default to XCM-based messaging rather than native parachain transfers unless explicitly overridden in advanced mode.

Multi-Chain Asset Visibility

1. The main dashboard shows assets grouped by chain, with collapsible sections for each connected network. Assets appear only if the chain is online and the account holds a non-zero balance.

2. Token metadata—including logo, name, and decimal precision—is pulled directly from on-chain asset registries where available, falling back to community-maintained JSON manifests hosted on IPFS.

3. Native tokens like DOT or KSM retain their original naming and display logic regardless of the active parachain context, ensuring consistent identification across environments.

4. Cross-chain liquidity positions, such as those held in liquidity pools on HydraDX or StellaSwap, are displayed under dedicated “Cross-Chain Positions” tabs rather than merged into native balance lists.

Frequently Asked Questions

Q1: Does Talisman Wallet support Ethereum or EVM-compatible chains?No. Talisman is built exclusively for Substrate-based ecosystems and does not implement EVM execution layers or Web3Provider injection for Solidity-based dApps.

Q2: Can I switch networks while a transaction is pending?Yes. Network switching does not interrupt ongoing signature requests or broadcast processes. Pending transactions remain tied to their originating chain context and continue processing independently.

Q3: Why does my account address change when I switch to a different parachain?Substrate uses chain-specific SS58 address formats. Each parachain defines its own prefix, resulting in distinct encoded representations of the same underlying public key.

Q4: Is it possible to disable automatic RPC health checks?No. Health verification is embedded into the core network routing layer and cannot be disabled. It ensures deterministic behavior during cross-chain operations and prevents misrouted XCM messages.

Disclaimer:info@kdj.com

The information provided is not trading advice. kdj.com does not assume any responsibility for any investments made based on the information provided in this article. Cryptocurrencies are highly volatile and it is highly recommended that you invest with caution after thorough research!

If you believe that the content used on this website infringes your copyright, please contact us immediately (info@kdj.com) and we will delete it promptly.

Related knowledge

See all articles

User not found or password invalid

Your input is correct