Yes. Cryptnox supports AURORA as an EVM token after you add it once: either the Ethereum ERC-20 token at 0xaaaaaa20d9e0e2461697782ef11675f668207961 or the Aurora-network ERC-20-equivalent token at 0x8bec47865ade3b172a928df8f990bc7f2a3b9f79. AURORA is not pre-programmed on the card, and this is not a native NEAR-format holding route. The receiving address is a 0x-prefixed 20-byte EVM address, with private keys generated inside the secure element and kept there.
CRYPTNOX products are also available worldwide through our official Amazon stores.
AURORA on Cryptnox is an EVM-token setup, not a native NEAR account setup. The asset can be held through the Ethereum ERC-20 contract 0xaaaaaa20d9e0e2461697782ef11675f668207961, or through the Aurora-network ERC-20-equivalent contract 0x8bec47865ade3b172a928df8f990bc7f2a3b9f79. Aurora describes its network as EVM-compatible on NEAR in the Aurora documentation, which is why the wallet route here uses Ethereum-style addresses rather than native NEAR-format accounts.
The Cryptnox coin and blockchain support page is useful when you need to compare AURORA with assets that use different address formats. For this asset, the key distinction is simple: the Cryptnox card controls the private key for the EVM address, while the AURORA token record is added afterward for the route you intend to use.
The two AURORA routes share an Ethereum-style address format, but they are not the same token route. On Ethereum, AURORA is added as an ERC-20 token using 0xaaaaaa20d9e0e2461697782ef11675f668207961. On the Aurora network, AURORA is added as the ERC-20-equivalent token using 0x8bec47865ade3b172a928df8f990bc7f2a3b9f79. Aurora’s own token page publishes AURORA token information at aurora.dev/tokens/aurora, so the contract route should be matched before receiving.
Check the route before you copy your address into an exchange, bridge, or application. A 0x address alone does not tell you whether the transfer is using Ethereum or the Aurora network. The sender must use the same route you added in the wallet interface.
After the correct route is added, the AURORA balance can be viewed against the EVM address controlled by your Cryptnox card. The visible token entry belongs to the software view; the private key that controls the 0x address is generated inside the secure element and never leaves it.
The Cryptnox card does not arrive with an AURORA profile already selected. After your wallet is initialized, add AURORA once through the relevant EVM workflow. If your intended route is Ethereum, add the ERC-20 token contract. If your intended route is the Aurora network, add the Aurora network or the AURORA token on that network, depending on the interface you are using.
The free Cryptnox app is available for iOS and Android, connects to Web3 through WalletConnect, and works with MetaMask. In an AURORA workflow, the card protects the private key for the EVM address while the connected interface is used to add the token or network view. The Cryptnox hardware wallet tutorials help with product setup; keep the AURORA contract and route details separate from general initialization steps.
For AURORA, the protected item is the private key controlling the 0x-prefixed EVM address. The token may be displayed through Ethereum or through the Aurora network, but address control depends on the same key model. Cryptnox generates private keys inside the secure element, and those private keys never leave it.
The secure element uses an EAL6+-certified chip. For an AURORA holder, that matters at the approval point because the key material remains in the secure element instead of being exposed to the phone or connected wallet interface. Adding 0xaaaaaa20d9e0e2461697782ef11675f668207961 or 0x8bec47865ade3b172a928df8f990bc7f2a3b9f79 changes the token route shown in software; it does not move the private key out of the card.
Unlock approval uses the phone’s biometrics through the Cryptnox app. The card itself has no fingerprint sensor or face sensor. In an AURORA transaction flow, that separates the local phone unlock step from the card’s role in protecting the EVM-address private key.
The product is a contact and NFC smart card. You can tap it to a phone or insert it into a reader. For AURORA, that means the same 0x-prefixed EVM address can be used after the correct Ethereum or Aurora-network token route has been added.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set ships uninitialised. During setup, the seed is generated inside both secure elements, so the second card is the backup for the same wallet. For AURORA, that backup applies to the same EVM address used for the Ethereum ERC-20 route or the Aurora-network route.
The default backup model does not require writing down a recovery phrase. Instead, both cards are created as the paired AURORA-capable wallet during setup, with the private keys generated inside secure elements and retained there. That is especially relevant when the token itself is added only after initialization: the backup is for the EVM address, not for a single token display entry.
Importing an existing BIP39 recovery phrase is available as an advanced option, but it is not the default setup path. A buyer starting a fresh AURORA wallet can use the dual-card generation model instead of beginning from an existing phrase.
AURORA is an EVM wallet workflow because both supported routes use 0x-prefixed 20-byte addresses. Through the Cryptnox app, Web3 connection via WalletConnect and use with MetaMask allow the AURORA token or Aurora network to be added in the interface while the card continues to protect the private key for the address.
When AURORA is not visible immediately, the next step is to add the correct route rather than to create a native NEAR-format account for this setup. Add 0xaaaaaa20d9e0e2461697782ef11675f668207961 for Ethereum ERC-20 AURORA, or add 0x8bec47865ade3b172a928df8f990bc7f2a3b9f79 for AURORA on the Aurora network. Both routes use EVM addressing.
For buyers organizing several EVM holdings, the AURORA setup has useful overlap with chain-specific EVM pages such as the Polygon hardware wallet page and the Ronin hardware wallet page. Those pages address different networks, while AURORA here is defined by its Ethereum ERC-20 contract, Aurora-network contract, and 0x address format.
The Cryptnox crypto hardware wallet hub gives the broader card-wallet context, but AURORA has a narrower decision path than many assets: choose the Ethereum ERC-20 contract or the Aurora-network ERC-20-equivalent contract, add that route once, and receive to the EVM address controlled by the card.
AURORA should not be handled like a native NEAR-format asset in this setup, even though Aurora is an EVM-compatible network on NEAR. It also should not be treated like a chain with a non-EVM address format. That is why AURORA setup differs from pages such as the Tron hardware wallet page or the Bitcoin hardware wallet page, where the address model and asset route are different.
For AURORA specifically, the purchase decision comes down to four concrete points: support is through EVM token routes, the token is added once rather than pre-programmed, the receiving address is 0x-prefixed, and the private keys are generated inside the secure element. The cards are Swiss-engineered and made in Switzerland, with one card serving as the active wallet and the second card serving as the backup created during setup.
No. AURORA is added after setup through Add a Network or Add a Token. Use the Ethereum ERC-20 contract 0xaaaaaa20d9e0e2461697782ef11675f668207961 or the Aurora-network ERC-20-equivalent contract 0x8bec47865ade3b172a928df8f990bc7f2a3b9f79. The card controls the EVM address that can hold the token.
Use 0xaaaaaa20d9e0e2461697782ef11675f668207961 when receiving AURORA as an Ethereum ERC-20 token. Use 0x8bec47865ade3b172a928df8f990bc7f2a3b9f79 when receiving AURORA on the Aurora network. Confirm the route before sending because both use EVM-style 0x addresses but they are different token routes.
No. The AURORA route described for Cryptnox is EVM-based only: Ethereum ERC-20 AURORA or the ERC-20-equivalent token on the Aurora network. The address format is a 0x-prefixed 20-byte EVM address, not a native NEAR-format account.
The Dual-Card Set is initialized by generating the seed inside both secure elements, so the second card is the backup for the same wallet. For AURORA, that backup applies to the same EVM address used on the Ethereum route or the Aurora-network route after the correct token or network is added.
No. Unlock approval uses the phone’s biometrics through the Cryptnox app, and the card itself has no fingerprint sensor or face sensor. The card’s role is to protect the private key for the AURORA EVM address, with private keys generated inside the secure element and kept there.
Yes. The free Cryptnox app is available on iOS and Android, connects to Web3 via WalletConnect, and works with MetaMask. AURORA still needs to be added as the correct Ethereum ERC-20 token or Aurora-network token before it appears in the connected wallet interface.
Receive AURORA to the 0x-prefixed 20-byte EVM address controlled by your Cryptnox card, after confirming whether the sender is using Ethereum or the Aurora network. Do not use a native NEAR-format address for the AURORA holding route described here.
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.