Yes. Cryptnox supports native FUSE after you manually add Fuse Network as an EVM network. FUSE is not pre-programmed on the card. Native FUSE uses an 0x-prefixed 20-byte EVM address, while bridged ERC-20 or BEP-20 FUSE representations are added separately as EVM tokens on their supported EVM chains. Private keys are generated inside the card’s secure element and never leave it.
CRYPTNOX products are also available worldwide through our official Amazon stores.
Native FUSE is held on Fuse Network, an EVM L1. On the Cryptnox Crypto Hardware Wallet – Dual-Card Set, that means the buyer adds Fuse Network once as an EVM network, then uses the resulting 0x-prefixed 20-byte EVM address for native FUSE. The card does not ship with FUSE already enabled, so the first FUSE-specific step is network setup rather than selecting a preloaded asset.
The same FUSE name can appear in different chain contexts. Native FUSE belongs to Fuse Network. A bridged ERC-20 or BEP-20 FUSE representation is an EVM token on the supported EVM chain where that representation exists. Cryptnox treats those routes differently: native FUSE is added through Add a Network, while a bridged representation is added through Add a Token on its own supported EVM chain.
Before sending FUSE to a newly configured card account, use the Cryptnox coin and blockchain support page to check the relevant route for Fuse Network or for the EVM chain that carries a bridged FUSE representation.
FUSE ownership is controlled by the private key behind the EVM address. With the Cryptnox Crypto Hardware Wallet – Dual-Card Set, private keys are generated inside the secure element and never leave it. For native FUSE, the Fuse Network account is therefore controlled by key material that is created inside the card rather than inside the phone app or a Web3 interface.
The card uses an EAL6+-certified chip. That certification applies to the chip platform. For a FUSE holder, the practical result is a clear custody model: the app can prepare a Fuse Network transaction, but the private key remains inside the card’s secure element for signing.
This matters because Fuse Network uses EVM-style accounts. The 0x address format can look familiar across EVM networks, but the network selection determines whether the transaction is native FUSE on Fuse Network or a token transfer on another supported EVM chain. The card protects the key; the user still selects the correct chain route before moving value.
The Dual-Card Set ships uninitialised. During setup, the seed is generated inside both secure elements, so the second card is the backup from the beginning. For FUSE, that backup protects the same EVM account that is later used after Fuse Network is manually added.
This default setup is different from writing down a recovery phrase during wallet creation. By default, there is no recovery phrase to write down; the second physical card is the backup. If the primary card is unavailable, the backup card is already tied to the same generated seed and can continue the card-based signing workflow for the FUSE account.
Advanced users can import a 12- or 24-word BIP39 recovery phrase. That is not the default path for the Dual-Card Set. The default path is to generate the seed inside both secure elements, keep the private keys inside the cards, and use the second card as the recovery device for the EVM account that will hold native FUSE after network setup.
For the setup sequence, use the Cryptnox hardware wallet tutorials before adding Fuse Network or a bridged FUSE token route.
The most important FUSE decision is whether the asset is native FUSE on Fuse Network or a bridged token representation on another supported EVM chain. The address may still begin with 0x, but the chain context changes the setup step and the transaction route.
For native FUSE, add Fuse Network as an EVM network. For an ERC-20 or BEP-20 FUSE representation, add the token on the supported EVM chain where that representation exists. Those token representations are not a separate native coin on Cryptnox; they are EVM tokens that require the correct chain and token route.
This distinction is especially important when a bridge, exchange, or Web3 app uses the FUSE name while offering more than one EVM route. The 0x address format identifies the account style; it does not by itself prove that the transfer is native FUSE on Fuse Network.
The free Cryptnox app is available on iOS and Android. For FUSE, the app is the place to work with the card while using the network route you have added. The app connects to Web3 through WalletConnect and works with MetaMask, which gives FUSE users an EVM workflow after Fuse Network has been manually configured.
Unlock uses the phone’s biometrics through the Cryptnox app. The card itself has no biometric sensor. After the phone unlock step, the card remains the signing device and the private key remains inside the secure element. For native FUSE, review that the selected chain is Fuse Network before approving the signing flow.
If your EVM wallet plan also includes assets configured on other Cryptnox pages, keep the Fuse Network route separate from the route described for Polygon hardware wallet use and from the route described for Ronin hardware wallet use.
The Cryptnox wallet is a contact and NFC smart card. You can tap it to a phone, or insert it into a reader. For FUSE, that means the same physical card can be used with the Cryptnox app for mobile setup and with a reader when that interface is preferred.
The card format keeps the FUSE custody roles separate. The phone runs the Cryptnox app, the app can connect to Web3 through WalletConnect and works with MetaMask, and the card protects the private keys in its secure element. Fuse Network is still added manually for native FUSE, and bridged FUSE representations are still added as tokens on their supported EVM chains.
The cards are Swiss-engineered. The product used for this FUSE setup is the Cryptnox Crypto Hardware Wallet – Dual-Card Set, which gives the buyer two uninitialised smart cards that create the seed inside both secure elements during setup.
If FUSE is one part of a broader card-based wallet setup, the Cryptnox hardware wallet collection is the parent collection for the Dual-Card Set. Keep the native FUSE route distinct from non-FUSE routes such as the TRON hardware wallet page and the Bitcoin hardware wallet page.
For a buyer who wants to hold native FUSE with card-based key storage, the required product is the Cryptnox Crypto Hardware Wallet – Dual-Card Set. The FUSE-specific work happens after wallet setup: add Fuse Network as an EVM network, confirm the 0x-prefixed EVM address, and use that route for native FUSE.
Do not treat FUSE as a pre-enabled card asset. The card arrives uninitialised, the seed is generated inside both secure elements during setup, and the second card becomes the backup. After that, Fuse Network is added manually. If the asset you are receiving is an ERC-20 or BEP-20 FUSE representation, add that token on the supported EVM chain instead of treating it as native FUSE.
No. FUSE is not pre-programmed on the card. To hold native FUSE, add Fuse Network manually as an EVM network. If you are using an ERC-20 or BEP-20 FUSE representation, add it as a token on the supported EVM chain where that representation exists.
Native FUSE on Fuse Network uses an 0x-prefixed 20-byte EVM address. That address format can also appear in other EVM contexts, so confirm the selected network before sending or receiving. For native FUSE, the network route must be Fuse Network.
The private key for the wallet account is generated inside the secure element and never leaves it. After Fuse Network is added, the native FUSE account is controlled by that key. The card signs through the wallet workflow while the key remains 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. That backup applies to the same EVM account used for native FUSE after Fuse Network is manually added.
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.
Yes. Importing a 12- or 24-word BIP39 recovery phrase is available as an advanced option. The default Dual-Card Set setup is different: the seed is generated inside both secure elements, and the second card serves as the backup for the wallet account.
Yes. The free Cryptnox app on iOS and Android connects to Web3 through WalletConnect and works with MetaMask. For native FUSE, add Fuse Network manually first, then review the network, asset, address, and transaction details before approving the card signing flow.
Native FUSE is the coin on Fuse Network. ERC-20 or BEP-20 FUSE versions are bridged EVM-token representations on their supported chains. On Cryptnox, native FUSE is added through Add a Network, while bridged representations are added through Add a Token on the appropriate supported EVM chain.
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.