Yes—Cryptnox supports alUSD by adding it once as the Ethereum ERC-20 token at 0xBC6DA0FE9aD5f3b0d58160288917AA56653660E9. alUSD is not pre-programmed on the cards, so setup means choosing Ethereum and verifying the exact contract address before receiving funds. The Cryptnox Crypto Hardware Wallet – Dual-Card Set then protects the Ethereum account that holds alUSD, with private keys generated inside the secure element and the second initialised card acting as the backup.
CRYPTNOX products are also available worldwide through our official Amazon stores.
alUSD is held with Cryptnox as an ERC-20 token on Ethereum. It is not a native coin on the cards and it does not ship as an enabled asset. The buyer’s setup task is to add the alUSD token once, confirm that the wallet interface is using Ethereum, and receive to the 0x-prefixed Ethereum address controlled by the initialised Cryptnox card set.
The contract address to add is 0xBC6DA0FE9aD5f3b0d58160288917AA56653660E9. Etherscan lists alUSD at this Ethereum token contract, and Alchemix also publishes contract address data in its Alchemix contract-address repository. Those checks matter because alUSD support on this page is the Ethereum ERC-20 route, not a preloaded card asset.
When comparing alUSD with other assets handled through Cryptnox, use the Cryptnox coin and blockchain support page to separate Ethereum ERC-20 token setup from other network routes.
The Dual-Card Set ships uninitialised, so there is no alUSD token display waiting on the cards. Initialise the two cards first, then add alUSD as an Ethereum ERC-20 token. After the token is added with the correct contract, the Ethereum address controlled by the card set is the address to use for alUSD.
The free Cryptnox app is available on iOS and Android. If you want to review the app workflow before setting up the cards or adding the alUSD token, the Cryptnox hardware wallet tutorials are the relevant preparation step for the Dual-Card Set.
Do not rely on the token name alone. The alUSD route for Cryptnox is defined by the Ethereum network, the ERC-20 standard, and the exact contract address. That is why the setup step is not just “find alUSD”; it is “add the Ethereum ERC-20 token at 0xBC6DA0FE9aD5f3b0d58160288917AA56653660E9.”
alUSD uses the standard Ethereum account format: an 0x-prefixed 20-byte EVM address. The Cryptnox cards do not create a separate alUSD-specific address format. They control an Ethereum account, and the alUSD token balance is associated with that account through the ERC-20 contract on Ethereum.
This is the detail to check when moving between wallet interfaces. If a service asks for an alUSD receiving address, use the Ethereum account you intend to control with the Cryptnox Dual-Card Set. If the interface is not set to Ethereum, or if the token contract is not 0xBC6DA0FE9aD5f3b0d58160288917AA56653660E9, it is not the alUSD setup described here.
Network-specific pages are useful when the address model changes. The Cryptnox guide for Polygon hardware wallet use is separate because Polygon is a different network context from alUSD on Ethereum. The Cryptnox guide for TRON hardware wallet use is separate because TRON uses a different network and address model.
For alUSD, backup means maintaining control of the Ethereum private key that can sign for the 0x-prefixed account. The Cryptnox Crypto Hardware Wallet – Dual-Card Set is designed so the second card is the backup after initialisation. During setup, the seed is generated inside both secure elements, so both cards are tied to the same Ethereum account.
That default flow avoids making a handwritten recovery phrase the normal backup method for a new alUSD wallet. A buyer starting fresh can initialise the pair, add alUSD as the Ethereum ERC-20 token, and use the second card as the backup for the same address. Importing an existing BIP39 recovery phrase is an advanced option, not the default way the Dual-Card Set is created.
Because the alUSD balance is associated with the Ethereum address, the backup card is backing up access to that Ethereum account rather than storing a separate alUSD file or separate alUSD account. If alUSD is received at the Cryptnox-controlled address, the initialised card set remains the signing route for transactions from that address.
When you are ready to buy the two-card setup for this alUSD route, use the official Cryptnox Crypto Hardware Wallet – Dual-Card Set product page.
An alUSD transfer is an Ethereum ERC-20 transaction from the 0x-prefixed account controlled by the Cryptnox card set. The private key for that account is generated inside the secure element and never leaves it. The phone or connected wallet interface can prepare the transaction, while the card remains the device that signs for the Ethereum address.
The card is a contact and NFC smart card. For an alUSD holder, that means the signing card can be tapped to a phone in an app-based flow or inserted into a reader in a reader-based flow. The form factor is dual-interface, so alUSD custody is not limited to a tap-only routine.
The security platform uses an EAL6+-certified chip. That rating belongs to the chip/platform. For the alUSD user, the operational point is that the Ethereum private key is created inside the secure element and is not exported to the phone or wallet interface.
The Cryptnox card has no fingerprint or face sensor. Unlock is handled through the phone in the Cryptnox app, using the phone’s own fingerprint or face unlock where the phone supports it. After that phone-side unlock step, the card signs for the Ethereum account that holds the added alUSD token.
The Cryptnox app is free on iOS and Android, connects to Web3 through WalletConnect, and works with MetaMask. For alUSD, that gives you a route to use an Ethereum account while keeping the private key generated inside the card’s secure element.
After alUSD has been added with the correct Ethereum contract, keep checking the same three details during connected use: Ethereum network, the Cryptnox-controlled 0x address, and alUSD at 0xBC6DA0FE9aD5f3b0d58160288917AA56653660E9. WalletConnect or MetaMask can help present the transaction workflow, but the asset route remains the Ethereum ERC-20 token route.
If you are comparing alUSD with other holdings before choosing a custody setup, the Cryptnox hardware wallet collection is a useful starting point. Asset pages such as the guide for Bitcoin hardware wallet use and the guide for Ronin hardware wallet use cover different chain assumptions from alUSD on Ethereum.
Cryptnox fits alUSD buyers who want to hold an Ethereum ERC-20 token with a physical smart card rather than a software-only wallet on a phone. The cards are Swiss-engineered and made in Switzerland. The alUSD workflow is direct: initialise the Dual-Card Set, add one Ethereum ERC-20 contract, receive to the 0x-prefixed address, and sign outgoing transactions with the card.
The alUSD-specific buying decision is whether you are comfortable adding the token manually and verifying the contract before receiving funds. That manual step is part of the support route because alUSD is not pre-programmed. Once the Ethereum token contract is added, the Cryptnox-controlled Ethereum account is the place where the alUSD balance is held.
The Dual-Card Set also keeps the backup model clear for a new alUSD holder. The seed is generated inside both secure elements during initialisation, so the second card is the backup from the beginning. For a buyer setting up a fresh alUSD account, that means the backup is another smart card tied to the same Ethereum address, not a default handwritten phrase.
No. alUSD is not pre-programmed on the cards. Add it once as the Ethereum ERC-20 token using contract 0xBC6DA0FE9aD5f3b0d58160288917AA56653660E9. After the token is added, the Cryptnox-controlled Ethereum address can be used for alUSD.
Use 0xBC6DA0FE9aD5f3b0d58160288917AA56653660E9 for alUSD on Ethereum. The receiving address format is an 0x-prefixed 20-byte EVM address. Compare the contract address exactly before using a newly added alUSD token display.
Choose Ethereum for this alUSD route. alUSD is held as an ERC-20 token on Ethereum, not as a separate asset shipped on the cards. If a wallet interface is showing another network, switch back to Ethereum before using the alUSD contract address.
During Dual-Card Set initialisation, the seed is generated inside both secure elements. That means the second card is tied to the same Ethereum account as the first card. If alUSD is received at that account’s 0x address, the second card is the backup.
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.
No. The private key for the Ethereum account that holds alUSD is generated inside the secure element and never leaves it. The phone or connected wallet interface can prepare the ERC-20 transaction, but signing is handled by the card.
Yes. The free Cryptnox app on iOS and Android connects to Web3 through WalletConnect and works with MetaMask. For alUSD, keep the connected wallet on Ethereum and confirm that the token contract is 0xBC6DA0FE9aD5f3b0d58160288917AA56653660E9.
No. The card has no fingerprint or face sensor. For an alUSD signing session, unlock is handled by the phone through the Cryptnox app, using the phone’s own fingerprint or face unlock where supported. The card remains the signing device for the Ethereum account.
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.