Yes. Cryptnox supports Boba Network (BOBA) as an ERC-20 token on Ethereum after you add the token once with its contract address. BOBA is not pre-programmed on the card. Use contract 0x42bbfa2e77757c645eeaad1655e0911a7553efbc and an 0x-prefixed 20-byte EVM address. Private keys are generated inside the secure element and never leave it when the card signs BOBA transactions.
CRYPTNOX products are also available worldwide through our official Amazon stores.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set is for holding BOBA as an Ethereum ERC-20 token with the private key generated inside the card’s secure element. BOBA is added by contract address after setup, not selected from a pre-programmed card profile. The Ethereum contract to add is 0x42bbfa2e77757c645eeaad1655e0911a7553efbc, and Etherscan lists the BOBA token contract at that address on Ethereum.
You can buy the set through the Cryptnox Crypto Hardware Wallet – Dual-Card Set product page. The Dual-Card Set ships uninitialised, and the wallet seed is created during setup inside both secure elements. For a BOBA holder, that means the Ethereum account that will later display BOBA is created when you initialise the two-card wallet set.
BOBA is not enabled before setup. Add it once through “Add a Token” or the relevant “Add a Network” route, then use the Ethereum-style receiving address that starts with 0x. The product is a contact and NFC smart card: tap the card to a phone for mobile use, or insert it into a reader for contact use.
BOBA support on Cryptnox follows the Ethereum token route. The asset is held as BOBA ERC-20 on Ethereum, so setup depends on the token contract and the Ethereum account controlled by your Cryptnox cards. The receiving address is an 0x-prefixed 20-byte EVM address.
The free Cryptnox app is available on iOS and Android. It connects to Web3 through WalletConnect and works with MetaMask, so a BOBA holder can use an Ethereum account controlled by the card while working with interfaces that expect WalletConnect or MetaMask. The private key remains inside the secure element when the card signs.
For the wider Cryptnox asset list, use the Cryptnox coin and blockchain support page. BOBA should be treated as an Ethereum ERC-20 token on that setup path, not as a separate address family.
When you create the wallet for your BOBA-holding Ethereum account, private keys are generated inside the secure element and never leave it. The phone or Web3 interface can prepare the BOBA transaction, but the card performs the signing operation without exporting the private key.
The card uses an EAL6+-certified chip. For BOBA, the practical point is that the Ethereum private key controlling the 0x address is created and retained inside the secure element. The same 0x address format is used when receiving BOBA because BOBA is held as an ERC-20 token on Ethereum.
Unlock in the Cryptnox app can use the phone’s face or fingerprint check. The Cryptnox card has no fingerprint or face sensor. For a BOBA transaction, the app gives you the interface and unlock flow, while the card remains the signing device for the Ethereum account.
This separation matters when BOBA is handled through WalletConnect or MetaMask. A Web3 interface can request a BOBA-related Ethereum transaction, but approval still depends on the Cryptnox card signing for the 0x address that holds the token.
The Dual-Card Set is built around two cards from the start. The set ships uninitialised. During setup, the seed is generated inside both secure elements, so the second card is the backup for the same wallet. If your BOBA is received at the Ethereum address generated by that wallet, the second card backs up access to that same BOBA-holding account.
No recovery phrase has to be written down in the default setup flow. The backup is the second card because the seed is generated inside both secure elements during the same setup. Importing a 12 or 24 word BIP39 seed is an advanced option, not the default way to start a new Dual-Card Set.
If you want the setup sequence before adding the BOBA contract, follow the Cryptnox tutorials for hardware wallet products. Set up the Dual-Card Set first, then add BOBA with its Ethereum ERC-20 contract details.
The Cryptnox app is free on iOS and Android. For BOBA, the app path starts with the Ethereum account generated by your cards and the BOBA ERC-20 contract address. Once the token is added, the same 0x address is the address you use to receive BOBA.
When a Web3 service asks for a wallet connection, the Cryptnox app connects through WalletConnect and works with MetaMask. This lets a BOBA transaction be prepared in an Ethereum-style wallet interface while the private key remains inside the card. The card signs; the phone and connected interface display and route the transaction request.
The Boba Network documentation is the relevant technical reference for Boba Network. In the Cryptnox wallet, the support route for BOBA is the Ethereum ERC-20 token route.
The Cryptnox wallet is a contact and NFC smart card. For BOBA management on a phone, tap the card to the phone. For a contact workflow, insert the card into a reader. The same BOBA-holding Ethereum account remains tied to the private key generated inside the secure element.
The card format matters for a BOBA buyer because BOBA is an Ethereum token added by contract address, while the signing key is stored on the card. You can add the BOBA token in the app or through a connected wallet interface, but the private key for the 0x address never leaves the secure element.
Cryptnox is Swiss-engineered. For BOBA storage, the relevant distinction is operational: the ERC-20 token is displayed through an Ethereum account, and the signing key for that account is created and kept inside the card’s secure element.
If you are comparing hardware wallet routes for several assets, the Cryptnox hardware wallet collection hub helps you move from BOBA to other asset pages without changing the BOBA facts: on Cryptnox, BOBA is added as an ERC-20 token on Ethereum.
BOBA uses an Ethereum ERC-20 contract and an 0x-prefixed EVM address. That makes its setup different from assets that use another chain or a different address format. The important BOBA-specific step is adding contract 0x42bbfa2e77757c645eeaad1655e0911a7553efbc after the Dual-Card Set has been initialised.
If you also hold TRON, compare the BOBA token route with TRON hardware wallet support, because BOBA is described here as an ERC-20 token on Ethereum. If you are comparing EVM-related assets, the Polygon hardware wallet page is another useful reference point for understanding token and network setup differences.
BOBA also differs from Bitcoin because BOBA uses an Ethereum contract and an 0x address. The Bitcoin hardware wallet page covers a non-EVM asset route, while this BOBA page is centered on Ethereum ERC-20 handling. For another comparison path, the Ronin hardware wallet page covers a different asset route from BOBA on Ethereum.
For BOBA specifically, initialise the Dual-Card Set, add BOBA once as an Ethereum ERC-20 token, confirm the contract address, and use the 0x address controlled by your Cryptnox cards before receiving funds.
No. BOBA is not pre-programmed on the cards. After setting up the Dual-Card Set, add BOBA once as an ERC-20 token on Ethereum. Use contract 0x42bbfa2e77757c645eeaad1655e0911a7553efbc and confirm that the receiving address is an Ethereum-style 0x address controlled by your Cryptnox wallet.
Add BOBA as an ERC-20 token on Ethereum using contract 0x42bbfa2e77757c645eeaad1655e0911a7553efbc. The account address format is an 0x-prefixed 20-byte EVM address. Adding the token once lets the wallet interface display BOBA for the Ethereum account generated by your Cryptnox cards.
Your private keys are generated inside the card’s secure element and never leave it. The phone or connected wallet interface can help prepare and display the BOBA transaction, but the signing key remains in the card. BOBA is controlled through the Ethereum 0x address whose private key stays inside the secure element.
The Dual-Card Set ships uninitialised. During setup, the seed is generated inside both secure elements, so the second card is the backup for the same wallet. If BOBA is held at the Ethereum address generated by that wallet, the backup card corresponds to the same BOBA-holding account after setup.
No. In the default Dual-Card Set setup, the seed is generated inside both secure elements and the second card acts as the backup. Importing a 12 or 24 word BIP39 seed is available as an advanced option, but it is not the default setup route for a new BOBA-holding wallet set.
Yes. The free Cryptnox app on iOS and Android connects to Web3 through WalletConnect and works with MetaMask. For BOBA, add the ERC-20 token details first, then use the Ethereum 0x account controlled by your Cryptnox card when a Web3 interface asks for a wallet connection.
No. The Cryptnox card has no fingerprint or face sensor. Unlock can use the phone’s face or fingerprint check through the Cryptnox app, while the card remains the device that signs BOBA transactions. The BOBA signing key stays inside the secure element rather than being exported to the phone.
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.
