Yes. Cryptnox supports Kyber Network Crystal v2 as the KNC ERC-20 token on Ethereum after you add it once through Add a Network or Add a Token. KNC is not pre-programmed on the card. Use the Ethereum contract address 0xdeFA4e8a7bcBA345F687a2f1456F5Edd9CE97202 and receive to a 0x-prefixed 20-byte EVM address controlled by your Cryptnox card. The Ethereum private key for that address is created inside the secure element and stays there.
CRYPTNOX products are also available worldwide through our official Amazon stores.
Kyber Network Crystal v2 is held with Cryptnox as KNC on Ethereum, using the ERC-20 token standard. The card does not arrive with KNC already set up, so the first KNC-specific step is to add the token manually. The detail that matters most is the Ethereum contract address: 0xdeFA4e8a7bcBA345F687a2f1456F5Edd9CE97202.
Kyber lists that address in its KNC contract address documentation, and the token contract can also be viewed on Etherscan. When you add KNC in a wallet workflow, use Ethereum as the chain context. Do not treat KNC as a separate Cryptnox card account type or as a non-Ethereum asset.
The Cryptnox coin and blockchain support page is useful when you are checking whether an asset uses a direct network route, a token contract route, or another account model. For KNC, the support route is the token contract route on Ethereum.
A KNC deposit goes to the Ethereum address controlled by your Cryptnox card. That address begins with 0x and follows the 20-byte EVM address format used by Ethereum accounts. The token balance is associated with that Ethereum account and the KNC contract, rather than with a separate KNC-only address.
Before withdrawing KNC from another service, check that the service is sending the Ethereum ERC-20 version of KNC. The receiving address should be the card-controlled 0x address, and the asset being sent should correspond to the contract 0xdeFA4e8a7bcBA345F687a2f1456F5Edd9CE97202. That is the combination that identifies KNC on Ethereum in the Cryptnox workflow.
If you are preparing a broader wallet setup, the Cryptnox hardware wallet tutorials cover the card and app workflow before you add the KNC token to the Ethereum account.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set is a contact and NFC smart card set. You can tap a card to a phone or insert it into a reader. For KNC, the important role of the card is to protect the Ethereum private key for the 0x address where the KNC ERC-20 balance is held.
The Ethereum private key behind that KNC address is generated inside the secure element and does not leave it. The card uses an EAL6+-certified chip. When a KNC transfer or an Ethereum transaction involving the KNC contract is prepared, the phone app provides the interface and the card performs the signing step inside the secure element.
KNC is an ERC-20 balance linked to an Ethereum account. Control of that account depends on the Ethereum private key, so protecting KNC means protecting the key for the 0x address. The card is the signing device for that address; the phone is used to view, prepare, and approve the action in the Cryptnox app workflow.
This matters when the same Ethereum address also appears in a Web3 connection. A connected service may display the account as a standard 0x Ethereum address, while KNC appears as the token balance under the KNC contract. The key that can approve movement from that address remains in the card’s secure element.
The Dual-Card Set arrives uninitialised. When you initialise the set for a fresh KNC wallet, the wallet seed is created within the secure elements of the two cards during the same setup process. The second card is therefore the backup for the Ethereum account that will hold KNC.
That backup model is especially relevant for KNC because there is no separate KNC recovery process. The recoverable object is the Ethereum wallet that controls the 0x address. Once KNC is added as the ERC-20 token at 0xdeFA4e8a7bcBA345F687a2f1456F5Edd9CE97202, both cards relate to the same wallet material and the same Ethereum address.
In the default Dual-Card Set setup, you are not asked to create the backup by copying a recovery phrase onto paper. The second card is prepared as the backup card. Importing a 12- or 24-word BIP39 recovery phrase is available as an advanced option, but a buyer setting up a new KNC wallet can use the normal two-card initialisation instead.
Store the two cards separately after setup. That keeps the backup useful if the daily card is unavailable. The KNC-specific point is simple: protect the cards that control the Ethereum address, because the KNC balance follows that address and the ERC-20 contract on Ethereum.
The free Cryptnox app is available on iOS and Android. It connects to Web3 through WalletConnect and works with MetaMask. For KNC, that means your card-controlled Ethereum 0x address can be used in a Web3 flow while the private key for the KNC-holding account remains inside the secure element.
When a Web3 site or wallet interface shows KNC, the details to verify are Ethereum, the connected 0x account, and the KNC contract address. The token itself is not a separate chain account. It is an ERC-20 token balance under the same Ethereum account that the card controls.
Unlocking uses the phone’s fingerprint or face unlock through the Cryptnox app. The card itself has no fingerprint or face sensor. For a KNC transfer or contract-related Ethereum transaction, the app is the screen where the action is prepared and reviewed, and the card is the device that signs after approval.
This keeps the KNC workflow focused on the Ethereum account. If you are using MetaMask with a Cryptnox-controlled account, confirm that the account shown in the interface matches the 0x address where you added or received KNC. If a token view asks for a contract, use 0xdeFA4e8a7bcBA345F687a2f1456F5Edd9CE97202.
KNC is an Ethereum ERC-20 token, so its Cryptnox setup depends on adding the token contract to an Ethereum account. That is different from buying a wallet for an asset whose page is built around another network or address model. If you are choosing one device for several assets, check the setup route for each asset before receiving funds.
The Cryptnox hardware wallet collection groups asset-specific wallet pages for buyers comparing those routes. If your purchase decision includes Bitcoin as well as KNC, the Bitcoin hardware wallet page is the better place to review that asset’s setup path. If your comparison includes Polygon, use the Polygon hardware wallet page for that separate route.
Buyers who also need TRON or Ronin can review the TRON hardware wallet page and the Ronin hardware wallet page. For this KNC page, the route remains Ethereum, ERC-20, contract 0xdeFA4e8a7bcBA345F687a2f1456F5Edd9CE97202, and a 0x-prefixed EVM address.
If you want to hold Kyber Network Crystal v2 with a card-based wallet, choose the Cryptnox Crypto Hardware Wallet – Dual-Card Set and initialise both cards before receiving KNC. The set is Swiss-engineered and uses the two-card setup as the default backup path for the Ethereum wallet that will hold the KNC ERC-20 token.
After setup, add KNC manually. Use Ethereum as the chain, ERC-20 as the token standard, and 0xdeFA4e8a7bcBA345F687a2f1456F5Edd9CE97202 as the contract. Receive KNC only to the card-controlled 0x address for that Ethereum account.
The result is a KNC workflow where the Ethereum address is visible in the app and Web3 tools, while the key that controls that address is handled by the card’s secure element.
No. KNC is not pre-programmed on the card. Add Kyber Network Crystal v2 once through Add a Network or Add a Token, using Ethereum as the chain and 0xdeFA4e8a7bcBA345F687a2f1456F5Edd9CE97202 as the ERC-20 contract.
Use the Ethereum address controlled by your Cryptnox card. KNC on Ethereum uses a 0x-prefixed 20-byte EVM address. Before sending from another service, confirm that the withdrawal is for the Ethereum ERC-20 version of KNC.
For KNC, the card protects the Ethereum private key for the 0x address that holds the ERC-20 token balance. That private key is generated inside the secure element and remains there while the card signs approved Ethereum transactions.
The Dual-Card Set is initialised before use. During setup for a fresh wallet, the seed is created inside the secure elements of both cards. The second card is the backup for the same Ethereum address that can hold KNC.
Yes. The Cryptnox app on iOS and Android connects to Web3 through WalletConnect and works with MetaMask. Use the Ethereum 0x account controlled by the card, and verify the KNC contract address when adding or reviewing the token.
No. Unlocking uses the phone’s fingerprint or face unlock through the Cryptnox app. The card itself has no fingerprint or face sensor; it stores and uses the Ethereum private key for the KNC-holding address inside the secure element.
Importing a 12- or 24-word BIP39 recovery phrase is an advanced option. The default Dual-Card Set path for a new KNC wallet creates the seed inside both secure elements and uses the second card as the backup.
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.