Yes. Wrapped Ether (WETH) is pre-programmed in the Cryptnox app as an ERC-20 token on ZKsync Era Mainnet and Base Mainnet, so no manual WETH token entry is needed on those two networks. For another EVM network, add the network with Add a Network, then add WETH as an ERC-20 token if it is not already visible. WETH actions are approved with the Cryptnox Crypto Hardware Wallet – Dual-Card Set, where private keys are generated inside the secure element and never leave it.
CRYPTNOX products are also available worldwide through our official Amazon stores.
Wrapped Ether (WETH) has a ready route in the Cryptnox app on two EVM networks: ZKsync Era Mainnet and Base Mainnet. On both networks, WETH is already present as a pre-programmed ERC-20 token, so a WETH holder does not need to create a custom token entry before using those two routes.
The network choice matters because WETH is managed through the token layer of the selected EVM network. WETH on ZKsync Era Mainnet is handled from the ZKsync Era Mainnet token entry, while WETH on Base Mainnet is handled from the Base Mainnet token entry. The asset name is the same, but the app route is network-specific.
Before ordering for a specific WETH route, compare the wider token and network list on the Cryptnox coin and blockchain support page.
In the Cryptnox app, WETH on ZKsync Era Mainnet and WETH on Base Mainnet are ERC-20 token entries. The practical order is network first, token second. Select the EVM network where the WETH is held, then use the WETH token entry on that same network.
This distinction is important for WETH because the same token name is available through more than one route. A Base Mainnet WETH action should be reviewed as a Base Mainnet action. A ZKsync Era Mainnet WETH action should be reviewed as a ZKsync Era Mainnet action. The Cryptnox app keeps those entries separate by network.
For WETH on the two pre-programmed networks, the path is direct: select ZKsync Era Mainnet or Base Mainnet, then choose WETH on that network. If the intended WETH is on another EVM chain, Add a Network comes before the token step. Once the EVM network is added, its native coin and ERC-20 tokens deployed on that chain can be managed.
For the ready WETH entries on ZKsync Era Mainnet and Base Mainnet, there is no manual Add a Token step. For WETH or another ERC-20 token on an added EVM network, Add a Token is available when the token is not already visible.
The Cryptnox app includes an expansion route for EVM networks. Any EVM network can be added through Add a Network. After that network is present in the app, its native coin and any ERC-20 token deployed on that chain can be managed. This is the route for WETH when it is not the pre-programmed WETH entry on ZKsync Era Mainnet or Base Mainnet.
The app separates the EVM network step from the ERC-20 token step. Add a Network makes the chain available. Add a Token is the manual route for an ERC-20 token that is not already visible on that added chain. WETH does not need that manual token entry on ZKsync Era Mainnet or Base Mainnet because those two WETH entries are already programmed in the app.
If you are setting up the cards before managing WETH, the Cryptnox startup guide explains the initial app and card workflow for the Dual-Card Set.
For WETH on ZKsync Era Mainnet or Base Mainnet, the Cryptnox card is the signing object behind the app workflow. The private keys for the accounts that manage WETH are generated inside the secure element and never leave it. The app prepares the WETH action for the selected EVM network, and the card is used when authorization is required.
The card uses an EAL6+-certified chip. For WETH, the relevant point is chip-level protection for the key material that authorizes ERC-20 activity on the chosen network. WETH may appear as a visible token entry in the Cryptnox app, but the private key is not moved into ordinary app storage.
The phone can use its own face or fingerprint check when the Cryptnox app is unlocked. The card itself has no fingerprint or face sensor, so WETH authorization stays in the smart-card workflow while the phone handles the app unlock experience.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set ships uninitialised. During setup, the seed is generated inside both secure elements, so the second card becomes the backup for the same accounts that can manage WETH. In the standard setup, the user does not begin by writing down a recovery phrase.
For WETH, that backup model is tied directly to account access. WETH on ZKsync Era Mainnet and WETH on Base Mainnet are ERC-20 token entries controlled by the relevant account keys. If the active card cannot be used, the second initialized card is the backup card for those same accounts.
The standard Dual-Card Set setup is card-based: initialize the two cards together, use one card for WETH activity, and keep the second card as the backup. Importing an existing BIP39 seed is available as an advanced option, but it is not the default setup path for the Dual-Card Set.
This model is useful for WETH holders who want the backup to be another secure-element card rather than a written phrase in the normal starting flow. The seed is generated inside both secure elements, and the backup is the second card from the initialized pair.
The WETH workflow uses the Cryptnox smart-card form factor. The card is dual-interface: tap it to a phone for the mobile app flow, or insert it into a reader for a contact-card flow. For WETH, the app displays the selected EVM network and token entry while the card protects the account keys.
The free Cryptnox app is available on iOS and Android. On ZKsync Era Mainnet and Base Mainnet, WETH is already present in the app as an ERC-20 token. Select the network, select WETH on that network, and present the card when the app requires authorization.
The exact product for this WETH workflow is the Cryptnox Crypto Hardware Wallet – Dual-Card Set, a contact and NFC smart-card pair for the app-based setup described here.
The Cryptnox app connects to Web3 through WalletConnect and works with MetaMask. For WETH, keep the connected workflow aligned with the network-specific token entry in the app. A Base Mainnet WETH action should match the Base Mainnet WETH entry, and a ZKsync Era Mainnet WETH action should match the ZKsync Era Mainnet WETH entry.
That network match is the main check when WETH is used through a connected app flow. WalletConnect and MetaMask provide the connection path, while the card remains the authorization object and the private key remains inside the secure element.
If WETH is one part of a broader hardware-wallet comparison, the best crypto hardware wallet collection groups related Cryptnox pages. Buyers comparing WETH with other asset routes can review the Polygon hardware wallet page, the Bitcoin hardware wallet page, and the Tron hardware wallet page.
WETH is not treated as one generic entry across every chain. The ready route is WETH as a pre-programmed ERC-20 token on ZKsync Era Mainnet and Base Mainnet. Other EVM networks follow Add a Network, and ERC-20 tokens that are not already visible follow Add a Token.
Yes. Wrapped Ether (WETH) is pre-programmed in the Cryptnox app as an ERC-20 token on ZKsync Era Mainnet and Base Mainnet. On those two networks, the user does not need to add WETH manually before managing it with the Cryptnox Crypto Hardware Wallet – Dual-Card Set.
WETH is managed as an ERC-20 token on the relevant EVM network. In the Cryptnox app, the network comes first, then the WETH token entry for that network. WETH on ZKsync Era Mainnet and WETH on Base Mainnet are separate network-specific token entries.
Use Add a Network to add the EVM network. Once the network is added, its native coin and ERC-20 tokens deployed on that chain can be managed. If WETH or another ERC-20 token is not already visible on that added network, Add a Token is the manual route.
Private keys for the accounts that manage WETH are generated inside the secure element and never leave it. The card uses an EAL6+-certified chip, and the Cryptnox app coordinates the WETH workflow for the selected EVM network while the card is used for authorization.
The Dual-Card Set ships uninitialised. During setup, the seed is generated inside both secure elements, so the second card is the backup for the same accounts that can manage WETH. The standard setup does not begin with writing down a recovery phrase.
Yes. The free Cryptnox app on iOS and Android connects to Web3 through WalletConnect and works with MetaMask. For WETH, match the connected workflow to the correct network entry: ZKsync Era Mainnet, Base Mainnet, or another EVM network you added.
The Cryptnox card is a contact and NFC smart card. For WETH management, tap the card to a phone during the mobile app flow, or insert it into a reader for a contact-card flow. The app shows the WETH network and token route; the card protects the private key.
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.