Cryptnox supports Axelar exposure through the wrapped ERC-20/EVM representation of AXL, shown as AXL or wAXL, on Ethereum or another supported EVM chain. It is not a native AXL wallet route for Axelar Network. The asset is not pre-programmed, so add the relevant EVM network or token once. Your receiving address is a 0x-prefixed 20-byte EVM address, controlled by private keys generated inside the secure element and never exported.
CRYPTNOX products are also available worldwide through our official Amazon stores.
AXL has two wallet routes that buyers must keep separate. Native AXL belongs to Axelar Network, a non-EVM Layer 1 environment. The Cryptnox route is the wrapped ERC-20/EVM representation of AXL, shown as AXL or wAXL, on Ethereum or another supported EVM chain.
That distinction decides the address format and the setup path. With Cryptnox, the receiving account for AXL or wAXL is an EVM account with a 0x-prefixed 20-byte address. That address format fits wrapped AXL or wAXL on Ethereum and other supported EVM chains, but it should not be treated as a native Axelar Network destination.
Axelar explains wAXL as the wrapped ERC-20 AXL token, which is the form relevant to the Cryptnox EVM route. Axelar also describes AXL as the token associated with Axelar Network in its AXL token summary, so the network label matters before any transfer.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set does not arrive with AXL already prepared as a visible asset. After initialising the cards, add the EVM network or add the AXL/wAXL token for the specific chain where your wrapped token exists. The user adds it once through Add a Network or Add a Token.
If your wrapped AXL is on Ethereum, the setup is for the Ethereum ERC-20 version. If your wrapped AXL is on another supported EVM chain, the setup follows that chain instead. The same 0x-style address pattern does not replace the need to choose the correct network.
The current network and asset coverage is listed on the Cryptnox supported coins and blockchains page. For the card setup flow before adding an EVM token such as AXL or wAXL, use the Cryptnox hardware wallet tutorials alongside the app.
Wrapped AXL on an EVM chain uses a 0x-prefixed 20-byte address. That is necessary for the Cryptnox AXL route, but it is not the only check. Ethereum and other EVM chains can use addresses that look structurally similar, while the token still exists on the chain selected by the sender.
When a platform offers more than one AXL withdrawal choice, read the asset name and the network name together. A withdrawal marked for native Axelar Network AXL is not the same as a wrapped ERC-20 AXL or wAXL withdrawal. The Cryptnox card-backed account is the destination for the wrapped EVM route.
This is the main operational point for AXL buyers: Cryptnox can secure the EVM account used for AXL or wAXL, but the sending service must send the wrapped token on the matching EVM chain.
For wrapped AXL, the account key that controls the 0x EVM address is generated inside the secure element in the Cryptnox smart card and is not exported. The transaction request can appear through the app or a Web3 interface, but the card remains the signing device for the account that holds AXL or wAXL.
The chip platform used by the card is an EAL6+-certified chip. That certification belongs to the chip platform. For an AXL holder, the important boundary is between the EVM token workflow and the key material: the token may be displayed in an EVM interface, while the private key stays within the card’s secure element.
The free Cryptnox app is available on iOS and Android. For Web3 access, Cryptnox connects through WalletConnect and works with MetaMask. That matters for AXL and wAXL because the supported asset route is an ERC-20/EVM token route rather than native Axelar Network handling.
App unlocking can use the phone’s face or fingerprint check. The smart card itself has no fingerprint reader or face sensor. The local app unlock stays on the phone while the signing key for the AXL/wAXL EVM account remains in the card.
The Dual-Card Set ships uninitialised, so the AXL/wAXL wallet route is created during setup rather than arriving with a prepared account. In the default setup, the seed is generated inside both secure elements, and the second card becomes the backup for the same wallet.
That backup card covers the EVM account used for wrapped AXL because the account derives from the same wallet setup. Once you have used a Cryptnox-backed 0x account for wrapped AXL on Ethereum or another supported EVM chain, the second card is the recovery path for that same wallet rather than a separate AXL account.
The default backup design is card-based, so there is no recovery phrase to copy as the normal setup step. Importing an existing 12- or 24-word BIP39 phrase is available as an advanced option, but it is not the default Dual-Card Set flow.
The product for this AXL/wAXL setup is the Cryptnox Crypto Hardware Wallet – Dual-Card Set. It is a contact and NFC smart card set, so the card can be tapped to a phone or inserted into a reader depending on the workflow.
AXL is easy to confuse with assets that have a single obvious wallet route, because its native Axelar Network form and its wrapped EVM form are not the same destination type. If your portfolio includes multiple chains, keep the AXL rule explicit: Cryptnox is for AXL or wAXL on Ethereum or another supported EVM chain, using a 0x-prefixed EVM address.
The broader Cryptnox hardware wallet collection can help you compare how different assets map to different network models. The Cryptnox hardware wallet page for Polygon covers a native EVM-chain case, while the Ronin hardware wallet page covers another network-specific route.
Assets outside the AXL/wAXL pattern should be checked on their own terms. The Cryptnox hardware wallet page for Tron describes a different chain model, and the Bitcoin hardware wallet page covers an asset that does not use the ERC-20 token route. Those comparisons are useful because AXL support depends on whether the token is the wrapped EVM representation.
Cryptnox fits an AXL buyer who wants to hold the wrapped ERC-20/EVM representation and is willing to verify the network before receiving funds. The card set is not a native Axelar Network wallet route, and it is not pre-programmed with AXL as a ready asset. It is a smart-card route for the EVM account that receives AXL or wAXL on Ethereum or another supported EVM chain.
The form factor is a Swiss-engineered contact and NFC smart card. For an AXL/wAXL holder, that means the same card-based wallet can be used by tapping to a phone in the mobile flow or by inserting the card into a reader where contact use is required. The card format is practical when the asset lives in an EVM interface but the account key should remain inside a separate secure element.
If those points match how you plan to hold Axelar exposure, the Dual-Card Set gives you a clear route: create the wallet on the cards, add the correct EVM network or token, and use the card-backed 0x account for AXL or wAXL only.
No. The Cryptnox route for Axelar exposure is wrapped ERC-20/EVM AXL or wAXL on Ethereum or another supported EVM chain. Native AXL on Axelar Network is a different route and should not be sent to a Cryptnox EVM address as though it were the wrapped token.
AXL or wAXL uses a 0x-prefixed 20-byte EVM address when held through the supported Cryptnox route. That address format matches Ethereum and other supported EVM chains. Check the address format together with the withdrawal network, because multiple EVM chains can use similar-looking 0x addresses.
No. The Dual-Card Set ships uninitialised, and AXL is not pre-programmed as a visible asset. After setup, add the relevant EVM network or add the AXL/wAXL token once. The correct setup depends on where your wrapped AXL exists, such as Ethereum or another supported EVM chain.
During the default Dual-Card Set setup, the seed is generated inside both secure elements. The second card is therefore the backup for the same wallet, including the EVM account used for AXL or wAXL. The default backup method is the second card, not a recovery phrase copied during setup.
Yes. The Cryptnox app is free on iOS and Android, connects to Web3 through WalletConnect, and works with MetaMask. For AXL or wAXL, that is relevant because the supported asset route is an ERC-20/EVM token route rather than native Axelar Network AXL.
The private keys for the Cryptnox-backed EVM account are generated inside the smart card’s secure element and do not leave it. The card uses an EAL6+-certified chip platform. For AXL or wAXL, the token sits on an EVM chain while the signing key remains inside the card.
No. The card has no fingerprint reader or face sensor. When local app unlocking is needed, the Cryptnox app can use the phone’s face or fingerprint check. That phone unlock is separate from where the AXL/wAXL account key is held: inside the card’s 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.