Yes. Polygon zkEVM is pre-programmed in the free Cryptnox app, so ETH on Polygon zkEVM can be managed without adding the network manually. The same network entry can also manage ERC-20 tokens deployed on Polygon zkEVM, with manual token addition available through Add a Token. The Cryptnox Crypto Hardware Wallet – Dual-Card Set generates private keys inside secure elements, and the second card is created as the backup during setup.
CRYPTNOX products are also available worldwide through our official Amazon stores.
Polygon zkEVM is already present in the free Cryptnox app on iOS and Android. For a buyer securing ETH on Polygon zkEVM, the important setup detail is simple: select the pre-programmed Polygon zkEVM network rather than creating a custom EVM network entry first. The app’s Polygon zkEVM route covers the network’s native coin and ERC-20 tokens deployed on that chain.
This matters because Polygon zkEVM is not just a token label. It is the chain context used by the app for balances, token entries, and transaction preparation. If an ERC-20 token belongs to Polygon zkEVM and is not already visible, it can be added manually with Add a Token. If a different EVM chain is needed later, Add a Network is available for that separate chain.
Buyers checking whether Polygon zkEVM fits alongside other assets can review the Cryptnox coin and blockchain support page before deciding which networks they want to manage with the card set.
ETH on Polygon zkEVM should be managed from the Polygon zkEVM network in the Cryptnox app. That chain entry is different from the separate Polygon network route used for Polygon PoS. The distinction is important when a buyer holds assets across multiple Polygon-related networks, because the app entry must match the chain where the asset is deployed.
For ERC-20 tokens, the chain matters as much as the token standard. An ERC-20 token deployed on Polygon zkEVM belongs under the Polygon zkEVM entry in the app. A token deployed on another EVM network belongs under that other network after it has been added or selected. The shared ERC-20 standard does not make different EVM networks the same place to manage assets.
Use Polygon zkEVM in the app when your ETH activity is on Polygon zkEVM. Use Add a Token when a Polygon zkEVM ERC-20 token needs to be added manually. Use Add a Network only when the chain itself is a different EVM network and is not already present.
If you also manage assets on Polygon PoS, compare this page with the Cryptnox hardware wallet page for Polygon so the Polygon zkEVM and Polygon PoS routes stay separated before you move or manage assets.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set ships uninitialised. During initialisation, the seed is generated inside both secure elements. That setup makes the second card the backup for the first card from the beginning, before ETH on Polygon zkEVM or Polygon zkEVM ERC-20 tokens are placed under the account.
The default setup does not require writing down a recovery phrase. For a Polygon zkEVM buyer, that changes the usual planning around ETH and ERC-20 storage: the backup is the second smart card created in the same setup process, not a later export of private-key material. Importing a 12- or 24-word BIP39 phrase is available as an advanced option, but it is not the default route for the Dual-Card Set.
When setting up the card pair for the first time, follow the Cryptnox startup guide before relying on the Polygon zkEVM account for ETH or ERC-20 management.
For ETH on Polygon zkEVM, private keys are generated inside the secure element and never leave it. The app can show the Polygon zkEVM network, prepare the account view, and provide the mobile interface, but the private-key material is not handed to the phone during Polygon zkEVM use.
The card uses an EAL6+-certified chip. That certification applies to the chip platform. For the buyer, the practical effect is that Polygon zkEVM approvals are tied to a dedicated secure element rather than to key material created on the mobile device.
Unlocking uses the phone’s biometrics through the Cryptnox app. The card itself has no biometric sensor. In the Polygon zkEVM workflow, that means the phone provides the app unlock flow while the smart card holds the private keys used for the account.
This separation is useful when one Polygon zkEVM account may manage ETH and several ERC-20 tokens. The app handles the chain and token interface, and the card keeps the account’s private keys inside the secure element.
The Cryptnox product is a contact and NFC smart card. For Polygon zkEVM management on a phone, tap the card to the phone while using the Cryptnox app. When a reader is used, insert the card into the reader. The card is dual-interface, so Polygon zkEVM use is not limited to only one smart-card contact method.
For ETH on Polygon zkEVM, the form factor affects the daily approval flow. The app presents the Polygon zkEVM account and token context, while the smart card protects the private keys for that account. The chain entry in the app and the physical card work together: Polygon zkEVM is selected in software, and the account’s key material remains in the card’s secure element.
The Dual-Card Set is sold as the Cryptnox Crypto Hardware Wallet – Dual-Card Set. Buyers choosing it for Polygon zkEVM get two uninitialised smart cards that are set up together, with the second card becoming the backup during initialisation.
The Cryptnox app connects to Web3 through WalletConnect and works with MetaMask. For Polygon zkEVM buyers, that provides a route when a Web3 session needs access to an account secured by the Dual-Card Set. The Polygon zkEVM network remains the chain context in the app, while the card protects the private keys for the account.
Use the pre-programmed Polygon zkEVM network when the Web3 activity is on Polygon zkEVM. If a different EVM network is needed, it can be added through Add a Network, and its native coin and ERC-20 tokens deployed on that chain can then be managed. This keeps Polygon zkEVM activity separate from other EVM chain entries inside the same app workflow.
If you are comparing Polygon zkEVM storage with other card-based crypto storage needs, the Cryptnox hardware wallet hub helps place this Polygon zkEVM page within the wider hardware wallet collection.
Polygon zkEVM should be selected for ETH and ERC-20 tokens deployed on Polygon zkEVM. If a buyer also holds assets on other chains, the chain-specific page matters because the app route and token handling can differ by network. Polygon zkEVM is pre-programmed, while other EVM networks can be added through Add a Network when needed.
For Polygon-related holdings outside Polygon zkEVM, use the separate hardware wallet page for Polygon. For TRON holdings, use the hardware wallet page for Tron rather than treating it as a Polygon zkEVM asset route. Buyers comparing Ronin can review the hardware wallet page for Ronin, and buyers separating Bitcoin storage from Polygon zkEVM activity can use the hardware wallet page for Bitcoin.
Choose the Polygon zkEVM route when the account is meant to manage ETH on Polygon zkEVM, then initialise the Dual-Card Set before relying on that account for the chain’s native coin or ERC-20 tokens.
Yes. Polygon zkEVM is pre-programmed in the free Cryptnox app on iOS and Android. A buyer managing ETH on Polygon zkEVM does not need to add that network manually. The same Polygon zkEVM entry can manage the chain’s native coin and ERC-20 tokens deployed on that chain.
Yes. ERC-20 tokens deployed on Polygon zkEVM can be managed from the Polygon zkEVM network in the Cryptnox app. If a token is not already visible, use Add a Token. The token should be added under Polygon zkEVM only when it is deployed on that chain.
No. Polygon zkEVM and Polygon PoS should be treated as separate network routes. ETH on Polygon zkEVM belongs under the pre-programmed Polygon zkEVM entry in the Cryptnox app. Assets on Polygon PoS should be managed through the separate Polygon route, not through Polygon zkEVM.
The Dual-Card Set ships uninitialised, and the seed is generated inside both secure elements during setup. That makes the second card the backup for the Polygon zkEVM account from the start. The default setup does not require writing down a recovery phrase; BIP39 import is an advanced option.
Private keys are generated inside the secure element and never leave it. For ETH on Polygon zkEVM and ERC-20 tokens on that chain, the Cryptnox app provides the network and account interface, while the card protects the private keys inside its secure element.
No. Unlocking uses the phone’s biometrics through the Cryptnox app. The card itself does not have a biometric sensor. In the Polygon zkEVM workflow, the phone provides the app unlock step, and the smart card protects the private keys for the account.
Yes. The Cryptnox app connects to Web3 through WalletConnect and works with MetaMask. Use the pre-programmed Polygon zkEVM network in the app for ETH or ERC-20 assets on that chain, then use the supported Web3 connection route when a session needs wallet access.
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.