Yes. GNOSIS is pre-programmed in the Cryptnox app, so you do not need to add the Gnosis network manually. The Cryptnox Crypto Hardware Wallet – Dual-Card Set uses contact and NFC smart cards that you can tap to a phone or insert into a reader. Private keys are generated inside the secure element and never leave it, while the free iOS and Android app connects to Web3 through WalletConnect and works with MetaMask.
CRYPTNOX products are also available worldwide through our official Amazon stores.
Gnosis support starts with the GNOSIS network already present in the Cryptnox app. For a GNO buyer, that means the network route is ready before you add token entries or compare the setup with another EVM chain. The product used for this setup is the Cryptnox Crypto Hardware Wallet – Dual-Card Set, which is sold as two smart cards prepared together during initialisation.
The app separates the Gnosis network from token entries. GNOSIS is the pre-programmed network route. ERC-20 tokens can be added manually through Add a Token when a token entry is needed. If you later want to use a different EVM network, Add a Network is the route for that chain; once that EVM network is added, its native coin and any ERC-20 deployed on that chain can be managed.
This distinction matters because adding a token is not the same as adding a network. Start from the existing GNOSIS entry for Gnosis activity, then add ERC-20 token entries only when they need to appear in the app. If you want to compare Gnosis with the wider asset list before ordering, the Cryptnox coin and blockchain support page is the support hub to review.
For a GNO account managed through the GNOSIS route in the Cryptnox app, the private key is generated inside the card’s secure element. It is not created in the phone app and then moved to the card. The custody model begins inside the hardware card, and the private key remains inside that secure element after creation.
The chip used for this model is an EAL6+-certified chip. For Gnosis use, the important point is the chip platform inside the smart card: the card holds the private key and supports signing without exporting that key to the phone, to a browser wallet, or to a written note.
This separation is useful for Gnosis because the network path and token display live in the app, while custody of the account key stays on the card. WalletConnect or MetaMask can be used as Web3 connection routes through the Cryptnox app, but the Gnosis private key is not copied into those tools.
The Dual-Card Set ships uninitialised. During setup for your Gnosis wallet, the seed is generated inside both secure elements. The second card is therefore the backup card from the beginning, rather than making a written recovery phrase the default backup step before you can use the wallet.
For Gnosis holders, the two-card model is a practical buying difference. The account you use through the GNOSIS network in the Cryptnox app is prepared with two hardware cards in the same setup process. If one card is not available, the second card is the backup created during initialisation.
Before transferring GNO or ERC-20 tokens connected to your Gnosis use, initialise both cards and confirm that the app is using the pre-programmed GNOSIS network. The Cryptnox startup guide is the setup reference to use before funding the wallet address shown in the app.
The backup approach is especially clear when you are choosing a wallet specifically for Gnosis. You are not buying a single card and then creating a separate default paper backup. You are buying a Dual-Card Set in which the second smart card is part of the normal setup model.
The Cryptnox card used for Gnosis 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 when using the contact interface. The GNOSIS network entry remains the same in the app whichever card interface you use.
On mobile, the free Cryptnox app on iOS and Android is the interface for the pre-programmed GNOSIS network, ERC-20 token additions, and Web3 connection flow. Unlocking uses the phone’s face or fingerprint check through the Cryptnox app. The card itself has no biometric sensor; its role is to protect the private key inside the secure element.
This matters for a Gnosis buyer because network setup and physical card interaction are separate steps. GNOSIS is already in the app. The card can be used through either interface, and the private key remains inside the secure element during Gnosis account use.
Gnosis support in Cryptnox starts with the pre-programmed GNOSIS network. That network entry is the route to use for GNO activity. Token management is handled separately: ERC-20 tokens can be added manually through Add a Token when a token entry is needed in the app.
For a GNO buyer, the main setup question is whether you need to add a network or a token. With Gnosis, the network answer is already handled because GNOSIS is pre-programmed. If the asset you want to manage is an ERC-20 token, use the token flow rather than creating another network entry for the same Gnosis use case.
The same distinction helps when comparing Gnosis with other EVM pages in the Cryptnox collection. A buyer reviewing Polygon hardware wallet support or Ronin hardware wallet support is also looking at network and token choices, while this page focuses on the pre-programmed GNOSIS route.
If your Gnosis activity also involves a different EVM chain, add that chain through Add a Network first. After that, the native coin for that chain and ERC-20 tokens deployed on it can be managed from the app. Keep the GNOSIS entry for Gnosis activity and use token additions for token visibility.
The free Cryptnox app connects to Web3 through WalletConnect and works with MetaMask. For Gnosis users, the app provides the connection route while the smart card remains the hardware element controlling the private key for the account used through the GNOSIS network.
This separation matters when you use Gnosis beyond checking a balance. WalletConnect and MetaMask are connection routes. The card is where the private key was generated and where it remains. A Web3 session does not require the Gnosis private key to be copied into the phone or into a browser wallet.
If you are comparing Gnosis with a non-EVM asset before choosing a wallet, the Cryptnox hardware wallet collection is a useful parent page. You can also compare this Gnosis setup with Bitcoin hardware wallet storage if your buying decision includes both EVM and non-EVM assets.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set is the Cryptnox product for a buyer who wants Gnosis support through the pre-programmed GNOSIS network in the app. The set gives you two smart cards, a second-card backup model, and use of the free Cryptnox app on iOS and Android. The cards are Swiss-engineered and made in Switzerland.
Before moving GNO or ERC-20 tokens into the wallet account shown in the app, initialise the two cards and use the existing GNOSIS network entry. If a token entry is missing, add it through Add a Token. If you need a different EVM chain, add that chain through Add a Network and then manage its native coin and ERC-20 tokens from the app.
If you are still comparing networks, the Cryptnox page for Tron hardware wallet support covers a different asset route, while this Gnosis page is specific to the pre-programmed GNOSIS network in the app.
When you are ready to buy for Gnosis, order from the official Cryptnox product page, set up both cards, and confirm the GNOSIS network in the app before sending assets.
Yes. GNOSIS is pre-programmed in the Cryptnox app, so you do not need to add the Gnosis network manually. For ERC-20 tokens, use Add a Token when a token entry needs to be added. Add a Network is for another EVM chain, not for the existing GNOSIS route.
The app supports the pre-programmed GNOSIS network and manual ERC-20 token additions through Add a Token. Once an EVM network is available in the app, its native coin and ERC-20 tokens deployed on that chain can be managed. For Gnosis, start with the existing GNOSIS network entry.
The private key for the wallet account is generated inside the secure element and remains there. For Gnosis use, the app provides the GNOSIS network route and the user interface, while the smart card keeps the private key inside the secure element rather than exposing it to the phone.
The Dual-Card Set ships uninitialised. During setup, the seed is generated inside both secure elements, so the second smart card is the backup. A written recovery phrase is not the default setup route, although importing an existing 12- or 24-word BIP39 recovery phrase is an advanced option.
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.
No. Unlocking uses the phone’s face or fingerprint check through the Cryptnox app. The card itself has no biometric sensor. In a Gnosis setup, the card protects the private key inside the secure element while the phone and app provide the interaction layer.
Yes. The free Cryptnox app connects to Web3 through WalletConnect and works with MetaMask. For Gnosis activity, those tools provide Web3 access while the private key remains inside the smart card’s secure element.
It is both. The Cryptnox wallet is a contact and NFC smart card, so you can tap it to a phone for app-based use or insert it into a reader when using the contact interface. The GNOSIS network entry remains the same in the app.
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.