Yes. The Cryptnox Crypto Hardware Wallet – Dual-Card Set can hold mETH as an ERC-20 token on Ethereum or as the EVM token representation on Mantle Network after you add the network or token if needed. mETH is not pre-programmed on the card. The private key for the 0x address is generated inside the secure element and never leaves it while the card signs mETH transactions.
CRYPTNOX products are also available worldwide through our official Amazon stores.
Mantle Staked Ether can be held with Cryptnox in two routes: mETH as an ERC-20 token on Ethereum, or the EVM token representation on Mantle Network. Both routes use an 0x-prefixed 20-byte EVM address, so the address format looks familiar even when the network route changes. Before receiving mETH, choose the route that matches the sender, exchange, bridge, or Web3 application you plan to use.
Mantle presents the asset through its own mETH Protocol materials, and the Ethereum ERC-20 token can be viewed through the public Ethplorer mETH token view. For wider planning across assets and networks, the Cryptnox coin and blockchain support page helps you check which routes you want to use with the card.
The important point for mETH is that the token view and the network view must match. An Ethereum mETH transfer belongs on Ethereum. A Mantle Network mETH transfer belongs on Mantle Network. The same 0x-style address can appear in both places, but the network choice decides where the token is received and shown.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set protects the private key used by your mETH address by generating it inside the secure element. The private keys never leave the secure element. For an asset such as mETH, that means the key behind the 0x address is not exposed as a software wallet key during normal card use.
The card uses an EAL6+-certified chip. That certification belongs to the chip platform, not to the finished wallet product. For a buyer holding mETH, the practical point is simple: the signing key is created and kept inside the card’s secure element, and transactions are signed through the card rather than by exporting the private key.
This is especially relevant because mETH can appear on more than one EVM route. The same card-backed address structure can be used after the proper network or token has been added, but the card does not decide the route for you. You choose Ethereum or Mantle Network in the wallet flow, then sign the transaction with the card.
The Cryptnox card is a contact and NFC smart card. You can tap it to a phone or insert it into a reader. That dual-interface form factor matters for mETH users who may want to review a token action on a phone and also keep the card experience close to a smart-card workflow.
mETH is not pre-programmed on the Cryptnox card. Treat mETH setup as a one-time network or token addition before you receive or manage the asset. If you are using Ethereum, the asset route is the ERC-20 token on Ethereum. If you are using Mantle Network, the route is the EVM token representation on Mantle’s EVM L2.
The free Cryptnox app is available on iOS and Android. Unlock in the app can use the phone’s fingerprint or face unlock, and the card itself has no fingerprint or face sensor. That distinction matters because the physical card protects the key, while the phone app provides the wallet interface used to reach the mETH network or token view.
If you want a broader product walkthrough before setting up mETH, the Cryptnox tutorials for hardware wallet products page is the best starting point for learning the app and card workflow. The mETH-specific part of that workflow is the manual network or token addition, because mETH is not shipped as an enabled asset on the card.
The setup order should be deliberate: initialise the Dual-Card Set, confirm that your EVM address is available, add the relevant mETH route, then receive a transfer only on the route you selected. That sequence reduces confusion between Ethereum ERC-20 mETH and the Mantle Network token representation.
The Dual-Card Set ships uninitialised. During setup, the seed is generated inside both secure elements, so the second card is the backup. For mETH, that means the backup card protects access to the same card-generated wallet that holds the Ethereum ERC-20 mETH route or the Mantle Network route you add.
By default, there is no recovery phrase to write down. The second card is the backup for the wallet created during setup. Importing a 12- or 24-word BIP39 recovery phrase is an advanced option, not the default setup path for the Dual-Card Set.
mETH can be managed on Ethereum or on Mantle Network, and both routes depend on the same kind of EVM address format. If you add the correct network and token view on a replacement phone or wallet interface, the backup card can sign for the same wallet because the seed was created inside both secure elements during setup.
This backup model is different from a setup where the buyer must immediately store a written phrase before using the wallet. With the Dual-Card Set, the backup is part of the two-card setup itself. For an mETH holder, the practical task is to keep the second card separate from the primary card and to remember which route was used for each mETH transfer.
The backup card does not make mETH pre-programmed. You still add Ethereum token details or Mantle Network token details when the wallet interface needs them. The backup card protects the same underlying wallet keys; the network and token display settings remain part of the wallet setup experience.
The free Cryptnox app connects to Web3 through WalletConnect and works with MetaMask. For mETH, that gives you a way to use the card-backed EVM address when interacting with Ethereum or Mantle Network flows that expect an 0x address. The key stays inside the secure element while the card handles signing.
mETH users should pay attention to the network selected in the Web3 interface. If the asset is being handled as an ERC-20 token on Ethereum, the interface should be on Ethereum. If the asset is being handled as the Mantle Network token representation, the interface should be on Mantle Network after that network has been added if needed.
If you are comparing where Cryptnox fits among cold-storage options, the best crypto hardware wallet collection gives a broader view of the product family. For this page, the mETH-specific decision is narrower: choose Ethereum ERC-20 mETH or the Mantle Network EVM route, add what is missing, and sign with the card.
The same buyer may hold multiple EVM assets, but mETH should not be treated as a generic token entry. Its support route depends on whether the transfer is on Ethereum or Mantle Network. WalletConnect and MetaMask can help reach Web3 flows, but the route and token view still need to be selected correctly before signing.
The main operational risk with mETH is not the address format; it is the route. Ethereum and Mantle Network can both use 0x-prefixed 20-byte EVM addresses, so an address can look right even when the selected network is wrong for the transfer you intend to make.
Before you receive mETH, ask the sender which route they will use. If the sender is transferring the ERC-20 token on Ethereum, prepare the Ethereum token view. If the sender is transferring the Mantle Network token representation, prepare Mantle Network and add the token if needed. Do not rely only on the address shape.
The same habit applies when sending. Select the network first, then confirm the token, then review the 0x address, then sign. The Cryptnox card protects the private key during signing, but it is still the user’s job to choose the mETH route that matches the transaction.
If you are building a multi-asset setup, it can help to compare mETH with other network-specific wallet pages. The hardware wallet for Polygon page is useful for another EVM network context, while the hardware wallet for Tron page shows a different chain family. Those comparisons make the mETH point clearer: for this asset, Ethereum and Mantle Network are the two routes to set up.
The product for this setup is the Cryptnox Crypto Hardware Wallet – Dual-Card Set. It is a Swiss-engineered contact and NFC smart card set for buyers who want a card-based way to hold the key behind an mETH EVM address. You can buy it from the official Cryptnox Crypto Hardware Wallet – Dual-Card Set product page.
For mETH, the purchase decision should be tied to the support route you actually need. The card can hold mETH as an ERC-20 token on Ethereum or as the EVM token representation on Mantle Network after you add the network or token if needed. It does not arrive with mETH already enabled as a pre-set asset.
If your wallet planning extends beyond mETH, the hardware wallet for Bitcoin page covers a non-EVM asset context, and the hardware wallet for Ronin page covers another network-specific setup. Those pages are useful comparisons, but the mETH setup remains specific: Ethereum ERC-20 mETH or Mantle Network mETH, using an 0x-prefixed EVM address.
Buyers who want the shortest safe path should set up the two cards first, confirm the app workflow, add the correct mETH route, and only then receive funds. That order matches the way mETH is actually held with Cryptnox: not as a pre-programmed card asset, but as an EVM token route added to a card-protected wallet.
Yes. Cryptnox can hold mETH as an ERC-20 token on Ethereum or as the EVM token representation on Mantle Network. The asset is not pre-programmed on the card, so you add the network or token if needed before receiving or managing mETH.
mETH uses an 0x-prefixed 20-byte EVM address with Cryptnox. That address format applies whether you are using the Ethereum ERC-20 route or the Mantle Network route. The address can look similar across routes, so always check the selected network before receiving or sending.
No. mETH is not pre-programmed on the card. After setup, you add Mantle Network or add the mETH token once if the wallet flow does not already show it. Ethereum mETH is handled as an ERC-20 token, while Mantle Network uses the EVM token representation.
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 same wallet that can hold mETH after the correct Ethereum or Mantle Network token route is added.
No. The card itself has no fingerprint or face sensor. Unlock can use the phone’s fingerprint or face unlock through the Cryptnox app, while the private key remains generated and stored inside the card’s secure element.
Yes. The free Cryptnox app connects to Web3 through WalletConnect and works with MetaMask. For mETH, select the correct route first: Ethereum for ERC-20 mETH or Mantle Network for the EVM token representation, then sign with the card.
No recovery phrase is required by default for the Dual-Card Set. The second card is the backup because the seed is generated inside both secure elements. Importing a 12- or 24-word BIP39 recovery phrase is an advanced option, not the default path.
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.