Yes. Cryptnox can hold CRO as the native gas coin on Cronos EVM mainnet when you add Cronos manually as an EVM network or token. This is the chain ID 25 route with a 0x-prefixed 20-byte EVM address. It is not pre-programmed on the card, and it is not the native CRO route on Cronos POS cro-addresses. The Dual-Card Set keeps the Cronos EVM signing key inside secure elements, with the second card created as the backup during setup.
CRYPTNOX products are also available worldwide through our official Amazon stores.
Cryptnox supports CRO through the Cronos EVM mainnet route. In this setup, CRO is the native coin used for gas on an EVM L1 network with chain ID 25. The card does not arrive with Cronos already selected as a preloaded asset, so the buyer adds Cronos once through an Add a Network or Add a Token flow before using the CRO balance on that EVM route.
The chain ID is the practical identifier for the EVM network you are adding. Cronos documentation for adding Cronos Mainnet to MetaMask identifies the Cronos Mainnet EVM route and chain ID 25, which is the network route used for CRO on this page.
After Cronos EVM is added, the Cryptnox card signs for the 0x address that holds CRO on that network. The important buying decision is narrow and concrete: use Cryptnox for CRO on Cronos EVM mainnet after manual network setup, not as a pre-programmed Cronos POS cro-address wallet.
CRO is not a single-address-format asset across all Cronos-related environments. The Cryptnox route here is Cronos EVM mainnet, where the address is a 0x-prefixed 20-byte EVM address and CRO is the native gas coin for transactions on chain ID 25. Native CRO on Cronos POS uses cro-addresses and is a non-EVM form, so it should not be sent as though it were the same destination type.
If the receiving address begins with 0x and the selected network is Cronos EVM mainnet, it matches the CRO route described for Cryptnox. If the receiving address uses a cro-address format on Cronos POS, it does not match this EVM route. The prefix is not a naming detail; it points to the address system being used.
Before transferring CRO, check both fields together: the network shown by the sending platform and the address format shown by the receiving wallet. The correct pair for this page is Cronos EVM mainnet plus a 0x-prefixed 20-byte address. A cro-address belongs to the POS-chain form instead.
This distinction also explains why the card is not described as shipping with CRO already enabled. Cronos EVM use depends on adding the right EVM network or token route once. For a buyer searching for a cronos wallet, the key question is whether the CRO to be held is the EVM mainnet form on chain ID 25.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set is the product used for the Cronos EVM route on this page. For the 0x-prefixed Cronos EVM address, the private key is generated inside the secure element and never leaves it. The card signs Cronos EVM transactions for chain ID 25 without exporting that key to the phone or to the connected Web3 flow.
For CRO on Cronos EVM, that matters because the 0x address is controlled by the EVM private-key model. A Cronos EVM send or Web3 action is prepared outside the card, but the signing key stays inside the card’s secure element. The result is a Cronos EVM workflow where the card remains the signing object for the CRO address.
Unlocking the app experience uses the phone’s biometrics through the Cryptnox app. The card itself has no biometric sensor. For Cronos EVM use, that separates the app unlock step from the card signing step: the phone unlocks the app flow, and the card signs for the 0x address that holds CRO on chain ID 25.
The Dual-Card Set ships uninitialised, which matters for a Cronos EVM buyer because the CRO address is created during setup rather than arriving as a prepared account. During setup, the seed is generated inside both secure elements. The second card is therefore the backup for the same wallet that controls the Cronos EVM 0x address.
There is no recovery phrase to write down by default. For CRO on Cronos EVM, the normal backup object is the second smart card created during setup, not a handwritten phrase produced as the standard setup step. Keeping the second card separate from the first card is the practical backup action for the Cronos EVM wallet created by the set.
The default route is to generate the seed inside both secure elements when the two-card wallet is initialised. Importing a BIP39 recovery phrase of 12 or 24 words is available as an advanced option, but it is not the default route for a new CRO wallet on Cronos EVM.
This backup model fits the manual Cronos EVM addition process. First, the two cards are initialised so the same wallet can be recovered with the backup card. Then Cronos EVM mainnet is added as the chain ID 25 route for the 0x address. The backup card is tied to the wallet seed, so it remains the backup for the Cronos EVM address after the network is added.
The free Cryptnox app is available on iOS and Android. For CRO, the app is used with the card wallet while Cronos EVM mainnet is added manually as the EVM route. Cryptnox connects to Web3 through WalletConnect and works with MetaMask, so buyers who already use Cronos as a MetaMask-style EVM network can follow the chain ID 25 setup route.
The Cronos-specific step is not card activation by asset name; it is adding the EVM network or token route once. If CRO is not visible automatically, the expected action is to add Cronos EVM mainnet or add CRO through the token flow, then use the 0x address for that network.
If you want the card and app steps before adding Cronos, the Cryptnox hardware wallet tutorials are the relevant starting point. After the card wallet is ready, the Cronos part is the manual addition of the EVM mainnet route for CRO.
Cryptnox is a contact and NFC smart card, which gives two ways to use the same Cronos EVM signing card. You can tap it to a phone, or insert it into a reader. For CRO on chain ID 25, the interaction method does not change the address format: the wallet route remains a 0x-prefixed 20-byte EVM address on Cronos EVM mainnet.
The card is dual-interface, so Cronos EVM use is not tied to a single card interaction method. The phone or connected wallet flow prepares the Cronos EVM action, and the card signs for the protected 0x address. A CRO send and a Cronos EVM Web3 action both use the same EVM address model for this route.
This is also why the POS-chain distinction should be checked before sending CRO. The smart card can protect the EVM key for the 0x address, but this page’s CRO route is not the native Cronos POS cro-address route. The card form factor and the chain route are separate decisions: the form factor is contact and NFC smart card use, while the CRO route is Cronos EVM mainnet on chain ID 25.
For a buyer comparing devices, the important point is that the Cronos EVM account is not a phone-held key account. The phone participates in the app and connection flow, while the card signs for the Cronos EVM 0x address with the key kept inside the secure element.
Because CRO must be added through the Cronos EVM route, it is worth checking asset coverage before purchase if you plan to hold several networks on the same card wallet. The Cryptnox coin and blockchain support page is the relevant place to review broader coverage, while this page is specific to CRO as the native gas coin on Cronos EVM mainnet.
If you are still deciding whether the smart card wallet format fits your asset mix, the Cryptnox hardware wallet collection hub explains the product category around the Cryptnox card approach. For the exact product covered here, the purchase route is the Dual-Card Set linked above.
Cronos EVM should be compared by chain type and address format. The Polygon hardware wallet page is useful when comparing another 0x-address EVM route, while the Tron hardware wallet page covers a different address model. The Bitcoin hardware wallet page is another example where the setup logic is not the Cronos EVM chain ID 25 route.
For CRO, the deciding checklist remains short: Cronos EVM mainnet, chain ID 25, CRO as the native gas coin, manual Add a Network or Add a Token setup, and a 0x-prefixed 20-byte address. If those details match the CRO you intend to hold, the Cryptnox Dual-Card Set is the relevant smart card hardware wallet route.
No. CRO is not pre-programmed on the card for this route. You add Cronos EVM mainnet manually through an Add a Network or Add a Token flow. The supported route described here is CRO as the native gas coin on Cronos EVM mainnet, chain ID 25, using a 0x-prefixed 20-byte EVM address.
Use a 0x-prefixed 20-byte EVM address when holding CRO on Cronos EVM mainnet with Cryptnox. That address format belongs to the chain ID 25 EVM route. Native CRO on Cronos POS uses cro-addresses, which are a different non-EVM form and are not the route described for this setup.
This page covers CRO on Cronos EVM mainnet, where CRO is the native gas coin and the address is 0x-prefixed. Native CRO on Cronos POS uses cro-addresses and is a non-EVM form. For the Cryptnox route described here, the relevant network is Cronos EVM mainnet with chain ID 25.
For the Cronos EVM 0x address, the private key is generated inside the secure element and never leaves it. The card signs Cronos EVM transactions for chain ID 25 without exporting the key to the phone or connected Web3 flow. The platform uses an EAL6+-certified chip.
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.
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 wallet that controls the Cronos EVM 0x address. There is no recovery phrase to write down by default, though importing a 12 or 24 word BIP39 phrase is an advanced option.
Yes. The free Cryptnox app is available on iOS and Android, connects to Web3 through WalletConnect, and works with MetaMask. For Cronos, you add Cronos EVM mainnet manually as the chain ID 25 EVM route and use the 0x-prefixed address format for CRO.
No. Unlocking uses the phone’s biometrics through the Cryptnox app. The card itself has no biometric sensor. For CRO on Cronos EVM, the phone unlocks the app flow, while the smart card signs for the 0x address with the private key 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.