Yes. Cryptnox supports native STRAX on Xertra Mainnet by adding Xertra once as a custom EVM network in the Cryptnox app; STRAX is not pre-programmed on the cards. STRAX uses an 0x-prefixed 20-byte EVM address on its own EVM L1. With the Cryptnox Crypto Hardware Wallet – Dual-Card Set, private keys are generated inside the secure element and never leave it, and the second card is the backup.
CRYPTNOX products are also available worldwide through our official Amazon stores.
STRAX is held on Cryptnox as the native coin of Xertra Mainnet, an EVM L1 network. The network was formerly known as StratisEVM or Stratis Mainnet, and the STRAX ticker remains the same after the move to the Xertra name.
For a buyer setting up a hardware wallet, the practical point is that STRAX is not a preloaded switch on the card. You add Xertra Mainnet once in the Cryptnox app through the custom EVM network route, then use the resulting 0x account for native STRAX activity on that chain.
Xertra describes its mainnet as live in its own network announcement for StratisEVM/Xertra Mainnet. That supports the setup route used here: native STRAX belongs on Xertra Mainnet, not on a different EVM network simply because the address style looks familiar.
The address format matters, but it is not enough by itself. A STRAX address can look like an Ethereum-style account because it begins with 0x, yet the selected network must still be Xertra Mainnet when you are working with native STRAX.
The Dual-Card Set reaches you without an initial wallet state, so the first STRAX decision happens during your own setup rather than at the factory. After the cards are initialised, add Xertra Mainnet in the free Cryptnox app for iOS or Android and use that configured EVM network for the STRAX account.
The useful buyer distinction is between the private key and the network view. The card protects the private key for the 0x address, while the app tells your wallet interface which EVM L1 you are using. For STRAX, that EVM L1 is Xertra Mainnet.
For setup guidance around the app and card workflow, use the Cryptnox hardware wallet tutorials. For a wider view of assets and networks that can be configured, review the Cryptnox coin and blockchain support page.
This page is specifically about native STRAX. If you also manage other networks, compare the route here with the Cryptnox Polygon hardware wallet page, where the network assumptions are different even though Polygon also uses EVM-style addresses.
STRAX on Xertra Mainnet uses an 0x-prefixed 20-byte EVM address. That can be convenient if you already recognise EVM account formatting, but it also creates the main setup risk: the same visible address style can appear across multiple EVM networks.
For native STRAX, the network label is not cosmetic. The Cryptnox app or connected Web3 route must be pointing to Xertra Mainnet before the account is used for STRAX. An 0x address shown under another EVM network is not automatically a Xertra STRAX account.
This is why the STRAX setup should be treated as a chain-specific configuration, not as a general EVM assumption. The card keeps the private key for the account, and Xertra Mainnet is the network context that makes that account relevant for native STRAX.
The same principle applies when comparing STRAX with other EVM-like assets. The Cryptnox Ronin hardware wallet page is useful for comparison because it also involves a named network route; STRAX still belongs under Xertra Mainnet.
For a native STRAX holder, the sensitive item is not the public 0x address. The sensitive item is the private key that controls that address on Xertra Mainnet. With the Cryptnox card, private keys are generated inside the secure element and never leave it.
The secure element uses an EAL6+-certified chip. In the STRAX setup, that means the key controlling the Xertra 0x account is created inside the card’s protected environment rather than being created as a normal file on a phone or browser.
Unlocking the STRAX workflow happens through the Cryptnox app using the phone’s local biometric unlock. The card itself has no biometric sensor. In practice, the phone handles the app unlock step, while the card remains the place where the STRAX private key is held and used.
This separation is important for a custom EVM network such as Xertra. The app can add, remove, or re-add the Xertra Mainnet view, but the private key for the STRAX account remains in the card’s secure element. Network configuration and key custody are separate parts of the same wallet workflow.
If you are choosing hardware for several assets, the Cryptnox hardware wallet collection gives the broader product context, while this STRAX page explains the specific Xertra route.
The Dual-Card Set uses a two-card setup that is especially relevant for a custom-network asset like STRAX. During standard setup, the seed is generated inside both secure elements, so the second card is the backup for the same wallet seed that controls the Xertra 0x account.
That matters because Xertra Mainnet is a configuration you can add again, while the wallet seed is the part that must continue to control the same account. If the app view is rebuilt later, adding Xertra Mainnet again restores the STRAX network view around the same card-held key material.
By default, there is no recovery phrase to write down during the standard Dual-Card Set setup. The backup relationship is between the two cards in the set: both secure elements receive the seed during initialisation, and the second card is kept as the backup for access to the same wallet.
Importing an existing BIP39 recovery phrase is available as an advanced option. That is different from the standard STRAX buyer flow, where the two-card setup creates the seed inside the secure elements and the user then adds Xertra Mainnet in the app.
The hardware sold for this STRAX setup is the Cryptnox Crypto Hardware Wallet – Dual-Card Set. For native STRAX, the product gives you one primary smart card and one backup smart card for the Xertra EVM account structure.
The free Cryptnox app on iOS and Android connects to Web3 through WalletConnect and works with MetaMask. For STRAX, that connection should come after Xertra Mainnet has been added as the custom EVM network, because the asset is native to Xertra rather than a token on another chain in this setup.
When MetaMask or a WalletConnect flow shows an EVM-style account, keep the STRAX chain context in view. The account address can be 0x-prefixed, but native STRAX activity still depends on Xertra Mainnet being the selected network.
A clear Web3 sequence for STRAX is simple: configure Xertra Mainnet, confirm the 0x address, and then use the Cryptnox app’s supported Web3 route. The card remains responsible for the private key, while WalletConnect or MetaMask provides the interface path to the configured network.
This distinction is useful if your portfolio includes assets that do not share Xertra’s assumptions. The Cryptnox Tron hardware wallet page and the Cryptnox Bitcoin hardware wallet page show very different network contexts, while STRAX remains a native coin on Xertra Mainnet.
The Cryptnox wallet used for STRAX is a contact and NFC smart card. You can tap it to a phone when using the Cryptnox app, or insert it into a reader when a contact smart-card setup is preferred.
For Xertra, the form factor changes how you present the card to the device, not which chain the account uses. The STRAX account is still the 0x-prefixed EVM address under Xertra Mainnet, and the private key for that account is still generated inside the card’s secure element.
This card format suits STRAX buyers who want the network configuration to live in the app while the key stays on the smart card. The app supplies the iOS or Android route, WalletConnect and MetaMask provide Web3 paths, and the card supplies the secure-element key control for the Xertra account.
Choose the Dual-Card Set for STRAX if you want native STRAX on Xertra Mainnet, a second card as the backup, and a Swiss-engineered smart-card wallet that supports both contact and NFC use. The only STRAX-specific setup step to plan for is adding Xertra Mainnet once as the custom EVM network before using the account.
No. STRAX is not pre-programmed on the cards. The buyer adds Xertra Mainnet once as a custom EVM network in the Cryptnox app, or uses Add a Token when that route is shown. After that, native STRAX is handled through the configured Xertra account.
Choose Xertra Mainnet. STRAX is the native coin of Xertra Mainnet, an EVM L1 that was formerly known as StratisEVM or Stratis Mainnet. The ticker remains STRAX, but the current network name to use in the wallet setup is Xertra Mainnet.
STRAX on Xertra Mainnet uses an 0x-prefixed 20-byte EVM address. The address may look like addresses used on other EVM networks, so network selection matters. For native STRAX, the configured network should be Xertra Mainnet.
Yes. In the standard Dual-Card Set setup, the seed is generated inside both secure elements, making the second card the backup. If the app setup is rebuilt later, Xertra Mainnet can be added again so the STRAX view points to the same wallet seed.
Yes. The Cryptnox app connects to Web3 through WalletConnect and works with MetaMask. For STRAX, add Xertra Mainnet as the custom EVM network first, then use the configured 0x account through the Web3 route.
No. Unlocking uses the phone’s local biometric unlock through the Cryptnox app, and the card itself has no biometric sensor. The card remains a contact and NFC smart card used by tapping to a phone or inserting into a reader.
Importing an existing BIP39 recovery phrase is an advanced option, not the default setup. The standard Dual-Card Set flow generates the seed inside both secure elements, then the user adds Xertra Mainnet for native STRAX.
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.