Yes. The Cryptnox Crypto Hardware Wallet – Dual-Card Set can hold native EVMOS after you add Evmos manually as a custom EVM network. EVMOS is not pre-programmed on the card; you add it once through Add a Network or Add a Token. Evmos uses an 0x-prefixed 20-byte EVM address, while the private key for that account is generated inside the secure element and never leaves it.
CRYPTNOX products are also available worldwide through our official Amazon stores.
EVMOS is supported as the native coin of the Evmos EVM L1, not as a pre-programmed card entry. The buyer workflow is to initialise the Cryptnox Crypto Hardware Wallet – Dual-Card Set, add Evmos manually as a custom EVM network, and then use the 0x-prefixed 20-byte EVM address for native EVMOS on Evmos.
This distinction matters because EVMOS support is a chain route. The visible address has the same 0x style used by EVM networks, but the asset covered here is native EVMOS on Evmos. The Evmos project publishes its chain software in the Evmos GitHub repository, and the Cryptnox route treats EVMOS as a native Evmos asset added through the custom EVM network path.
If you are checking how Cryptnox handles different assets before buying, the Cryptnox coin and blockchain support page is the right place to compare supported routes. For EVMOS, the route is clear: add Evmos once, confirm the 0x address, and use that Evmos network path for native EVMOS.
Evmos must be added manually before native EVMOS is used with the Cryptnox wallet. The setup path may appear as Add a Network or Add a Token, but the intended result is the same: Evmos is the selected custom EVM network for the 0x account that will hold native EVMOS.
Network details should be entered carefully because a 0x address format alone does not identify the chain being used. A useful reference for Evmos network parameters is the ChainList Evmos entry. The point of checking the network entry is to make sure native EVMOS is handled on Evmos rather than on another EVM route.
For product setup steps, use the Cryptnox hardware wallet tutorials. If you also hold assets on other chains, keep the Evmos route separate from the instructions for the Polygon hardware wallet or the Bitcoin hardware wallet, because those pages cover different asset routes.
Evmos uses an 0x-prefixed 20-byte EVM address in this Cryptnox setup. That address is the visible account identifier for native EVMOS on the Evmos network, while the private key associated with it is generated inside the card’s secure element and never leaves it.
The address format is only one part of the EVMOS setup. The selected network must also be Evmos. A buyer who already uses other EVM assets may recognise the 0x address shape, but native EVMOS belongs on the Evmos custom EVM network route added through the Cryptnox app workflow.
This chain-plus-address model is the practical way to think about EVMOS on Cryptnox. The chain is Evmos, the asset is native EVMOS, and the address is the 0x-prefixed EVM address controlled by the secure element in the smart card.
If you compare EVMOS with another EVM-style asset route, the Ronin hardware wallet page shows a separate network path for a different asset. For this page’s asset, the route remains native EVMOS on Evmos.
For the Evmos 0x account created with Cryptnox, the private key is generated inside the secure element and never leaves it. The phone, app, and Web3 connection route provide access to the Evmos account workflow, but the private key for native EVMOS is not exported from the card.
The secure element uses an EAL6+-certified chip. For an EVMOS holder, this chip-level security design is paired with the manual Evmos network route: the account is still an EVM-style 0x account, but the key material is created and retained inside the smart card rather than kept only in software.
Unlocking the wallet experience uses the phone through the Cryptnox app. The app can use the phone’s face or fingerprint unlock, and the card itself has no face or fingerprint scanner. That separation fits the Evmos workflow because the phone supplies the interface while the card remains the place where the Evmos account’s private key is held.
This model lets an EVMOS buyer use an Evmos address in a mobile workflow while keeping the private key inside the smart card.
The Dual-Card Set ships uninitialised, and the backup is created during setup. During initialisation, the seed is generated inside both secure elements, so the second card becomes the backup for the same wallet. For EVMOS, that means the backup card protects the same underlying Evmos 0x account route after Evmos has been added manually.
The default setup does not begin with writing a paper recovery phrase. Instead, the second smart card is prepared as the backup for the same wallet. That matters for an Evmos buyer because the backup card is not a separate Evmos address and not a second standalone EVMOS setup; it is the second card for the same wallet created during initialisation.
For native EVMOS, the practical result is a card-to-card backup model. Initialise the two cards, add Evmos through the custom EVM network route, and keep the second card separate from the card used day to day.
The free Cryptnox app on iOS and Android connects to Web3 via WalletConnect and works with MetaMask. For EVMOS, this matters because Evmos is added as a custom EVM network, and the 0x account must be used on the Evmos route when native EVMOS is involved.
When MetaMask is part of the workflow, the Evmos network selection should be checked before native EVMOS is used. The visible address can have the familiar EVM 0x format, so the chain context is the detail to verify. Add Evmos once, then use the account on that Evmos network route.
If your comparison includes non-Evmos assets, the Tron hardware wallet page covers a different chain route. EVMOS should stay on the Evmos route with the 0x-prefixed 20-byte EVM address.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set is a contact and NFC smart card product. For EVMOS, the card format means you can tap a card to a phone when using the mobile app, or insert a card into a reader when using the contact interface. It is a dual-interface smart card.
This form factor fits an Evmos buyer who wants the private key for an 0x account to stay inside a secure element while using a phone-based app and a Web3 connection route. The chain-specific work for EVMOS is adding Evmos manually and confirming the 0x-prefixed address before using native EVMOS.
The cards are Swiss-engineered. The product for this setup is the Cryptnox Crypto Hardware Wallet – Dual-Card Set, sold on the Cryptnox Dual-Card Set product page. If you are deciding whether this hardware wallet category fits more than EVMOS, the broader crypto hardware wallet collection places the Dual-Card Set in context with other supported asset routes.
Choose this product for EVMOS if you are comfortable adding Evmos manually as a custom EVM network, want a 0x-prefixed EVM address for native EVMOS, and prefer a second secure-element card as the default backup for the same wallet.
No. EVMOS is not pre-programmed on the card. The supported route is to add Evmos manually as a custom EVM network through Add a Network or Add a Token. After Evmos is added, native EVMOS is used on that Evmos route with an 0x-prefixed 20-byte EVM address.
Evmos uses an 0x-prefixed 20-byte EVM address in this setup. That address format is familiar across EVM networks, so the network selection still matters. For native EVMOS, make sure the app or connected service is set to Evmos before using the address.
The private key for the Evmos 0x account is generated inside the Cryptnox card’s secure element and never leaves it. The app provides the phone interface and Web3 connection route, but the private key is retained inside the smart card.
The Dual-Card Set ships uninitialised. During setup, the seed is generated inside both secure elements, so the second card becomes the backup for the same wallet. Once Evmos is added manually, the backup card protects the same wallet used for the Evmos 0x account.
Yes. The free Cryptnox app on iOS and Android connects to Web3 via WalletConnect and works with MetaMask. For EVMOS, add Evmos manually as a custom EVM network first, then use the 0x-prefixed address on the Evmos network.
No. The card itself has no face or fingerprint scanner. Unlocking the wallet experience can use the phone’s face or fingerprint unlock through the Cryptnox app, while the card’s role is to keep the Evmos account’s private key inside the secure element.
No. The Cryptnox wallet is a contact and NFC smart card. You can tap it to a phone when using the mobile app, or insert it into a reader. Evmos support uses that dual-interface card format together with the manual custom EVM network route.
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.