Yes. Cryptnox can hold DEGEN as an ERC-20 token on Base or as the native gas coin on the EVM-compatible Degen Chain after you add the token or network manually. DEGEN is not pre-programmed on the card. Use Add a Token for the Base ERC-20 route, or Add a Network for Degen Chain. Both routes use an 0x-prefixed 20-byte EVM address.
CRYPTNOX products are also available worldwide through our official Amazon stores.
DEGEN has two support routes with the Cryptnox Crypto Hardware Wallet – Dual-Card Set. One route is DEGEN as an ERC-20 token on Base. The other route is DEGEN as the native gas coin on the EVM-compatible Degen Chain. The card does not arrive with either DEGEN route pre-programmed, so the buyer adds the relevant token or network once before holding or signing with DEGEN.
The address format for both DEGEN routes is an 0x-prefixed 20-byte EVM address. That shared address style can make the two routes look similar, but the network context is different. DEGEN on Base is a token entry on Base. DEGEN on Degen Chain is the native coin used as gas on that EVM L3.
CoinGecko lists DEGEN on Base, which helps distinguish the Base ERC-20 token route from the native-coin route on Degen Chain. The setup decision is not the asset name alone; it is whether your DEGEN is on Base or on Degen Chain before the card signs.
Choose the Base route when the DEGEN you want to hold is the ERC-20 token on Base. In that setup, the buyer adds DEGEN once through Add a Token. After the token is added, DEGEN appears under the Base route tied to the 0x-prefixed EVM address format used for that account.
The Base route should be treated as token-based. DEGEN is not the gas coin of Base in this setup; it is an ERC-20 token on Base. That distinction matters when checking where a balance is expected, where a transaction is being sent, and which network is selected before the Cryptnox card signs.
The Cryptnox coin and blockchain support page is useful when reviewing broader asset coverage before deciding how DEGEN fits into your wallet setup. For comparison, the Polygon hardware wallet page covers a different EVM network asset, while this DEGEN route is specifically the ERC-20 token on Base.
Choose the Degen Chain route when the DEGEN you want to hold is the native gas coin on Degen Chain. In that setup, the buyer manually adds Degen Chain through Add a Network. Once the network has been added, DEGEN is used as the native gas coin for that EVM-compatible L3.
This is not the same action as adding the DEGEN token on Base. The Base route adds a token to a Base network context. The Degen Chain route adds a network where DEGEN is the native coin. Both routes use an 0x-prefixed 20-byte EVM address, but the signing context must match the DEGEN route you intend to use.
Alchemy describes Degen Chain access for EVM tooling, which supports the manual network route for native DEGEN. For a buyer, the practical takeaway is direct: add Degen Chain when the DEGEN movement belongs on that chain, not when the balance is the ERC-20 token on Base.
If you compare manually selected networks, the TRON hardware wallet page describes a different network-specific wallet path. DEGEN needs its own decision between Base token handling and Degen Chain native-coin handling.
For DEGEN on Base or Degen Chain, the private key for the 0x-prefixed EVM account is generated inside the secure element and never leaves it. The phone, the Cryptnox app, WalletConnect, and MetaMask can be part of the visible DEGEN workflow, but the card remains the signing component for the selected route.
The card uses an EAL6+-certified chip. That chip-level protection is part of the DEGEN signing path whether the transaction concerns the Base ERC-20 token or the native gas coin on Degen Chain. The product is a contact and NFC smart card, so a DEGEN holder can tap the card to a phone or insert it into a reader when signing through the configured route.
Unlock for a DEGEN signing flow uses the phone’s biometrics through the Cryptnox app. The card itself has no biometric sensor. That separation keeps the phone responsible for the unlock experience while the card keeps the DEGEN account keys inside the secure element.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set ships uninitialised, which matters before you add DEGEN on Base or Degen Chain. During setup, the seed is generated inside both secure elements. The second card is the backup because it receives the same seed inside its secure element during initialisation.
This backup model fits a DEGEN buyer who wants one EVM account setup available for the Base ERC-20 route or the Degen Chain native-coin route. The default setup does not require writing down a recovery phrase to create the backup card. Importing a BIP39 recovery phrase is an advanced option rather than the default setup path.
The cards are made in Switzerland. For a DEGEN buyer, the product decision is about using two smart cards for one EVM wallet setup: one card for signing and a second card that serves as the backup after initialisation.
When setting up DEGEN, the free Cryptnox app on iOS and Android is used for the wallet flow, including the choice to add the Base token or manually add Degen Chain. The app connects to Web3 through WalletConnect and works with MetaMask, so the DEGEN route selected in the connected flow should match the asset route you intend to use.
For DEGEN on Base, the connected wallet context should show the Base ERC-20 token route. For native DEGEN, the connected wallet context should show Degen Chain after that network has been added. The same 0x-prefixed address style does not remove the need to choose the correct network before approving a transaction.
The Cryptnox hardware wallet tutorials page is useful when preparing the app, checking card signing steps, or connecting through WalletConnect before handling DEGEN. Pair the tutorial flow with the route decision on this page: Base token through Add a Token or Degen Chain through Add a Network.
The Ronin hardware wallet page shows another network-specific buying path, but DEGEN requires a Base-versus-Degen-Chain choice before the signing flow is approved.
The Cryptnox hardware wallet collection helps buyers compare asset-specific pages, but DEGEN has a setup detail that should not be skipped: it can be held as an ERC-20 token on Base or as the native gas coin on Degen Chain. That makes the first setup question more precise than simply asking whether the asset name is visible.
DEGEN also differs from a non-EVM asset route. The Bitcoin hardware wallet page covers a different address and network model, while DEGEN uses an 0x-prefixed 20-byte EVM address on the routes described here. A buyer moving between those pages should expect the DEGEN setup to depend on Base or Degen Chain.
Start by identifying where your DEGEN is meant to exist. If the balance is DEGEN on Base, add the ERC-20 token on Base through Add a Token. If the balance is native DEGEN on Degen Chain, manually add Degen Chain through Add a Network. The card is not shipped with either DEGEN route pre-programmed.
The buying decision is practical: choose the Dual-Card Set if you want DEGEN signing through a contact and NFC smart card, a second card that serves as the backup after setup, and manual route control for Base or Degen Chain.
No. DEGEN is not pre-programmed on the card. Add it once according to the route you need: Add a Token for DEGEN as an ERC-20 token on Base, or Add a Network for Degen Chain when you want DEGEN as the native gas coin.
Choose Base when the DEGEN you want to hold is the ERC-20 token on Base. Choose Degen Chain when DEGEN is the native gas coin on that EVM-compatible L3. Both routes use an 0x-prefixed 20-byte EVM address, so the network context should be checked before signing.
Yes. DEGEN on Base and native DEGEN on Degen Chain both use an 0x-prefixed 20-byte EVM address format. The address style is the same, but the route is not: one is an ERC-20 token on Base, and the other is the native coin on Degen Chain.
For the EVM account used with DEGEN, private keys are generated inside the secure element and never leave it. The card uses an EAL6+-certified chip, and the card signs after the DEGEN route has been selected through the app or connected wallet flow.
The 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 EVM account used with DEGEN. The default setup does not require writing down a recovery phrase.
Yes. The Cryptnox app on iOS and Android connects to Web3 through WalletConnect and works with MetaMask. For DEGEN, make sure the connected flow matches your route: Base for the ERC-20 token, or Degen Chain for the native gas coin.
The Cryptnox card is a contact and NFC smart card. For DEGEN, you can tap the card to a phone or insert it into a reader after the Base token or Degen Chain route is configured. The card signs while the keys stay inside the 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.