Cryptnox supports LayerZero (ZRO) as an Ethereum ERC-20 token that you add once through Add a Token or Add a Network; it is not pre-programmed on the cards. ZRO is held at a 0x-prefixed 20-byte EVM address controlled by an Ethereum private key generated inside the card secure element and never exported. Former Stargate Finance (STG) holders may use the approved STG Redemption process before holding ZRO.
CRYPTNOX products are also available worldwide through our official Amazon stores.
LayerZero (ZRO) is held with Cryptnox as an ERC-20 token on Ethereum. The Cryptnox Crypto Hardware Wallet – Dual-Card Set does not arrive with ZRO already active, so the ZRO step happens after card initialisation. In the app, the buyer adds ZRO once through Add a Token or Add a Network and selects the Ethereum ERC-20 route.
The address format for ZRO on this route is the standard Ethereum EVM format: a 0x-prefixed 20-byte address. That means the ZRO balance is tied to the Ethereum account controlled by the Cryptnox card, not to a separate LayerZero-specific address format. The private key for that Ethereum account is generated inside the secure element and never leaves it.
For buyers checking whether ZRO sits within their broader Cryptnox setup, the Cryptnox coin and blockchain support page is the right place to review supported asset routes. For this asset, the route to use is specific: Ethereum, ERC-20, and manual addition after the Dual-Card Set is initialised.
ZRO is not shipped as an already enabled card entry. That is important because a buyer preparing to receive ZRO should not look for a preloaded LayerZero option during unboxing. The Dual-Card Set ships uninitialised, and the ZRO token entry is added later in the wallet interface after the Ethereum account has been created inside the card secure elements.
The practical flow is to initialise the Dual-Card Set first, then add LayerZero (ZRO) as an Ethereum ERC-20 token. Once the token is added, the ZRO balance is associated with the 0x-prefixed Ethereum address shown for the card-controlled account. The app interface can display and manage the token route, while the Ethereum private key remains inside the secure element.
This setup distinction is useful when comparing ZRO with other holdings. A buyer reviewing another Ethereum-style route can compare the asset checklist with the Cryptnox Polygon hardware wallet page, while keeping the ZRO route fixed as Ethereum ERC-20 with a 0x-prefixed address.
For a ZRO holder, the asset-specific security question is where the Ethereum private key for the 0x address is created and kept. In the Cryptnox Dual-Card Set, private keys are generated inside the secure element and never leave it. The ZRO token entry is added in the app, but the key that controls the Ethereum account is created and retained in the card hardware.
The card uses an EAL6+-certified chip. That certification belongs to the chip platform. For ZRO, the relevant result is a separation between the wallet interface and the private key: the app can show the Ethereum ERC-20 token route, while the private key for the 0x-prefixed address remains inside the secure element.
Unlocking the Cryptnox app to manage the Ethereum account uses the phone’s biometrics through the app. The card itself has no fingerprint reader or face sensor. For ZRO buyers, that means the phone handles the app unlock step, while the card remains the place where the Ethereum private key for the ZRO-holding address is held.
The Dual-Card Set backup model matters for ZRO because the Ethereum account is created during setup rather than supplied in advance. The set ships uninitialised. During initialisation, the seed is generated inside both secure elements, so the second card becomes the backup for the same Ethereum account that can hold ZRO.
By default, a new ZRO setup does not require writing down a recovery phrase. The backup is the second smart card from the same Dual-Card Set. For a buyer planning to receive ZRO at a 0x-prefixed Ethereum address, the second card is tied to the same wallet route that controls that ERC-20 holding.
The default sequence for a new ZRO holder is straightforward: initialise both cards, add the LayerZero token route, confirm the Ethereum address format, and keep the second card as the backup for that same wallet. Buyers who want to see the card and app flow before adding ZRO can use the Cryptnox hardware wallet tutorials.
The Cryptnox card is a contact and NFC smart card for the Ethereum account that can hold ZRO. You can tap it to a phone or insert it into a reader. This dual-interface form factor is relevant to ZRO because the same 0x-prefixed Ethereum address can be managed through the phone-based Cryptnox app flow or through a reader-based card workflow.
The free Cryptnox app is available on iOS and Android. For ZRO, the app is where the Ethereum ERC-20 token entry is added and where the buyer manages the interface for the card-controlled address. The app connects to Web3 via WalletConnect and works with MetaMask, so ZRO can be used through those supported connection routes after the token entry is added.
The app and Web3 connection route do not change the ZRO address format. ZRO remains an Ethereum ERC-20 token held at the 0x-prefixed address controlled by the private key generated inside the secure element.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set is the product to choose when you want a smart-card hardware wallet for a ZRO Ethereum address. The ZRO workflow uses the Ethereum account created in the secure elements during setup, then adds LayerZero as an ERC-20 token in the app.
For a ZRO buyer, the value of the two-card package is not that ZRO is preloaded. It is that the Ethereum private key for the 0x address is generated inside secure-element hardware, the second card is the backup for the same wallet, and the LayerZero token entry can be added once after initialisation.
If you are comparing ZRO storage with broader hardware-wallet planning, the Cryptnox hardware wallet collection hub explains the wider product family. The ZRO-specific decision remains the Ethereum ERC-20 route: add LayerZero once, then use the 0x-prefixed address controlled by the card.
LayerZero (ZRO) should have its own checklist even when the same buyer uses Cryptnox for several assets. For ZRO, the checklist is Ethereum chain, ERC-20 standard, 0x-prefixed 20-byte EVM address, and manual addition through Add a Token or Add a Network. Those details should not be mixed with the route for a different asset.
A buyer comparing ZRO with BTC storage can review the Cryptnox Bitcoin hardware wallet page because Bitcoin uses a different asset route. A buyer checking another network can compare the ZRO checklist with the Cryptnox Tron hardware wallet page. The comparison is useful because it keeps the ZRO decision anchored to Ethereum ERC-20 rather than treating every asset route as the same.
For ZRO itself, the instruction remains simple: add LayerZero as an Ethereum ERC-20 token, use the 0x-prefixed address from the Cryptnox-controlled Ethereum account, and rely on the Dual-Card Set backup created during initialisation for that same wallet.
No. ZRO is not pre-programmed on the Cryptnox Dual-Card Set. After the cards are initialised, add LayerZero (ZRO) once through Add a Token or Add a Network. Use the Ethereum route because ZRO is held as an ERC-20 token on Ethereum.
Use the Ethereum EVM address shown for the Cryptnox-controlled account. For ZRO on Cryptnox, the address format is a 0x-prefixed 20-byte address because the asset is held as an ERC-20 token on Ethereum. Do not use a non-EVM address route for this setup.
The Ethereum private key that controls the 0x address for ZRO is created inside the card secure element and never leaves it. The ZRO token entry is added in the wallet interface, but the account key behind that ERC-20 holding remains in secure-element hardware.
The Dual-Card Set ships uninitialised. During setup, the wallet seed for the Ethereum account that can hold ZRO is generated inside both secure elements, making the second card the backup for the same wallet. The default setup is not based on writing down a recovery phrase.
Yes. Importing an existing 12- or 24-word BIP39 recovery phrase is an advanced option. The default ZRO setup is different: initialise the Dual-Card Set so the wallet is generated inside both secure elements, then add LayerZero (ZRO) as an Ethereum ERC-20 token.
Yes. The free Cryptnox app on iOS and Android connects to Web3 via WalletConnect and works with MetaMask. For ZRO, first add the asset as an Ethereum ERC-20 token, then use the 0x-prefixed address controlled by the Cryptnox card.
No. The card itself has no fingerprint reader or face sensor. When managing the Ethereum account that can hold ZRO, unlock uses the phone's biometrics through the Cryptnox app, while the card holds the private key for the 0x address 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.