How to Add Custom Tokens to Guarda Wallet?

Understanding Custom Token Integration

1. Guarda Wallet supports manual addition of tokens across multiple blockchains including Ethereum, BSC, Polygon, and Solana.

2. Users must verify contract addresses before adding tokens to prevent phishing or counterfeit asset exposure.

3. The wallet does not auto-detect tokens added via external sources—manual entry triggers on-chain validation only after confirmation.

4. Each custom token requires precise input of symbol, decimals, and network-specific contract address.

5. Tokens added manually appear in the asset list immediately but require at least one confirmed transaction to display accurate balance updates.

Step-by-Step Token Addition Process

1. Open Guarda Wallet mobile or desktop application and log into your account using password or biometric authentication.

2. Navigate to the Assets tab and tap the + icon in the top-right corner.

3. Select Add Custom Token from the dropdown menu.

4. Choose the correct blockchain network matching the token’s deployment—Ethereum mainnet, BSC, or another supported chain.

5. Paste the verified contract address into the designated field; Guarda performs real-time checksum validation for ERC-20 and BEP-20 standards.

Verification and Validation Checks

1. Guarda cross-references entered contract addresses against known token registries and Etherscan/BscScan verified contracts.

2. If a contract is flagged as unverified or lacks audit documentation, the interface displays a red warning banner with 'Unverified Contract'.

3. Token symbol and decimal precision are auto-fetched upon successful contract resolution—if unavailable, users must manually enter them.

4. Balance sync initiates only after the wallet detects at least one inbound transaction to the user’s address on that contract.

5. No automatic price feed integration occurs for custom tokens; market data remains absent unless listed on CoinGecko or CoinMarketCap APIs.

Security Protocols During Token Registration

1. All custom token configurations are stored locally on the device—no metadata or contract details are transmitted to Guarda servers.

2. The wallet enforces strict input sanitization to reject malformed addresses containing non-hexadecimal characters or incorrect length.

3. Users receive an on-screen prompt confirming network mismatch if the selected chain does not match the contract’s deployment layer.

4. Repeated failed attempts to add invalid tokens trigger a temporary UI lockout lasting 60 seconds.

5. Private key exposure risk remains unchanged during custom token addition—no cryptographic operations involve seed phrase transmission.

Frequently Asked Questions

Q: Can I add a token that isn’t ERC-20 or BEP-20 compliant?A: Guarda only supports standards-compliant tokens on EVM-compatible chains. SPL tokens on Solana require explicit network selection and valid mint address format.

Q: Why does my custom token show zero balance even after receiving funds?A: This occurs when the wallet hasn’t indexed the latest block containing the transfer. Manually triggering a rescan or waiting for full node synchronization resolves it.

Q: Is there a limit to how many custom tokens I can add?A: No hard cap exists, but performance degradation may occur beyond 50 manually added tokens due to local storage overhead.

Q: Do custom tokens support staking or yield features inside Guarda?A: Staking functionality depends entirely on the underlying protocol—not Guarda’s interface. The wallet only displays balances and enables transfers.