Native BitBoxApp support
The BitBoxApp provides direct, native support for the Ethereum (ETH) network and a curated list of popular ERC-20 tokens.
.png)
To use any other EVM (Ethereum Virtual Machine) chain, you must connect your BitBox02 to a compatible third-party wallet.
How to access any EVM chain
You can securely manage assets on virtually any EVM-compatible network by connecting your BitBox02 to a powerful third-party wallet.
To get started, follow one of our guides:
These wallets act as a secure interface, allowing your BitBox02 to sign transactions on chains like Polygon, Avalanche, and Base while your keys never leave your device.
Firmware-supported chains
The BitBox02 firmware has built-in parameters for many popular EVM chains, which you can verify in the source code on GitHub. When you transact on these networks, the transaction details will appear clearly for verification on your BitBox02 screen, without any warnings.
| Ethereum (ETH) | Binance Smart Chain (BSC) | Polygon (MATIC) |
| Avalanche (AVAX) | Gnosis (GNO) | Arbitrum (ARB) |
| Base | Fantom (FTM) | Optimism (OP) |
Using other EVM chains (Unknown Chain ID Warning)
You can use your BitBox02 with many of other EVM chains that are not in the list above.
When you create a transaction for one of these chains, the BitBox02 will show a warning: "Unknown chain ID".
This is expected and normal behavior. The warning simply means the network's specific details are not pre-loaded in the BitBox02 firmware.
For example, Fantom (FTM) is migrating to a new chain called SONIC. While FTM is listed in our firmware, the new SONIC chain is not. When you try to sign a transaction on SONIC, you will receive the "Unknown chain ID" warning.
You can safely ignore this warning and confirm the transaction on your BitBox02 after carefully verifying the address and transaction details in your third-party wallet (like Rabby or MEW) and your BitBox.