Yes. Cryptnox supports Ethereum Classic by holding native ETC on Ethereum Classic mainnet after you add it once as a custom EVM network in the Cryptnox app. ETC is not pre-programmed on the card. The ETC account uses a 0x-prefixed 20-byte EVM address, while private keys are generated inside the secure element and never leave it. The Dual-Card Set ships uninitialised, with the second card serving as the backup.
CRYPTNOX products are also available worldwide through our official Amazon stores.
Ethereum Classic is held with Cryptnox as native ETC on Ethereum Classic mainnet. It is not an ERC-20 token on Ethereum mainnet, and it is not pre-programmed on the card before setup. The buyer adds Ethereum Classic once in the Cryptnox app as a custom EVM network through Add a Network or Add a Token.
The ETC account uses a 0x-prefixed 20-byte EVM address. That address shape belongs to EVM networks, so the network entry matters: for this asset, the chain is Ethereum Classic and the asset is native ETC. The Ethereum Classic network documentation identifies Ethereum Classic as its own network environment, which matches the Cryptnox setup route for native ETC.
If you hold more than one asset, the Cryptnox coin and blockchain support page helps you separate Ethereum Classic from other supported networks before you configure the app entry.
ETC on this setup is the native coin of Ethereum Classic mainnet. The 0x address format can look familiar to buyers who have used Ethereum or other EVM chains, but the address alone does not define the chain. With Cryptnox, the intended route is to add Ethereum Classic as the custom EVM network and use native ETC on that network.
This distinction is important when preparing to receive ETC. A native Ethereum Classic account should be used with the Ethereum Classic mainnet entry you added in the Cryptnox app. Treating ETC as a token on Ethereum mainnet would not match the asset route described here.
The official Ethereum Classic endpoints resource lists endpoints for the Ethereum Classic network. For a Cryptnox buyer, the practical point is that the custom EVM network entry must correspond to Ethereum Classic mainnet when the asset is native ETC.
For an Ethereum Classic account, the private keys behind the 0x ETC address are generated inside the card’s secure element and never leave it. The ETC key is not created as a normal phone app file. The app gives you the interface for the Ethereum Classic network entry, while the card remains the hardware element that protects the account keys.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set is a contact and NFC smart card. You can tap the card to a phone when using the Cryptnox app, or insert it into a reader when using the contact interface. That dual-interface form factor is useful for an ETC holder because the same card model supports phone tapping and reader insertion without changing how the ETC private keys are protected.
The chip platform used for the card is an EAL6+-certified chip. That statement applies to the chip, not to a claim that the finished card is a certified wallet. For ETC buyers, the important security model is simpler: the Ethereum Classic account key is generated inside the secure element and stays there.
The product for this setup is the Cryptnox Crypto Hardware Wallet – Dual-Card Set. It is the card set to buy if you want to hold native ETC through the Cryptnox smart-card model after adding Ethereum Classic as a custom EVM network.
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 Ethereum Classic account protected by the first card. The default ETC setup does not require writing down a recovery phrase before the card set can protect native ETC.
This matters for Ethereum Classic because ETC is added after the card set is initialised. You set up the two-card hardware wallet first, then add Ethereum Classic once as a custom EVM network in the Cryptnox app. The ETC account is then derived from the seed held inside both secure elements.
Importing a BIP39 phrase with 12 or 24 words is an advanced option, not the default path for a new Dual-Card Set. For an ETC buyer, the normal backup decision is therefore about protecting two smart cards that represent the same Ethereum Classic account.
The Cryptnox app is free on iOS and Android. For Ethereum Classic, the app is where you add the custom EVM network once, view the ETC account interface, and use the physical card that protects the private keys. ETC should not be treated as already configured when the card arrives.
Unlock for the ETC workflow uses the phone’s biometrics through the Cryptnox app. The card itself has no biometric sensor. The phone provides the app unlock experience, while the smart card remains the secure element that holds the Ethereum Classic private keys.
Cryptnox connects to Web3 through WalletConnect and works with MetaMask. For Ethereum Classic, add ETC first as a custom EVM network in the Cryptnox app, then use the card-protected account through the available connection routes.
For setup guidance across Cryptnox wallet products, use the Cryptnox hardware wallet tutorials. The Ethereum Classic-specific step is the custom EVM network addition, because native ETC is not pre-programmed on the card.
Ethereum Classic has a different setup path from Bitcoin, Tron, Polygon, and Ronin. ETC uses a 0x-prefixed EVM address, but the chain is Ethereum Classic mainnet and the asset is its native coin. A buyer comparing storage options should check both the key model and the network route.
The Cryptnox hardware wallet hub is a useful starting point when you want to compare how different assets fit into the same Dual-Card Set. Ethereum Classic should be compared as a native EVM Layer 1 coin, not as a token on another chain.
Polygon also uses EVM-style addresses, but it is not Ethereum Classic; its route is covered separately on the Cryptnox hardware wallet for Polygon page. Ronin has its own network path as well, described on the Cryptnox hardware wallet for Ronin page.
The contrast is different with Bitcoin, because Bitcoin does not use a 0x-prefixed EVM address; the Cryptnox hardware wallet for Bitcoin page addresses that separate asset route. Tron is also treated separately on the Cryptnox hardware wallet for Tron page.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set is the product to buy when you want to hold native ETC with the Cryptnox smart-card model. It ships uninitialised, and Ethereum Classic is added later as a custom EVM network in the app.
For an Ethereum Classic buyer, the purchase decision comes down to three practical points. First, native ETC is held on Ethereum Classic mainnet, not as an Ethereum mainnet token. Second, the ETC private keys are generated inside the secure element and never leave it. Third, the second card is the backup created during the default Dual-Card Set setup.
You can buy the Cryptnox Crypto Hardware Wallet – Dual-Card Set from the Cryptnox shop. After setup, add Ethereum Classic through the custom EVM network route and use the card set as your hardware wallet for native ETC.
No. Ethereum Classic is not pre-programmed on the card. You add ETC once in the Cryptnox app as a custom EVM network through Add a Network or Add a Token. The asset held through this route is native ETC on Ethereum Classic mainnet.
ETC uses a 0x-prefixed 20-byte EVM address format with Cryptnox. The address shape is familiar across EVM networks, but the chain selection must be Ethereum Classic mainnet when you are holding native ETC.
For an ETC account, the private keys are generated inside the secure element and never leave it. The card uses an EAL6+-certified chip platform, and the Ethereum Classic account key behind the 0x address is created inside the secure element.
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 ETC account. A written recovery phrase is not part of the default setup, while importing a BIP39 phrase is an advanced option.
Yes. The free Cryptnox app on iOS and Android provides the mobile interface for adding Ethereum Classic as a custom EVM network and using the card-protected ETC account. Unlock uses the phone’s biometrics through the app; the card has no biometric sensor.
Cryptnox connects to Web3 through WalletConnect and works with MetaMask. For Ethereum Classic, add ETC first as a custom EVM network in the Cryptnox app. The ETC private keys remain generated inside the card’s secure element and never leave it.
No. ETC on Cryptnox is native Ethereum Classic on Ethereum Classic mainnet. It is the native coin of an EVM Layer 1 chain and uses a 0x-prefixed 20-byte EVM address. It should not be treated as an ERC-20 token on Ethereum mainnet.
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.