Cryptnox supports Band Protocol as ERC-20 BAND on Ethereum, not as native BandChain BAND. BAND is not pre-programmed on the card, so you add the Ethereum token once through Add a Token or Add a Network using contract 0xba11d00c5f74255f56a5e366f4f77f5a186d7f55. The receiving address is a 0x-prefixed 20-byte EVM address, with the BAND-controlling Ethereum key created and kept inside the card’s secure element.
CRYPTNOX products are also available worldwide through our official Amazon stores.
For a Cryptnox buyer, the important BAND distinction is the network route. The Cryptnox Crypto Hardware Wallet – Dual-Card Set can hold ERC-20 BAND on Ethereum after the token is added. It does not hold native BAND on BandChain.
That means a BAND balance sent to a Cryptnox-controlled address must use Ethereum as the transfer network. The address format for this route is the standard Ethereum-style 0x-prefixed 20-byte EVM address. Native BandChain BAND belongs to a different chain environment and should not be sent to the Ethereum address used with Cryptnox.
The Cryptnox coin and blockchain support page is the right internal reference when checking whether an asset is handled as a native coin or as a token on another chain. For BAND, the supported Cryptnox route is specifically the Ethereum ERC-20 representation.
BandChain is the native Band Protocol chain, and it is a Cosmos-SDK, non-EVM layer 1. That matters because native BandChain BAND does not use the same account route as ERC-20 BAND on Ethereum. Cryptnox holds the Ethereum representation of BAND, so the account you use is an Ethereum account, not a native BandChain account.
The official BandChain documentation describes BandChain as its own chain, while Cryptnox support for this asset is limited to the Ethereum token route. The two forms may share the BAND name, but the wallet path is not interchangeable.
This is the operational decision that prevents confusion: if the sending platform asks for the network, choose the Ethereum/ERC-20 route for Cryptnox. If the platform shows native BandChain as the route, that is not the route this card can hold for BAND.
BAND is not shipped as a pre-enabled asset on the Cryptnox card. After the Dual-Card Set is initialised, add BAND once through Add a Token or Add a Network. For BAND, the details to enter are Ethereum as the network and 0xba11d00c5f74255f56a5e366f4f77f5a186d7f55 as the ERC-20 contract.
The setup sequence for a BAND holder is therefore different from simply receiving a native coin address. First initialise the two-card wallet, then open the Ethereum account controlled by the card, then add the ERC-20 BAND token so the Ethereum BAND balance can be managed through the chosen app or Web3 flow.
If you are new to the smart card workflow, use the Cryptnox hardware wallet tutorials before funding the BAND address. The tutorial hub is useful before adding an Ethereum token manually because it explains the card and app flow you will use for the ERC-20 BAND account.
ERC-20 BAND on Cryptnox is identified by its Ethereum token contract. The contract to use is 0xba11d00c5f74255f56a5e366f4f77f5a186d7f55. The Etherscan BAND token page is the external contract reference for the Ethereum token.
The receiving address for the Cryptnox BAND route is a 0x-prefixed 20-byte EVM address. That address is suitable for ERC-20 BAND on Ethereum because the BAND balance is tied to the Ethereum account controlled by the card. A native BandChain address is not the address type for this Cryptnox route.
These checks are especially important for BAND because the asset name can appear in both native-chain and Ethereum-token contexts. Cryptnox handles the Ethereum-token context only, so the network, contract, and address format all need to match that route.
For BAND on Cryptnox, the protected item is the Ethereum private key that controls the 0x address holding the ERC-20 token. That key is created inside the secure element and is not exported from the card. The BAND token balance remains on Ethereum, while the card controls the signing authority for the Ethereum address.
Each Cryptnox card contains an EAL6+-certified chip. For a BAND holder, that chip-level protection is relevant because the key for the Ethereum BAND address is generated and retained inside the secure element instead of being handled as a normal phone or computer file.
Unlock approval can use the phone’s fingerprint or face unlock through the Cryptnox app. The card itself has no fingerprint reader, face sensor, or other body-scanning component. That division keeps the BAND key on the smart card while the phone provides the local app unlock experience.
The card is dual-interface: it works as a contact and NFC smart card. For a BAND transaction, you can tap the card to a phone or insert it into a reader, depending on the workflow you are using with the Cryptnox app and connected Ethereum tools.
The Dual-Card Set ships uninitialised, which matters for BAND buyers who want the backup created before funds arrive. During setup, the wallet seed is generated inside the secure elements of both cards. The second card is therefore the backup for the same Ethereum wallet that can hold ERC-20 BAND.
By default, this setup does not require writing down a recovery phrase. The BAND-relevant benefit is straightforward: the Ethereum address used for ERC-20 BAND is backed by the second card from the start, because both cards are initialised together as one wallet setup.
Importing a BIP39 recovery phrase with 12 or 24 words is available as an advanced option, but it is not the default path for the Dual-Card Set. Buyers who want the standard Cryptnox BAND setup use the two-card initialisation flow so the backup is part of the wallet creation step.
You can buy the Cryptnox Crypto Hardware Wallet – Dual-Card Set directly from the product page. For ERC-20 BAND, the two-card design is useful because the asset is controlled by the Ethereum key created during that initialisation.
The free Cryptnox app is available on iOS and Android, and BAND holders use it with the card-controlled Ethereum account. The app connects to Web3 through WalletConnect and works with MetaMask, which is useful when ERC-20 BAND must be added by contract before it appears in an Ethereum token view.
For BAND, MetaMask or a WalletConnect session is the interface layer; the Cryptnox card remains the place where the Ethereum key is created and kept. Adding the BAND contract in a Web3 interface does not move the key into that interface. It only tells the Ethereum tool which ERC-20 token to use with the card-controlled address.
The Cryptnox hardware wallet collection gives broader context for buyers comparing asset routes before choosing a card wallet. BAND should be evaluated as an Ethereum ERC-20 holding on Cryptnox, not as the native BandChain coin.
That route differs from assets such as Polygon, where the Polygon hardware wallet page covers an EVM-style network case, and TRON, where the TRON hardware wallet page covers a different address environment. If you also compare native asset custody, the Bitcoin hardware wallet page is a separate reference point.
Cryptnox is a fit for BAND holders whose BAND is on Ethereum as the ERC-20 token and who want the controlling Ethereum key kept on a smart card. The product is a Swiss-engineered contact and NFC smart card set, so the BAND workflow is built around tapping to a phone or inserting the card into a reader.
The reasons to choose it for BAND are specific: the supported route is ERC-20 BAND on Ethereum, the card uses a secure element with an EAL6+-certified chip, and the second card becomes the backup during the initial two-card setup. WalletConnect and MetaMask support also matter because BAND is added and used as an Ethereum token.
Cryptnox is not the right holding route for native BandChain BAND. If your BAND is already ERC-20 on Ethereum, Cryptnox gives you a card-protected way to manage the Ethereum address that controls it. If your BAND is native on BandChain, do not treat the Cryptnox Ethereum address as a BandChain receiving address.
No. Cryptnox holds BAND only as the ERC-20 token on Ethereum. Native BandChain BAND is not holdable on the card. When receiving BAND into a Cryptnox-controlled wallet, use the Ethereum/ERC-20 route and a 0x-prefixed 20-byte EVM address.
No. BAND is not pre-programmed. After the cards are initialised, add ERC-20 BAND once through Add a Token or Add a Network. Use Ethereum as the network and contract 0xba11d00c5f74255f56a5e366f4f77f5a186d7f55.
For the Cryptnox BAND route, add ERC-20 BAND on Ethereum with contract 0xba11d00c5f74255f56a5e366f4f77f5a186d7f55. The address you receive to should be a 0x-prefixed Ethereum address, not a native BandChain address.
The Ethereum private key that controls your ERC-20 BAND address is generated inside the card’s secure element and does not leave it. BAND itself is an Ethereum token balance, while the Cryptnox card controls the key used for that Ethereum address.
The Dual-Card Set is initialised before use, and the wallet seed is generated inside both secure elements during setup. The second card is the backup for the same wallet, including the Ethereum address that can receive ERC-20 BAND.
Yes. The Cryptnox app works with MetaMask and connects to Web3 through WalletConnect. For BAND, use those tools with the Ethereum ERC-20 route, then add the BAND contract if the token is not already available in the interface.
No, and on this network that is not a limitation. The Cryptnox wallet uses one address per chain. HD address rotation comes from Bitcoin’s UTXO model and the BIP32/BIP44/BIP49/BIP84 derivation scheme; on account-model networks each account is a single fixed address by design, so the question does not apply in the same way. Cryptnox’s single-address-per-chain behaviour matches how these networks work.
At the cryptography layer the card derives keys along BIP32 and SLIP-10 paths, one path per supported chain, though that is not exposed in the app as multi-address management.
Yes. Cryptnox ships worldwide from the official CRYPTNOX store. Orders to Switzerland, the European Union and the United States are dispatched from stock already held in each of those regions, so the parcel does not cross a customs border into your country and there are no import duties to pay. Orders to other destinations are shipped internationally, and any import duties or local taxes are set by the destination country and are the recipient’s responsibility. Current shipping rates are shown at checkout.