The Cryptnox Crypto Hardware Wallet – Dual-Card Set can hold 0x (ZRX) as an Ethereum ERC-20 token after you add it once through Add a Network or Add a Token. ZRX is not pre-programmed on the cards. Use the Ethereum contract address 0xE41d2489571d322189246DaFA5ebDe1F4699F498 and a 0x-prefixed 20-byte EVM address. The secure element creates the private keys and keeps them inside it.
Buy it from CRYPTNOX shop directly
Accepts:
Preferred shopping solution for US:
Also available on other Amazon shops:
DE, FR, IT, BE, SE, ES, PL, NL, CA, MX, AU
0x, ticker ZRX, is holdable with the Cryptnox Crypto Hardware Wallet – Dual-Card Set as an ERC-20 token on Ethereum. The ZRX entry is added once through Add a Network or Add a Token; it is not pre-programmed on the cards before setup. That distinction matters because ZRX is identified by its Ethereum token contract, while the card protects the private keys for the Ethereum address that receives and sends the token.
The contract to enter or verify for ZRX is 0xE41d2489571d322189246DaFA5ebDe1F4699F498 on Ethereum. The receiving address format is the normal EVM format for Ethereum accounts: a 0x-prefixed 20-byte address. Before sending ZRX, check both the contract and the address format, because the ZRX support route depends on Ethereum ERC-20 handling rather than a separate native ZRX chain.
If you hold ZRX alongside other assets, confirm each asset’s route on the Cryptnox coin and blockchain support page before preparing a transfer. ZRX should be treated specifically as the Ethereum ERC-20 token at its contract address, not as a generic token name without a chain and contract check.
ZRX support starts with Ethereum because the supported form is the ERC-20 token on Ethereum. The card does not need a preloaded ZRX app or a separate ZRX network to hold it. Instead, the Ethereum address is controlled by keys kept in the secure element, and the ZRX token entry tells the app which ERC-20 contract represents the asset.
This is the practical difference between holding an Ethereum ERC-20 token and holding an asset with a separate native network. With ZRX, the important asset-specific fields are chain, contract, token standard, and address format. The public asset listing on CoinGecko identifies 0x by the ZRX ticker, while the Ethereum contract gives the exact token address to use during setup.
For a buyer, the main point is that ZRX support is deliberate rather than automatic. After setup, the card is protecting the Ethereum private keys, and the ZRX token record identifies the balance and transaction context for the ERC-20 token at 0xE41d2489571d322189246DaFA5ebDe1F4699F498.
When ZRX is held through Cryptnox, the security boundary is the secure element inside the card. The secure element creates the private keys for the Ethereum address and keeps those keys inside the card. ZRX transactions are then signed from that protected environment, so the private key for the address used with the ERC-20 token is not exposed to the phone app.
The card uses an EAL6+-certified chip. For a ZRX holder, that chip is the place where the Ethereum account key material is created and retained. The app is used for management, token setup, and the user flow around approving actions, while the secure element remains the place that holds the keys controlling the 0x-prefixed address.
Unlocking can use the phone’s face or fingerprint check through the Cryptnox app. The card itself has no fingerprint reader or face sensor. That separation is important in the ZRX flow: the phone helps with access through the app, and the card protects the private keys for the Ethereum address that holds the ZRX ERC-20 token.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set ships uninitialised. During the setup flow, the seed is created inside both secure elements. The second card is therefore the backup for the Ethereum address that can hold ZRX after the ERC-20 token is added.
This matters for ZRX because the token record and the address control are different parts of the experience. Adding ZRX through Add a Network or Add a Token identifies the ERC-20 token at 0xE41d2489571d322189246DaFA5ebDe1F4699F498. The underlying Ethereum address remains controlled by the keys in the card pair. If ZRX is added after the card pair is initialised, the backup remains the second card because it was part of the same seed generation flow.
The default setup does not ask you to write down a recovery phrase. The card pair is the default backup model. Importing a BIP39 phrase is available as an advanced option, but it is not the standard path for a new Dual-Card Set used to hold ZRX.
The free Cryptnox app is available on iOS and Android. For ZRX, the app is where you initialise the Dual-Card Set, add the Ethereum ERC-20 token entry, and manage the wallet flow around the 0x-prefixed address. Once the token entry is added, the card continues to protect the private keys for that Ethereum address.
The card is a contact and NFC smart card. You can tap it to a phone, or insert it into a reader. That dual-interface format is useful for a ZRX buyer who wants a card-shaped wallet while still using Ethereum ERC-20 token details in the app.
For Web3 sessions, the Cryptnox app connects through WalletConnect and works with MetaMask. In a ZRX context, this means you can connect the Ethereum address used for the ZRX ERC-20 token while the private keys stay inside the secure element. If you are setting up the product for the first time, the Cryptnox hardware wallet tutorials are the right place to review the app and card setup flow before adding ZRX.
The product for this ZRX setup is the Cryptnox Crypto Hardware Wallet – Dual-Card Set. It is the card pair used for the backup model described above: the seed is created inside both secure elements during setup, and the second card is the backup for the Ethereum address that can hold ZRX.
The cards are Swiss-engineered, and the cards are made in Switzerland. For ZRX, the buying decision is not whether the token is already present on the cards. It is not. The relevant point is that ZRX can be added once as the Ethereum ERC-20 token at 0xE41d2489571d322189246DaFA5ebDe1F4699F498, while the private keys for the receiving address remain inside the secure element.
If you are comparing ZRX with other supported assets before buying, the Cryptnox hardware wallet collection is the parent hub for related wallet pages. Use it when you want to compare this Ethereum ERC-20 token route with pages for assets that use different setup details.
ZRX should be set up as an Ethereum ERC-20 token, so its setup is driven by the Ethereum contract and a 0x-prefixed EVM address. That makes it different from asset pages where the key setup question is a separate chain, a different address convention, or a network-specific route.
If you also hold Polygon assets, compare ZRX’s Ethereum ERC-20 setup with the Cryptnox hardware wallet for Polygon page. The comparison is useful because ZRX’s contract address belongs to Ethereum, and the ZRX page should not be used as a substitute for a Polygon-specific setup check.
For a sharper contrast, compare ZRX with the Cryptnox hardware wallet for Tron page or the Cryptnox hardware wallet for Bitcoin page. Those pages are not governed by the ZRX Ethereum ERC-20 contract. If your holdings include Ronin as well, the Cryptnox hardware wallet for Ronin page gives that asset its own setup context. Keep the ZRX rule simple: Ethereum, ERC-20, contract 0xE41d2489571d322189246DaFA5ebDe1F4699F498, and a 0x-prefixed 20-byte EVM address.
No. ZRX is not pre-programmed on the cards. You add it once through Add a Network or Add a Token. The supported form is 0x (ZRX) as an ERC-20 token on Ethereum at contract 0xE41d2489571d322189246DaFA5ebDe1F4699F498.
Use a 0x-prefixed 20-byte EVM address for ZRX. The supported ZRX route is Ethereum ERC-20, so the receiving address should be an Ethereum-style address. Before receiving funds, also verify the ZRX contract address: 0xE41d2489571d322189246DaFA5ebDe1F4699F498.
The secure element creates the private keys and keeps them inside it. For ZRX, those keys control the Ethereum address used with the ERC-20 token. The card uses an EAL6+-certified chip, and the app manages the setup and approval flow.
The Dual-Card Set ships uninitialised. During setup, the seed is created inside both secure elements, so the second card is the backup. After ZRX is added as an Ethereum ERC-20 token, that backup still protects the same underlying Ethereum address.
No recovery phrase is written down by default in the Dual-Card Set setup. The seed is created inside both secure elements, and the second card serves as the backup. Importing a BIP39 phrase is available as an advanced option instead of the default generation flow.
No. The card has no fingerprint reader or face sensor. Unlocking can use the phone’s face or fingerprint check through the Cryptnox app, while the card protects the private keys for the Ethereum address used with ZRX.
Yes. The free Cryptnox app on iOS and Android connects to Web3 through WalletConnect and works with MetaMask. For ZRX, add the Ethereum ERC-20 token first, then use the app flow with the keys kept inside the secure element.
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.
