How to Use Guarda Wallet for Multi-Currency Storage? Full Guide

Multi-Chain Support Architecture

1. Guarda Wallet natively integrates with over 70 blockchain networks including Ethereum, Binance Smart Chain, Polygon, XDC Network, Litecoin, and Bitcoin.

2. Each supported chain operates independently within the wallet interface, allowing users to switch between networks without reconfiguration or external bridge tools.

3. Token recognition is automatic: ERC-20, BEP-20, XRC-20, and LTC-native tokens appear instantly upon wallet creation or import.

4. Cross-chain asset visibility relies on decentralized node infrastructure—no centralized indexer controls balance display logic.

5. Users retain full control over network selection; no default chain is enforced during transaction initiation.

Wallet Initialization Process

1. A new Guarda Wallet generates cryptographic keys locally in the browser or mobile runtime environment using WebCrypto API or Secure Enclave.

2. The 12-word mnemonic phrase is derived exclusively from local entropy sources and never transmitted to any server.

3. AES-256 encryption wraps the private key before storage on-device; decryption occurs only when entering the correct password or biometric confirmation.

4. No KYC data collection occurs at setup—no email, phone number, or identity document is requested or stored.

5. Recovery remains fully offline: importing the mnemonic into another Guarda instance restores all balances across all supported chains simultaneously.

Asset Management Workflow

1. Deposits are chain-specific: receiving BTC requires a Bitcoin address, while USDT on Ethereum demands an ERC-20-compliant address.

2. Sending assets triggers real-time gas estimation per network, with adjustable fee sliders for EVM-compatible chains.

3. Built-in token swap functionality routes orders through decentralized liquidity aggregators like 1inch and Paraswap without exposing private keys.

4. Staking operations for supported assets—including XDC and DOT—execute directly via smart contract interaction verified on-chain.

5. Portfolio value aggregation pulls price feeds from Chainlink oracles and displays weighted totals in user-selected fiat currencies.

Security Enforcement Mechanisms

1. Private keys never leave the device—even during cloud backup of encrypted wallet files.

2. Biometric authentication gates access to sensitive actions including send, swap, and staking confirmations.

3. Transaction signing occurs entirely within isolated execution contexts; no third-party script can intercept raw signatures.

4. Session timeouts enforce mandatory re-authentication after five minutes of inactivity on web interfaces.

5. Hardware wallet integration is intentionally omitted to preserve non-custodial guarantees—no external signing device can override local key management.

Frequently Asked Questions

Q1: Does Guarda Wallet support Bitcoin SegWit addresses?Yes. Guarda generates native SegWit (bech32) addresses by default for Bitcoin deposits and withdrawals.

Q2: Can I export private keys in WIF format from Guarda Wallet?No. Guarda does not expose raw private keys in any format—including WIF—to prevent accidental exposure or misuse.

Q3: Is there a maximum number of tokens I can hold simultaneously in one Guarda Wallet?There is no enforced limit. Users may hold thousands of tokens across multiple chains as long as each token’s contract address is valid and recognized by the wallet’s token list.

Q4: Do I need to manually add custom tokens for unsupported ERC-20 contracts?Yes. Guarda allows manual token addition by entering the contract address, symbol, and decimals—but only for tokens deployed on chains already enabled in the wallet.