How to Add a Custom Token in Trezor Suite

Supported Token Standards

1. Trezor Suite natively supports tokens built on Ethereum-compatible blockchains using the ERC-20 standard.

2. Tokens deployed on BNB Smart Chain adhering to BEP-20 are also recognized when manually added via contract address and decimal configuration.

3. Solana SPL tokens require explicit network selection and token list import through the Solana tab in Suite, as auto-detection is not enabled by default.

4. Polygon (ERC-20) and Avalanche C-Chain tokens appear automatically if listed on CoinGecko’s supported assets feed; otherwise, manual registration with chain ID and ABI snippet is necessary.

5. Arbitrum One and Optimism tokens follow the same manual addition flow as Ethereum, but users must verify correct RPC endpoint selection before confirming contract parameters.

Prerequisites for Manual Addition

1. A fully synced Trezor device connected via USB or WebUSB, with firmware version 24.9.1 or higher installed.

2. The exact token contract address—copied from Etherscan, BscScan, or equivalent explorer without leading/trailing spaces.

3. Precise decimal count, obtainable from the token’s official documentation or verified explorer page under “Token Info”.

4. Correct blockchain network identifier, such as 1 for Ethereum Mainnet, 56 for BSC, or 137 for Polygon.

5. An active internet connection and Trezor Suite desktop application v23.11.0 or later—browser extensions are not supported for custom token setup.

Step-by-Step Registration Process

1. Open Trezor Suite and navigate to the Portfolio tab, then click the + Add token button located at the top-right corner.

2. Select the target blockchain from the dropdown menu—options include Ethereum, BSC, Polygon, Avalanche, Arbitrum, and Optimism.

3. Paste the verified contract address into the designated field and click Continue.

4. Suite will attempt to fetch token metadata; if it fails, manually enter the token symbol, name, and decimal value as confirmed from an authoritative source.

5. Confirm all fields on the final preview screen, then approve the addition using your Trezor device’s physical buttons.

Verification and Balance Display

1. After successful registration, the token appears under the selected network’s asset list within the Portfolio view.

2. Real-time balance updates only after at least one confirmed on-chain transaction involving that token has been broadcast and mined.

3. Transaction history for the custom token is accessible only after the first inbound or outbound transfer—no historical data retroactively loads.

4. If the balance remains zero despite confirmed transfers, verify that the wallet address used matches the one derived from your Trezor’s Ethereum account path (m/44'/60'/0'/0/0).

5. Unsupported tokens may display a red warning icon next to the symbol; hovering reveals error code TKN-ERR-7, indicating ABI parsing failure or unsupported bytecode pattern.

Frequently Asked Questions

Q: Can I add a token with a non-standard decimal count like 18.5?A: No. Trezor Suite strictly enforces integer decimal values between 0 and 18 inclusive. Any token specifying fractional decimals will fail validation during manual entry.

Q: Why does my BEP-20 token show zero balance even after sending funds?A: This commonly occurs when the BSC network setting inside Suite is misconfigured. Ensure the network selector reads “BNB Smart Chain” and not “Ethereum” or “Testnet”, and confirm your receiving address was generated under the BSC derivation path (m/44'/714'/0'/0/0).

Q: Is it possible to remove a custom token once added?A: Yes. Right-click the token row in the Portfolio list and select “Remove token”. This action deletes local display settings only—it does not affect on-chain holdings or smart contract state.

Q: Do custom tokens support staking or governance actions directly through Suite?A: No. Trezor Suite provides read-only balance visibility and signing capability for transfers. Staking, voting, or contract interaction requires external dApps connected via WalletConnect, with Trezor acting solely as a signature provider.