Yes. Cryptnox supports Across Protocol (ACX) as an ERC-20 token on Ethereum at contract 0x44108f0223A3C3028F5Fe7AEC7f9bb2E66beF82F. ACX is not pre-programmed on the card; add it once through Add a Network or Add a Token. The Dual-Card Set secures the Ethereum private key for the 0x-prefixed ACX address, with the key generated inside the secure element and kept there.
CRYPTNOX products are also available worldwide through our official Amazon stores.
Across Protocol (ACX) is held with Cryptnox through its Ethereum ERC-20 token route. The token contract to add is 0x44108f0223A3C3028F5Fe7AEC7f9bb2E66beF82F. That contract is the setup detail that makes ACX distinct from a native coin: the card does not arrive with ACX already visible, and ACX is not treated as its own native network on the card.
For a buyer holding ACX, the practical setup is an Ethereum account controlled by the Cryptnox Dual-Card Set. ACX is displayed as an ERC-20 token associated with that Ethereum account. The receiving address is a 0x-prefixed 20-byte EVM address, so the ACX receiving format is the same address format used for Ethereum accounts.
The official Across Protocol site identifies the ACX project, while the Ethereum contract is the operational detail to use in the wallet interface. If you want to check how Cryptnox groups coins, tokens, and chains before adding ACX, review the Cryptnox coin and blockchain support page alongside the ACX contract details.
ACX must be added once during the wallet setup flow. Use Ethereum as the chain, then add ACX by its ERC-20 contract. Depending on the wallet screen in front of you, the action may be labelled Add a Token, or the route may involve Add a Network before the token is added. The important point is that the visible ACX balance comes from the Ethereum token contract, not from an ACX application already placed on the card.
Before receiving ACX, confirm that the wallet interface shows Ethereum, the ACX symbol, and the exact contract 0x44108f0223A3C3028F5Fe7AEC7f9bb2E66beF82F. A wrong contract can show a lookalike token or a confusing balance, even when the underlying Ethereum address belongs to you. The Cryptnox card secures the key for the Ethereum address; the token entry tells the interface which ERC-20 balance to display for that address.
For card setup steps before adding the ACX token, use the Cryptnox hardware wallet tutorials. Those guides are most useful before the first ACX transfer, because the card pair should already control the Ethereum address that will hold the token.
ACX is controlled by the Ethereum private key for the address that holds the ERC-20 token. The public ACX contract is not the secret. The sensitive element is the private key that can approve Ethereum transactions affecting the ACX balance. With Cryptnox, that private key is generated inside the secure element and never leaves it, so the Ethereum account used for ACX is not created in phone software and then copied onto the card.
For ACX transfers, the card’s role is to protect the Ethereum signing key while the connected wallet interface prepares the token action. The interface can show ACX, request a transfer, or connect to a Web3 flow, but the private key remains inside the secure element during the approval path. This distinction matters for ERC-20 tokens because the token balance is visible on Ethereum, while the authority to move it comes from the address key.
The secure element used for the Ethereum key that controls ACX has an EAL6+-certified chip. That property belongs to the chip platform. For an ACX holder, the practical outcome is that the Ethereum private key is generated and retained in secure hardware while ACX remains an ERC-20 token added by contract in the wallet interface.
If you compare the ACX route with the broader Cryptnox crypto hardware wallet collection, the key difference is the token layer. ACX does not require a separate address format from Ethereum; it uses the Ethereum address secured by the card set.
The Dual-Card Set ships uninitialised, which matters when planning an ACX holding setup. During initialisation, the seed is generated inside both secure elements, and the second card becomes the backup for the same wallet. For ACX, that means the backup protects access to the Ethereum address that will hold the ERC-20 token, rather than backing up a separate ACX account.
There is no recovery phrase to write down by default. The default backup is the second card in the set, initialised with the same wallet seed. Importing an existing BIP39 recovery phrase is available as an advanced option, but the normal Dual-Card Set setup creates the seed inside both secure elements. Buyers who intend to receive ACX should complete this paired-card setup before sending ACX to the Ethereum address.
This backup model fits an ERC-20 token such as ACX because the token is not recovered separately. Access follows the Ethereum wallet seed generated in the two secure elements, and the ACX balance is tied to the Ethereum address derived from that wallet.
The free Cryptnox app on iOS and Android is the app used with the card set when managing the Ethereum account that can hold ACX. The app connects to Web3 through WalletConnect and works with MetaMask, which gives ACX holders a route to use Ethereum wallet software while keeping the Ethereum private key on the card.
When an ACX transfer or approval request is reviewed, unlock uses the phone’s biometrics through the Cryptnox app. The card itself has no biometric sensor. This matters for ACX because the phone provides the user unlock step, while the card remains responsible for the secure operation involving the Ethereum key.
ACX still needs to be added by its Ethereum contract in the connected wallet interface. WalletConnect and MetaMask do not change the ACX support route; they provide ways to interact with Ethereum wallet flows while the Cryptnox card keeps the private key inside the secure element.
The Cryptnox card is a contact and NFC smart card. For an ACX holder, that means the same Ethereum account can be managed by tapping the card to a phone or by inserting the card into a reader. ACX remains an Ethereum ERC-20 token in either case; the card form factor changes how the card is presented, not the ACX contract or the 0x-prefixed address format.
A typical ACX action starts in software: the wallet interface shows the Ethereum address, the ACX ERC-20 token entry is present, and a transfer or Web3 action is prepared. The card is then used for the secure approval step. The Ethereum private key is not exported to the app or to the connected wallet interface as part of that ACX flow.
The contact and NFC design is useful because ACX management is not a single-screen task. You may add the token, confirm the address, connect a wallet flow, and then approve an action. Across those steps, the card’s job stays narrow and important: protect the Ethereum key that controls the ACX balance.
The product for this ACX setup is the Cryptnox Crypto Hardware Wallet – Dual-Card Set. For ACX, the reason to choose the dual-card product is not that ACX is preloaded. The reason is that the set can secure the Ethereum private key for the 0x-prefixed address where the ACX ERC-20 token is held, while the second card serves as the backup after paired initialisation.
The card set is Swiss-engineered and built around a dual-interface smart card form factor. For an ACX buyer, that form factor supports two practical handling methods: tap the card to a phone during the app workflow, or insert the card into a reader when that route is used. The ACX support route stays the same in both cases: Ethereum, ERC-20, and the contract 0x44108f0223A3C3028F5Fe7AEC7f9bb2E66beF82F.
Before buying for an ACX use case, decide whether you want a card-based Ethereum key setup for ACX alone or for ACX alongside other assets. ACX uses Ethereum and an ERC-20 contract. If you are also planning a separate Polygon setup, the hardware wallet for Polygon information belongs to that network route, not to the ACX contract entry. If your portfolio planning includes Tron, use the hardware wallet for Tron page for that separate address environment.
ACX should be funded only after the Ethereum address, card pair, and token contract entry are correct. The same planning discipline applies when comparing ACX with non-token routes such as the hardware wallet for Bitcoin page: ACX follows Ethereum ERC-20 rules, while other assets may follow their own address and network model.
No. ACX is not pre-programmed on the card. Add it once as an Ethereum ERC-20 token using contract 0x44108f0223A3C3028F5Fe7AEC7f9bb2E66beF82F. Depending on the wallet flow, the setup may use Add a Network or Add a Token, but the ACX route is still Ethereum ERC-20.
Use Ethereum for ACX. The supported ACX route is the ERC-20 token on Ethereum, and the receiving address is a 0x-prefixed 20-byte EVM address. Before receiving ACX, confirm that the wallet interface shows Ethereum and the ACX contract 0x44108f0223A3C3028F5Fe7AEC7f9bb2E66beF82F.
Cryptnox protects the Ethereum private key for the address that holds ACX. ACX itself is an ERC-20 token at a public contract address, while control of the token balance depends on the Ethereum account key. That private key is generated inside the secure element and never leaves it.
Yes. The Dual-Card Set ships uninitialised, and the seed is generated inside both secure elements during setup. The second card is the backup for the same wallet, so it backs up access to the Ethereum address where the ACX ERC-20 token is held.
No. In the default Dual-Card Set setup, there is no recovery phrase to write down. The seed is generated inside both secure elements, and the second card acts as the backup. Importing an existing BIP39 recovery phrase is an advanced option for users who choose that workflow.
Unlocking uses the phone’s biometrics through the Cryptnox app. The card itself has no biometric sensor. For ACX, the phone handles the unlock step in the app, while the card keeps the Ethereum private key inside the secure element during the approval process.
Yes. The free Cryptnox app on iOS and Android connects to Web3 through WalletConnect and works with MetaMask. ACX still needs to be added as the Ethereum ERC-20 token with contract 0x44108f0223A3C3028F5Fe7AEC7f9bb2E66beF82F.
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.