Yes. MNT is holdable with Cryptnox by adding Mantle Network once for native MNT, or by adding the Ethereum ERC-20 MNT token once at 0x3c3a81e81dc49a522a592e7622a7e711c06bf354. MNT is not pre-programmed on the card. The Cryptnox Crypto Hardware Wallet – Dual-Card Set protects the private key for the 0x-prefixed EVM address inside secure elements, while the free Cryptnox app connects to Web3 through WalletConnect and works with MetaMask.

Mantle MNT has two supported routes with the Cryptnox Crypto Hardware Wallet – Dual-Card Set. The first route is native MNT on Mantle Network, an EVM-compatible network where MNT is used as the native gas coin. The second route is the Ethereum ERC-20 MNT token, which is tracked on Ethereum mainnet by its token contract address.
For the native route, add Mantle Network once through the EVM network-add flow used by your wallet environment. Mantle identifies MNT as the native token of Mantle Network in its own overview of what MNT is. After Mantle Network is added, your MNT balance is associated with a 0x-prefixed 20-byte EVM address controlled by the private key protected on the Cryptnox card.
For the Ethereum route, add the ERC-20 MNT token once on Ethereum mainnet. The token contract is 0x3c3a81e81dc49a522a592e7622a7e711c06bf354, and the contract can be checked on Etherscan. This token entry is separate from adding Mantle Network, even though both routes use an EVM-style address.
For native MNT on Mantle Network and ERC-20 MNT on Ethereum, the asset view depends on the network or token you add, but the sensitive item is the private key behind the 0x-prefixed EVM address. With Cryptnox, that private key is generated inside the secure element and never leaves it.
This matters for MNT because a Mantle Network balance and an Ethereum token balance can both appear under EVM-style account handling. The card is not storing an MNT icon or a preloaded asset switch. It is protecting the key that controls the EVM account, while the wallet interface is told whether to show native MNT on Mantle Network or ERC-20 MNT on Ethereum.
The Cryptnox card uses an EAL6+-certified chip. For an MNT holder, the important distinction is that this certification belongs to the chip platform, while the card’s role in the MNT setup is to create and keep the private key inside the secure element.
When you prepare a Mantle Network action, the wallet context must be Mantle Network for native MNT. When you prepare an Ethereum token action, the wallet context must be Ethereum mainnet with the MNT token contract added. The same 0x address format does not make the two asset views the same; it only means the account follows the EVM address format.
The card can be tapped to a phone for an MNT workflow that uses NFC, or inserted into a reader when the contact interface is the chosen route. In both cases, the MNT account key remains inside the secure element rather than being handed to the phone, browser, or Web3 connection.
The Dual-Card Set ships uninitialised, which is important when setting up an MNT account from the beginning. During setup, the seed is generated inside both secure elements. That makes the second card the backup for the same card-generated account that can later be used for native MNT on Mantle Network or ERC-20 MNT on Ethereum.
By default, the MNT setup does not ask you to write down a recovery phrase. The backup is the second smart card created during the same setup process. Importing a BIP39 seed of 12 or 24 words is available as an advanced option, but that is not the default path for the Dual-Card Set.
This backup model is especially clear for MNT because the asset has two routes but one key principle. Whether you add Mantle Network for native MNT or add the Ethereum ERC-20 MNT token, the card-generated seed controls the EVM account behind the 0x address. The second card is therefore a backup for the account, not a separate MNT configuration entry.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set is the product for this two-card setup. For an MNT buyer, the second card is part of the default backup model rather than a separate accessory selected after setup.
The free Cryptnox app is available on iOS and Android, and it is the mobile route for pairing the smart card with an MNT workflow. For native MNT, the app is used alongside the Mantle Network entry. For ERC-20 MNT, the app is used alongside the Ethereum token entry at 0x3c3a81e81dc49a522a592e7622a7e711c06bf354.
The app connects to Web3 through WalletConnect and works with MetaMask. That matters for MNT because the asset may be viewed through an EVM network configuration rather than a pre-programmed coin entry. When Mantle Network is selected, the EVM account is being used in the native MNT context. When Ethereum mainnet is selected with the MNT token contract added, the EVM account is being used in the ERC-20 token context.
Unlock for an MNT session uses the phone’s face or fingerprint check through the Cryptnox app. The card itself has no fingerprint sensor or face sensor. The phone handles the local unlock step, while the card keeps the private key for the Mantle or Ethereum EVM account inside the secure element.
General setup guidance for the card and app is available in the Cryptnox hardware wallet tutorials. For MNT, use that setup guidance with the asset-specific choice on this page: add Mantle Network for native MNT, or add the Ethereum ERC-20 token contract for token MNT.
Before receiving MNT, decide whether the sender is using Mantle Network native MNT or Ethereum mainnet ERC-20 MNT. Both routes can use a 0x-prefixed EVM address, so the address shape alone does not tell you which network view should be added in the wallet interface.
If the MNT is native on Mantle Network, add Mantle Network and view the asset as the native gas coin on that EVM-compatible network. If the MNT is on Ethereum mainnet, add the ERC-20 token contract 0x3c3a81e81dc49a522a592e7622a7e711c06bf354. The Cryptnox card protects the key for the EVM address in either case, but the receiving context must match the route being used.
For buyers comparing MNT with other supported assets before ordering, the Cryptnox coin and blockchain support page is the broader place to review asset coverage. The MNT decision remains specific: Mantle Network for native MNT, or Ethereum mainnet for the ERC-20 MNT token.
MNT uses a 0x-prefixed 20-byte EVM address, so it is useful to compare it with another EVM asset page when you are checking how network entries work. The Polygon hardware wallet page is a relevant comparison because Polygon also sits in an EVM-style address environment, while Mantle Network remains a separate network that must be added for native MNT.
A non-EVM comparison is useful for the opposite reason. The Tron hardware wallet page helps show why MNT should not be treated as a generic coin entry: Mantle MNT belongs to the EVM address format, while Tron uses a different asset environment.
Bitcoin is also outside the MNT setup pattern. The Bitcoin hardware wallet page is a separate comparison point for buyers who want to distinguish an EVM network-and-token route from a non-EVM asset route.
The broader crypto hardware wallet collection brings those asset pages together. For MNT, the key takeaway is narrower: the card protects the private key for an EVM account, and the wallet interface must be configured for either Mantle Network native MNT or Ethereum ERC-20 MNT.
An MNT holder setting up Cryptnox starts with an uninitialised Dual-Card Set, then creates the seed inside both secure elements during setup. After the card-generated account is ready, the MNT-specific step is to add the correct EVM route: Mantle Network for native MNT, or the Ethereum ERC-20 token contract for token MNT.
The cards are made in Switzerland, and the product line is Swiss-engineered. For an MNT buyer, the practical value is the smart card model: a contact and NFC card protects the private key for the 0x address, while the mobile app and connected Web3 tools provide the Mantle Network or Ethereum token context.
The MNT setup is therefore not about receiving a card with Mantle already enabled. It is about creating a protected EVM account on the Dual-Card Set, then adding the Mantle Network or ERC-20 token view that matches the MNT you intend to hold.
No. MNT is not pre-programmed on the card. Add Mantle Network once when you want native MNT on Mantle Network, or add the Ethereum ERC-20 MNT token once with contract address 0x3c3a81e81dc49a522a592e7622a7e711c06bf354. The card protects the private key for the EVM account.
You can hold MNT as the native gas coin on the EVM-compatible Mantle Network, and you can also hold the Ethereum ERC-20 MNT token. The ERC-20 route uses contract address 0x3c3a81e81dc49a522a592e7622a7e711c06bf354. Both routes use a 0x-prefixed 20-byte EVM address.
Yes. The Dual-Card Set ships uninitialised, and the seed is generated inside both secure elements during setup. That makes the second card the backup for the EVM account used with MNT. By default, there is no recovery phrase to write down, although importing a BIP39 seed of 12 or 24 words is an advanced option.
Private keys are generated inside the secure element and never leave it. For MNT, that applies to the EVM account used on Mantle Network and to the EVM account used for the Ethereum ERC-20 token route. The network or token entry changes the asset view; the card protects the key.
Yes. The free Cryptnox app is available on iOS and Android, connects to Web3 through WalletConnect, and works with MetaMask. For MNT, add Mantle Network for the native route, or add the Ethereum ERC-20 token with its contract address for the token route.
Yes. The card is a contact and NFC smart card, so an MNT holder can tap it to a phone or insert it into a reader. The physical interface does not decide the asset route. You still add Mantle Network for native MNT or the Ethereum ERC-20 token for token MNT.
No. The card has no fingerprint sensor or face sensor. Unlock uses the phone’s face or fingerprint check through the Cryptnox app. For an MNT account, the phone handles the local unlock step while the card keeps the EVM private key inside the secure element.
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.