Yes. Cryptnox can hold ZORA as the ERC-20 token on Base after you add the Base network or add the ZORA token once. Use the Base contract 0x1111111111166b7fe7bd91427724b487980afc69 and a 0x-prefixed 20-byte EVM receiving address. ZORA is not pre-programmed on the cards, and the official Solana representation is not holdable. Private keys for the ZORA-capable account are generated inside the secure element and never leave it.
CRYPTNOX products are also available worldwide through our official Amazon stores.
ZORA is held on Cryptnox through one route: the Base ERC-20 token at 0x1111111111166b7fe7bd91427724b487980afc69. That contract is the token identifier to use when you add ZORA to the Cryptnox app, and the receiving account is an EVM account shown as a 0x-prefixed 20-byte address.
The cards do not arrive with ZORA already set up. Add Base through Add a Network, or add ZORA through Add a Token, then verify the contract before receiving. This is the practical difference between using the Base ERC-20 token and confusing it with the official Solana representation, which is not holdable on Cryptnox.
When comparing ZORA with other assets, use the Cryptnox coin and blockchain support page to check the supported asset route before moving funds. For ZORA, the route to use is Base ERC-20.
ZORA should not be added by ticker alone. On Cryptnox, the holdable asset is the Base ERC-20 token, so the contract 0x1111111111166b7fe7bd91427724b487980afc69 is the value that distinguishes the ZORA token you intend to add. A matching ticker without the Base contract is not enough for this setup.
The Zora support article identifies ZORA token information that helps distinguish Base from other representations. The zora-token repository is also useful when checking the token contract.
The token contract is public information that identifies ZORA on Base. The sensitive part is not the contract; it is the private key for the EVM account that can receive and control the token. Cryptnox keeps that private key inside the secure element.
A ZORA balance on Base is controlled by the private key for the EVM account that receives the token. In the Cryptnox Crypto Hardware Wallet – Dual-Card Set, private keys are generated inside the secure element and never leave it. The ZORA contract identifies the asset, while the EVM account key controls access to the 0x-prefixed address that can hold it.
The card uses an EAL6+-certified chip. That chip-level property belongs to the secure-element platform used for the ZORA-controlling keys. The card is a contact and NFC smart card, so you can tap it to a phone or insert it into a reader.
The Base contract address for ZORA is not a secret. You use it to add or verify the token. The private key for the receiving EVM account is the part that must remain protected, and Cryptnox generates that key inside the secure element.
Unlock can use the fingerprint or face unlock already set up on your phone through the Cryptnox app. The card itself has no fingerprint or face sensor. The phone handles the unlock step, while the card remains the place where the private key for the ZORA-capable account is kept.
If you are comparing ZORA with another EVM-style asset, the Polygon hardware wallet page is a separate place to review that asset. ZORA still requires its own Base contract and one-time token addition.
The Dual-Card Set ships uninitialised, which matters for a ZORA holder because the account is created during setup rather than arriving with a prewritten recovery phrase. During setup, the seed is generated inside both secure elements, so the second card is the backup for the same EVM account structure that can hold ZORA on Base.
By default, there is no recovery phrase to write down for the ZORA setup. The backup is the second card created from the same internally generated seed. If ZORA is added after setup, both cards correspond to the same underlying account structure, so the backup card is not a separate ZORA destination.
ZORA on Cryptnox depends on three matching details: Base as the chain, ERC-20 as the standard, and 0x1111111111166b7fe7bd91427724b487980afc69 as the token contract. A useful backup must preserve access to the same EVM account used for that route. The Dual-Card Set creates that backup during the same setup flow.
Importing a 12/24-word BIP39 seed is an advanced option, not the default ZORA flow. A buyer using the standard Dual-Card Set starts with uninitialised cards and lets the two secure elements generate the seed internally. The product for this flow is the Cryptnox Crypto Hardware Wallet – Dual-Card Set.
The ZORA setup starts in the free Cryptnox app for iOS and Android because ZORA is not pre-programmed on the cards. Add Base through Add a Network, or add ZORA through Add a Token, then use 0x1111111111166b7fe7bd91427724b487980afc69 to identify the token. The app is where the ZORA route is selected, while the account keys remain inside the card’s secure element.
The app connects to Web3 through WalletConnect and works with MetaMask. For ZORA, that means the EVM account controlled by the card can be used in a Web3 session after the Base ERC-20 token has been added with the correct contract. The Web3 connection does not change the ZORA route: it remains Base ERC-20.
If you want product steps before adding the token or connecting the account, the Cryptnox hardware wallet tutorials are the right place to start. If you are still comparing asset pages, the Cryptnox hardware wallet asset hub groups related hardware wallet options.
ZORA should be treated as a Base ERC-20 setup, not as a generic multi-chain token entry. The official Solana representation exists, but it is not the representation held on Cryptnox. The receiving address format gives the clearest signal: ZORA on Cryptnox uses a 0x-prefixed EVM address.
This makes ZORA a route-specific setup. If you are checking another asset, compare it separately rather than reusing the ZORA contract or address assumptions. The TRON hardware wallet page and the Ronin hardware wallet page are separate asset pages, while ZORA remains tied to the Base contract shown here.
The ticker ZORA is not enough to choose a transfer route. The route must match Base ERC-20, and the token contract must match 0x1111111111166b7fe7bd91427724b487980afc69. If the sending service asks for a non-EVM destination, that request does not match the Cryptnox ZORA setup.
Bitcoin is also a separate comparison because it is not an ERC-20 token. Buyers comparing card-based storage for different asset types can review the Bitcoin hardware wallet page separately, while using the ZORA flow only for the Base ERC-20 token.
This setup is for a buyer who wants to hold ZORA on Base with a card-controlled EVM account. It is not a preloaded ZORA experience. You add Base or add the ZORA token once, verify the contract, and use the 0x-prefixed account controlled by the Cryptnox card.
The form factor fits a ZORA holder who wants a smart card. The card is dual-interface: tap it to a phone for mobile use, or insert it into a reader when that workflow is preferred. In both workflows, the private keys controlling the ZORA-capable EVM account are generated inside the secure element and never leave it.
Cryptnox is Swiss-engineered, and the ZORA workflow depends on three product details working together: secure-element key generation for the EVM account, a second card backing up the same internally generated seed, and contact plus NFC smart-card access for the Base ERC-20 token route.
Yes. Cryptnox can hold ZORA as the ERC-20 token on Base after you add the Base network or add the ZORA token once. Use the contract 0x1111111111166b7fe7bd91427724b487980afc69 and a 0x-prefixed 20-byte EVM receiving address.
No. ZORA is not pre-programmed on the cards. Add Base through Add a Network or add ZORA through Add a Token in the Cryptnox app, then verify that the contract is 0x1111111111166b7fe7bd91427724b487980afc69 before receiving ZORA.
No. The official Solana representation of ZORA exists, but it is not holdable on Cryptnox. The ZORA route for Cryptnox is the Base ERC-20 token, using the 0x1111111111166b7fe7bd91427724b487980afc69 contract and an EVM address.
Use a 0x-prefixed 20-byte EVM address for ZORA on Base. The token contract to add or verify is 0x1111111111166b7fe7bd91427724b487980afc69. A Solana destination does not match the Cryptnox ZORA setup.
The private keys for the EVM account that can hold ZORA are generated inside the secure element and never leave it. The card uses an EAL6+-certified chip. The ZORA contract is public, but the private key controlling the 0x-prefixed account stays inside the card.
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 generated seed, so it backs up the EVM account that can hold ZORA on Base.
Yes. The free Cryptnox app connects to Web3 through WalletConnect and works with MetaMask. For ZORA, add the Base ERC-20 token with the correct contract first, then use the card-controlled EVM account in the Web3 session.
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.