Yes. Cryptnox can hold cbETH by adding it once as an ERC-20 token on Ethereum, using contract 0xBe9895146f7AF43049ca1c1AE358B0541Ea49704. cbETH is not pre-programmed on the cards. Your receiving address is a 0x-prefixed 20-byte EVM address, and the private keys for that Ethereum address are generated inside the secure element and never leave it. During setup, the second card becomes the backup for the same wallet.
CRYPTNOX products are also available worldwide through our official Amazon stores.
cbETH, Coinbase Wrapped Staked ETH, is held with Cryptnox as an ERC-20 token on Ethereum. It is not a separate chain in the card setup, and it is not pre-programmed before the Dual-Card Set is initialized. The practical route is Ethereum first, then cbETH as the token identified by its Ethereum contract.
Coinbase presents cbETH as Coinbase Wrapped Staked ETH. For wallet setup, the important data is the chain, token standard, contract, and address format. The cbETH ERC-20 contract to add is 0xBe9895146f7AF43049ca1c1AE358B0541Ea49704.
If you are checking where cbETH fits before buying, the Cryptnox coin and blockchain support page is the useful place to compare supported network and token routes. For cbETH, the route is Ethereum first, then the ERC-20 token entry for the cbETH contract.
cbETH should be added by its Ethereum contract, not by name alone. The contract 0xBe9895146f7AF43049ca1c1AE358B0541Ea49704 is shown for cbETH on Etherscan’s token page for that address. Using that contract keeps the cbETH entry tied to the ERC-20 token on Ethereum.
Your cbETH receiving address should look like an Ethereum address: it begins with 0x and uses the 20-byte EVM address format. That address is controlled by the private key in the card’s secure element. cbETH transfers use that Ethereum-style address because cbETH is an ERC-20 token on Ethereum.
Adding cbETH does not create a different address family. It tells the app or Web3 wallet to display and use the cbETH ERC-20 token on the Ethereum account controlled by the card. ETH and cbETH can be shown in the same Ethereum account environment, but cbETH remains tied to its own contract.
This is the key setup point for a cbETH buyer. The Cryptnox card protects the Ethereum private key, while the token entry tells the wallet interface which ERC-20 balance to show for contract 0xBe9895146f7AF43049ca1c1AE358B0541Ea49704.
Start with the free Cryptnox app on iOS or Android. For cbETH, add the Ethereum route if your app flow requires it, then add cbETH as an ERC-20 token using contract 0xBe9895146f7AF43049ca1c1AE358B0541Ea49704. The cards do not arrive with cbETH already configured, so the token entry is expected.
The Cryptnox hardware wallet tutorials are the right next step for app and card setup guidance. The cbETH-specific part remains the token data: Ethereum as the chain, ERC-20 as the standard, and the cbETH contract as the identifier.
After cbETH is added, the Cryptnox app connects to Web3 via WalletConnect and works with MetaMask. For cbETH, that means the Ethereum address controlled by the card can be used in those wallet flows while the token stays tied to the cbETH ERC-20 contract.
cbETH is controlled through an Ethereum private key because the asset is held at a 0x-prefixed Ethereum address. In the Cryptnox card pair, private keys are generated inside the secure element and never leave it. The card signs for the Ethereum address used with cbETH without exposing that private key outside the secure element.
The chip platform uses an EAL6+-certified chip. For cbETH storage, the protected item is the Ethereum private key that controls the address where the ERC-20 token is held.
The Dual-Card Set arrives uninitialised. During the standard setup, the seed is created inside both secure elements, so the second card is the backup for the same wallet. For cbETH, the backup card protects access to the same Ethereum address used for the cbETH token.
A written recovery phrase is not the normal setup step. Importing a BIP39 recovery phrase is available as an advanced option, but the usual Dual-Card Set flow uses the two secure elements as the backup structure. That matters for cbETH because the same 0x-prefixed Ethereum address must remain under the same private-key control.
The Cryptnox form factor is a contact and NFC smart card. For cbETH, that gives two ways to work with the same Ethereum address: tap the card to a phone, or insert it into a reader. The asset route does not change between those interfaces; cbETH remains an ERC-20 token on Ethereum with contract 0xBe9895146f7AF43049ca1c1AE358B0541Ea49704.
Unlock is handled through the phone’s biometrics in the Cryptnox app. The card itself has no biometric sensor. In cbETH use, the phone unlock step is part of the app interaction, while the card remains the hardware holder for the Ethereum private key associated with the 0x-prefixed address.
WalletConnect and MetaMask support are useful when you need cbETH visible in an Ethereum wallet workflow. The buyer detail stays the same: if cbETH is not visible at first, add it as the Ethereum ERC-20 token with the correct contract rather than treating it as another network.
The wider Cryptnox hardware wallet collection is useful when comparing this cbETH route with other asset pages. cbETH belongs in the Ethereum ERC-20 category, not in a non-EVM address family.
The product to buy for this cbETH setup is the Cryptnox Crypto Hardware Wallet – Dual-Card Set. The buyer receives two uninitialised smart cards, then sets up the wallet so both secure elements hold the generated seed. For cbETH, that backup arrangement applies to the Ethereum address that receives the ERC-20 token.
The cards are Swiss-engineered. The buyer still needs to add cbETH after setup because the token is not pre-programmed. That one-time addition uses Ethereum, ERC-20, the 0x-prefixed address format, and the cbETH contract.
This buying choice is different from looking for a cbETH-only card. Cryptnox secures the Ethereum address, and cbETH is added as the ERC-20 token that lives at contract 0xBe9895146f7AF43049ca1c1AE358B0541Ea49704.
cbETH uses Ethereum’s 0x-prefixed EVM address format. That makes its setup different from assets that do not use Ethereum addresses, and also different from chain-native assets where no ERC-20 contract is entered. For cbETH, the main setup task is to confirm the Ethereum token contract before receiving or using the asset.
If you hold assets beyond cbETH, separate the address family from the token name. The Cryptnox Bitcoin hardware wallet page shows a non-EVM route, while the Cryptnox Tron hardware wallet page covers a different chain environment. Those routes should not be mixed with the 0x-prefixed Ethereum address used for cbETH.
For EVM planning, compare cbETH with network-focused pages such as the Cryptnox Polygon hardware wallet page and the Cryptnox Ronin hardware wallet page. cbETH remains on Ethereum in this setup, so the token contract is the deciding detail.
Use Ethereum, add cbETH as an ERC-20 token, confirm 0xBe9895146f7AF43049ca1c1AE358B0541Ea49704, and receive only to a 0x-prefixed 20-byte EVM address controlled by the Cryptnox card pair.
No. cbETH is not pre-programmed on the cards. Add it once as an ERC-20 token on Ethereum, using contract 0xBe9895146f7AF43049ca1c1AE358B0541Ea49704. If your setup does not already include Ethereum, use Add a Network before adding the cbETH token.
Use the Ethereum ERC-20 contract 0xBe9895146f7AF43049ca1c1AE358B0541Ea49704. That contract identifies cbETH, Coinbase Wrapped Staked ETH, on Ethereum. Entering the contract helps keep cbETH separate from ETH and from other Ethereum token entries.
cbETH uses an Ethereum-style address because it is an ERC-20 token on Ethereum. The receiving address is a 0x-prefixed 20-byte EVM address. Do not send cbETH to a Bitcoin, Tron, or other non-Ethereum address format.
During the standard Dual-Card Set setup, the seed is generated inside both secure elements. The second card is the backup for the same wallet. For cbETH, that means the backup card protects access to the same Ethereum address used with the ERC-20 token.
No. The private keys for the Ethereum address used with cbETH are generated inside the secure element and never leave it. The app and Web3 connection provide the interface, while the card protects the key that controls the 0x-prefixed address.
Yes. The free Cryptnox app connects to Web3 via WalletConnect and works with MetaMask. cbETH still needs to be added as an ERC-20 token on Ethereum with contract 0xBe9895146f7AF43049ca1c1AE358B0541Ea49704 before that token appears in the workflow.
The normal Dual-Card Set setup creates the seed inside both secure elements, making the second card the backup. Importing a BIP39 recovery phrase is an advanced option, but it is not the default way to set up cbETH with the card pair.
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.