Yes. The Cryptnox Crypto Hardware Wallet – Dual-Card Set supports crvUSD by adding it once as an Ethereum ERC-20 token through Add a Network or Add a Token. crvUSD is not pre-programmed on the cards. Use contract 0xf939E0A03FB07F59A73314E73794Be0E57ac1b4E and a 0x-prefixed 20-byte EVM address. Private keys are generated inside the secure element and never leave it, while the second card is created as the backup during setup.
CRYPTNOX products are also available worldwide through our official Amazon stores.
crvUSD is held on Cryptnox as an ERC-20 token on Ethereum. The cards do not arrive with crvUSD already enabled, so the first crvUSD-specific step is to add the token once using its Ethereum contract address. The contract to add is 0xf939E0A03FB07F59A73314E73794Be0E57ac1b4E, which is the crvUSD token contract shown on Etherscan.
Use Add a Network or Add a Token, depending on the app view you are using. The receiving address for crvUSD is not a separate crvUSD address type; it is a 0x-prefixed 20-byte EVM address on Ethereum. The asset-specific detail is the ERC-20 contract that tells the wallet interface which token balance to show for that Ethereum address.
If you want to check asset coverage before setting up the token, use the Cryptnox coin and blockchain support page together with the crvUSD contract above. That is the practical check for a token that is added manually rather than displayed on the cards before initialization.
Before receiving crvUSD, verify that the receiving account is an Ethereum account and that the visible token is crvUSD on Ethereum. The address should begin with 0x and follow the 20-byte EVM address format. Many ERC-20 tokens use the same Ethereum address format, so the contract address is the detail that identifies crvUSD in the wallet interface.
For crvUSD, the contract separates this token from any other ERC-20 token shown under the same Ethereum address. Confirm Ethereum as the chain, confirm the 0x receiving address, and confirm 0xf939E0A03FB07F59A73314E73794Be0E57ac1b4E as the token contract before moving value.
The Cryptnox card protects the Ethereum private key that controls the 0x address. The crvUSD contract identifies the asset balance connected to that address. Keeping those two details separate helps you treat crvUSD as an Ethereum ERC-20 token rather than as an asset with its own native address family on the card.
When crvUSD is held through Cryptnox, control depends on the Ethereum private key for the 0x address that receives the ERC-20 token. That private key is generated inside the card secure element and never leaves it. The app can help you view the account and prepare the workflow, while the sensitive key material remains inside the secure element rather than being copied into the phone app.
The chip platform used by the card is an EAL6+-certified chip. That matters for crvUSD because the token balance follows the Ethereum account controlled by the card, not a password stored in a software interface. The crvUSD token contract can be public; the private key that controls the address holding crvUSD remains protected inside the secure element.
The product for this setup is the Cryptnox Crypto Hardware Wallet – Dual-Card Set. For a crvUSD buyer, the important distinction is that adding the ERC-20 token changes the displayed asset, while the hardware wallet security model protects the Ethereum key that controls the address.
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 state. For crvUSD, that means the backup card protects access to the Ethereum account that can hold the ERC-20 token after it has been added.
The default setup does not require writing down a recovery phrase before you can use the wallet. The backup is the second card created during initialization. That is especially relevant for an ERC-20 token such as crvUSD, because the asset display can be re-added by contract, while the critical access requirement is control of the same Ethereum account.
Importing a 12- or 24-word BIP39 recovery phrase is an advanced option. The default Dual-Card Set setup is different: both cards start uninitialised, and the wallet state is created inside the two secure elements. If you are setting up crvUSD for the first time, follow the product guidance in the Cryptnox hardware wallet tutorials when initializing the cards and adding the Ethereum token.
The free Cryptnox app is available on iOS and Android. For crvUSD, the app is used to manage the card flow, add the Ethereum ERC-20 token when needed, unlock using the phone’s biometrics, and connect to Web3. The card remains the signing device, and the private key for the Ethereum address remains inside the secure element.
Cryptnox connects to Web3 through WalletConnect and works with MetaMask. That gives a practical route for crvUSD because the token is added as an ERC-20 on Ethereum and is used through a 0x-prefixed EVM address. After crvUSD is added with contract 0xf939E0A03FB07F59A73314E73794Be0E57ac1b4E, the card-controlled Ethereum account is the account to use in the connected flow.
This workflow keeps the crvUSD token addition separate from key custody. The app handles the Ethereum token view and Web3 connection; the card protects the private key for the Ethereum address holding crvUSD.
For crvUSD on Ethereum, Cryptnox uses a contact and NFC smart card format. You can tap the card to a phone or insert it into a reader. The card is dual-interface, so crvUSD use is not limited to one connection method. The asset remains the Ethereum ERC-20 token at contract 0xf939E0A03FB07F59A73314E73794Be0E57ac1b4E; the card format changes how you carry and use the signing device.
The card-sized format is useful when you want a hardware wallet that fits like a payment card while still protecting the Ethereum key for a crvUSD address. When using a phone, unlock is handled through the phone’s biometrics in the Cryptnox app. The card itself does not scan a fingerprint or face. Its role in a crvUSD flow is to hold the key in the secure element and participate in signing when the app requests the card.
The cards are made in Switzerland and the product is Swiss-engineered. For a buyer holding crvUSD, the origin detail sits alongside the practical setup details: add crvUSD manually as an Ethereum ERC-20 token, confirm the 0x receiving address, and use the two-card setup as the default backup model.
crvUSD should be planned as an Ethereum ERC-20 token, even if you use the same Cryptnox Dual-Card Set for more than one asset. The crvUSD setup depends on the Ethereum chain, the ERC-20 standard, the 0x-prefixed address, and the contract 0xf939E0A03FB07F59A73314E73794Be0E57ac1b4E. Those are the details to keep in front of you before receiving crvUSD.
If crvUSD is one part of a wider wallet purchase, the Cryptnox hardware wallet hub gives the broader view of the hardware wallet category. Buyers comparing crvUSD storage with other asset setups can also review the dedicated Cryptnox Polygon hardware wallet and Cryptnox Bitcoin hardware wallet guides instead of assuming every asset is added like an Ethereum ERC-20 token.
For another EVM-style comparison, the Cryptnox Tron hardware wallet guide can help you separate chain setup from token setup, while the Cryptnox Ronin hardware wallet guide shows why every asset page should be checked on its own terms. The crvUSD decision comes down to a precise route: add the token once, verify the Ethereum contract, and use the card-controlled 0x address.
No. crvUSD is not pre-programmed on the cards. Add it once as an Ethereum ERC-20 token through Add a Network or Add a Token. Use contract 0xf939E0A03FB07F59A73314E73794Be0E57ac1b4E and receive to a 0x-prefixed 20-byte EVM address.
For crvUSD on Ethereum, add contract 0xf939E0A03FB07F59A73314E73794Be0E57ac1b4E. The token standard is ERC-20 on Ethereum. The receiving address is a 0x-prefixed 20-byte EVM address controlled by the private key generated inside the card's secure element.
Yes. The Dual-Card Set ships uninitialised, and the seed is generated inside both secure elements during setup. The second card is the backup for the same wallet state. For crvUSD, that backup protects access to the Ethereum account that holds the ERC-20 token.
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.
No. Unlock uses the phone's biometrics through the Cryptnox app. The card itself has no biometric sensor. In a crvUSD flow, the card's role is to keep the Ethereum private key inside the secure element and participate in signing through the smart card process.
Yes. The free Cryptnox app on iOS and Android connects to Web3 through WalletConnect and works with MetaMask. Add crvUSD as an Ethereum ERC-20 token with the correct contract first, then use the app and card flow with the 0x address controlled by the card.
crvUSD uses the Ethereum address format because it is held as an ERC-20 token on Ethereum. The receiving address is a 0x-prefixed 20-byte EVM address. The crvUSD-specific setup detail is the token contract: 0xf939E0A03FB07F59A73314E73794Be0E57ac1b4E.
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.