Yes—Cryptnox supports Hop Protocol (HOP) as an ERC-20 token on Ethereum, and as HOP deployments or representations on EVM networks after you add the relevant network and token contract. HOP is not pre-programmed on the card. Add it once through Add a Network or Add a Token, then use the 0x-prefixed EVM address controlled by the Cryptnox card. The private key for that HOP address is created inside the card secure element and is not exported.
CRYPTNOX products are also available worldwide through our official Amazon stores.
Hop Protocol (HOP) follows the EVM token path on Cryptnox. On Ethereum, HOP is held as an ERC-20 token at a 0x-prefixed 20-byte EVM address. If you hold a HOP deployment or representation on another EVM network, the network and that network’s HOP token contract must be added before you rely on the balance view or receive instructions.
This is not a preloaded coin entry. A HOP buyer should treat setup as a one-time mapping between three items: the EVM address controlled by the card, the network where HOP is being held, and the token contract for HOP on that network. The card protects the key for the address; the added network and token contract tell the app or connected wallet which HOP balance to show and which network to prepare transactions on.
Cryptnox lists broader asset and network coverage on the coin and blockchain support page. For HOP-specific network context, the Hop Protocol FAQ is useful when you are deciding which HOP route you intend to hold.
For the Ethereum route, HOP is handled as an ERC-20 token. The practical setup is to open the Cryptnox app, use the EVM account controlled by your card, and add HOP as an Ethereum token using the correct contract details. Once added, the app or connected Web3 wallet can display HOP for the same 0x-prefixed address used by that EVM account.
The address format matters. HOP on Ethereum is not received through a chain-specific account name or a non-EVM address type. It is received at a 0x-prefixed 20-byte EVM address. If an exchange, wallet, or counterparty asks for a HOP receiving address, the Ethereum route means you provide that EVM address and make clear that the transfer is for HOP on Ethereum.
If you want the product setup sequence before adding a manual token, use the Cryptnox hardware wallet tutorials. That is the right starting point before you add HOP as a token entry rather than assuming it appears automatically.
HOP can also be held as EVM-network deployments or representations. The key point is that a same-looking 0x address does not remove the need to choose the correct network. A HOP token entry on Ethereum and a HOP token entry on another EVM network are separate display and transaction routes, even when the address text starts with the same 0x prefix.
For non-Ethereum EVM routes, add the network first. Only after that should you add the HOP token contract for that specific network. Token contracts are network-specific, so copying an Ethereum contract into another network view can produce a wrong or useless token entry. Hop Protocol publishes mainnet address information in its mainnet address file, which can help you verify the intended contract before you receive HOP.
When someone sends HOP to you, the instruction should include both the destination address and the network. “Send to this 0x address” is incomplete if the sender might choose between Ethereum and another EVM network. The safer instruction is “send HOP on this network to this 0x address,” followed by a test transfer when you are using a newly added network or token contract.
This distinction is also why HOP setup differs from network-native asset pages. For comparison, Cryptnox’s Polygon hardware wallet guide focuses on Polygon network use, while this HOP page focuses on adding an EVM token contract to the network where the HOP balance exists.
For HOP, the sensitive object is the private key controlling the EVM address that holds the token balance. During setup, that key material is created inside the card secure element, so the HOP address is not based on a key generated in a software wallet and then copied to the card. When a HOP transaction is prepared through the app, MetaMask, or a WalletConnect flow, the signing step is tied back to the card-controlled EVM account.
The chip used for this HOP signing environment is an EAL6+-certified chip. The certification applies to the chip platform, and the buyer experience is the Cryptnox smart card working with the app to manage the 0x-prefixed account used for HOP. The result is a setup where the HOP token entry can be added or changed in the interface without changing where the private key is held.
This matters for HOP because token management can be confused with key management. Adding HOP as an ERC-20 token on Ethereum, or adding a HOP contract on another EVM network, is a visibility and routing action. It lets the wallet interface show the HOP balance and prepare transactions for the selected network. It does not export the private key for the 0x address.
The Dual-Card Set arrives uninitialised, so a new HOP wallet is created during your setup rather than being shipped with a preset wallet. The seed is generated inside both cards’ secure elements during setup, making the second card the backup for the HOP-controlling EVM account. The default path does not require writing down a recovery phrase. Importing an existing 12- or 24-word BIP39 seed is available as an advanced option, but a new HOP setup can use the two-card backup model from the start.
App unlocking uses the phone’s fingerprint or face unlock through the Cryptnox app. The card has no fingerprint or face sensor. For a HOP holder, that means phone unlock controls access to the app flow, while the HOP signing key remains inside the card secure element.
The HOP workflow can be mobile or desktop because the Cryptnox card is dual-interface: tap it to a phone with NFC, or insert it into a compatible contact smart-card reader. That is useful for HOP because the same EVM address may be used in a mobile app for checking a token balance and in a desktop Web3 session for adding a custom token or approving an Ethereum transaction.
The free Cryptnox app runs on iOS and Android and is where you initialise the two cards, unlock the app flow with the phone, and manage the card-controlled EVM account. For HOP, the app is also where the token entry or network route is added when it is not already visible.
Cryptnox connects to Web3 through WalletConnect and works with MetaMask. In a HOP session, that allows the card-protected 0x address to appear in Web3 flows where HOP is treated as an ERC-20 token on Ethereum or as a token on another added EVM network. MetaMask can also be part of the custom-token viewing flow when the relevant HOP contract must be added manually.
Adding HOP inside a connected wallet interface should not be mistaken for moving HOP into that interface. The token remains associated with the 0x address on the selected network. The interface prepares the view and transaction request; the card-controlled key is what authorises a transaction for that address.
The product to buy for this HOP setup is the Cryptnox Crypto Hardware Wallet – Dual-Card Set. It is the correct choice when you want a card-controlled EVM address for HOP and a second card created as the backup during setup. For a new HOP wallet, both cards are initialised together, and the HOP-relevant key material is generated inside the secure elements rather than imported from a software wallet by default.
The card format is also relevant to how HOP is used. HOP is an EVM token, so a buyer may need to add a token contract, use MetaMask, connect through WalletConnect, or check a balance from a phone. A contact and NFC smart card fits that pattern because you can tap with a phone or use a contact reader for a desktop session without changing the HOP address model.
If you are comparing HOP storage with other assets before purchasing, start with the crypto hardware wallet collection hub. HOP is an EVM-token setup, while other assets can have different account models. For contrast, the Bitcoin hardware wallet page is not based on adding an ERC-20 contract, and the TRON hardware wallet page covers a different network route. Those comparisons make the HOP requirement clearer: choose the correct EVM network, add the correct HOP token contract, and use the card-controlled 0x address.
Before sending HOP to your Cryptnox-controlled address, confirm the route in writing. The address alone is not enough when HOP may be handled on Ethereum or through another EVM-network deployment or representation. The network, the token contract, and the 0x address should all match the HOP balance you expect to receive.
This checklist is especially important when transferring from an exchange, bridge interface, or wallet that asks you to choose a network. A wrong network choice is not solved by the hardware wallet. The Cryptnox cards protect the private key for the EVM address; the sender still has to send HOP on the network you added and intend to use.
No. HOP is not pre-programmed on the card. Add HOP once as an ERC-20 token on Ethereum, or add the relevant EVM network and then the HOP token contract for that network. After setup, the balance is tied to the 0x-prefixed EVM address controlled by your Cryptnox card.
Use the Ethereum route when you want HOP as an ERC-20 token on Ethereum. Use the EVM-network route when you are holding a HOP deployment or representation on another EVM network. In both cases, the receiving address is a 0x-prefixed 20-byte EVM address, but the network and token contract must match.
The address format can look the same across EVM networks, but HOP balances belong to the network and token contract where they exist. When receiving HOP, give both the 0x address and the intended network. Add the HOP token contract for that network before relying on the balance display.
The Dual-Card Set is set up uninitialised. During setup, the seed for the EVM account that can hold HOP is generated inside both cards’ secure elements. That makes the second card the backup from the beginning. The default setup does not require writing down a recovery phrase.
The private key controlling the HOP EVM address is created inside the card secure element and is not exported. Adding HOP in the app, MetaMask, or a WalletConnect flow changes how the token is displayed and used on a selected network; it does not move the private key out of the card.
No. The card has no fingerprint or face sensor. Unlocking uses the phone’s fingerprint or face unlock through the Cryptnox app. For HOP, that phone unlock helps access the app flow, while the card remains the place where the EVM address signing key is protected.
Yes. The Cryptnox app on iOS and Android connects to Web3 through WalletConnect and works with MetaMask. For HOP, add the correct Ethereum ERC-20 token entry or the relevant EVM network and HOP contract, then use the card-controlled 0x address in the connected wallet flow.
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.