Yes. The Cryptnox Crypto Hardware Wallet – Dual-Card Set can hold Ethena USDe as an ERC-20 token on Ethereum after you add it once through Add a Network or Add a Token. USDe is not pre-programmed on the card. Use Ethereum contract 0x4c9EDD5852cd905f086C759E8383e09bff1E68B3, then receive USDe at the 0x-prefixed Ethereum address controlled by your Cryptnox card.
CRYPTNOX products are also available worldwide through our official Amazon stores.
Ethena USDe is used with Cryptnox through its Ethereum ERC-20 token contract, not through a USDe-specific blockchain address. After the card is set up, add USDe once with Add a Network or Add a Token, using contract 0x4c9EDD5852cd905f086C759E8383e09bff1E68B3 for the Ethereum token.
USDe is not pre-programmed on the card, so adding the token is the step that makes the Ethereum ERC-20 balance visible for use. The receiving address is still your Ethereum address; the token contract tells the wallet which asset on that address you want to view and transact with.
For a wider view of networks and assets that can be used with Cryptnox, the Cryptnox coin and blockchain support page is the right place to compare USDe on Ethereum with other supported routes.
A USDe transfer on this page means an ERC-20 transfer on Ethereum. The address you give to a sender should be the 0x-prefixed Ethereum address controlled by your Cryptnox card, and the token should match the USDe Ethereum contract address. Ethena lists the USDe Ethereum address in its key-address information.
This is different from a native network coin page, where the asset may have its own network model. For example, the Cryptnox hardware wallet for Bitcoin covers a non-ERC-20 asset, while this USDe page is specifically about an Ethereum token contract.
For the Ethereum account that receives Ethena USDe, the private keys are generated inside the Cryptnox secure element and never leave it. That matters for USDe because ERC-20 control follows control of the Ethereum account: the card is protecting the key for the 0x address that can hold and send the token.
When you prepare a USDe transfer, the transaction concerns the USDe ERC-20 contract on Ethereum, but the signing authority is still the Ethereum private key for your address. Cryptnox keeps that key inside the secure element while the phone or connected wallet prepares the transaction details.
The card uses an EAL6+-certified chip, with the certification applying to the chip/platform. For a USDe holder, the practical point is that the Ethereum private key used for the ERC-20 token is created and retained inside the secure element rather than being exposed to the phone.
The Dual-Card Set ships uninitialised, and setup creates the seed inside both secure elements. For a USDe holder, that means the second card is the backup for the same Ethereum account that receives the ERC-20 token at the 0x address.
There is no recovery phrase to write down by default in this setup. Importing a 12 or 24-word BIP39 seed is available as an advanced option, but the normal Dual-Card Set flow generates the seed inside both cards instead of starting from a written phrase.
USDe is not stored as a separate account outside Ethereum. It is an ERC-20 balance associated with the Ethereum address controlled by the generated seed. Because both cards are set up with that same generated seed, the backup card is tied to the same USDe-holding Ethereum address.
If you are comparing this backup approach with other EVM asset pages, the Cryptnox hardware wallet for Polygon shows a network-specific EVM context, while USDe here remains the Ethereum ERC-20 route.
USDe does not appear on the card as a pre-programmed asset. After initialising the Dual-Card Set with the free Cryptnox app on iOS or Android, add Ethena USDe as an Ethereum ERC-20 token by entering the token contract once.
Adding USDe does not create a new USDe-only address. It tells the wallet to recognise and display the ERC-20 token at your Ethereum address. If a sending interface asks for both a network and a token, choose Ethereum and the USDe contract above.
For walkthroughs that cover the card and app setup process, use the Cryptnox hardware wallet tutorials before adding the USDe token details.
For an Ethena USDe transaction, the phone or reader is used to prepare the Ethereum ERC-20 action, and the card is used to sign for the Ethereum address that holds the token. The card is a contact and NFC smart card, so you can tap it to a phone or insert it into a reader depending on your setup.
Unlock approval uses the phone’s biometrics through the Cryptnox app; the card itself has no biometric sensor. This keeps the USDe signing flow tied to the Cryptnox app and the card, while the private key for the Ethereum address remains inside the secure element.
The free Cryptnox app is available on iOS and Android. For Web3 use, Cryptnox connects through WalletConnect and works with MetaMask, so USDe can be used in Ethereum flows that require a wallet connection.
Ethena USDe is a token contract on Ethereum. That makes its Cryptnox setup different from assets that are added as native coins on their own networks. With USDe, the address format stays Ethereum-style, and the contract address is what identifies the token.
This distinction is useful when you manage more than one asset type. A Tron-focused setup is not the same as adding USDe on Ethereum, so the Cryptnox hardware wallet for Tron is a separate chain example rather than the route for this ERC-20 token.
If you are comparing several Cryptnox card-based options before buying, the crypto hardware wallet collection helps place this USDe-on-Ethereum setup alongside other wallet pages.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set is the purchase option for holding Ethena USDe through an Ethereum ERC-20 setup. It is a Swiss-engineered contact and NFC smart-card wallet sold as two cards, with the second card serving as the backup after the seed is generated inside both secure elements.
For a USDe buyer, the main fit is the combination of Ethereum token support, 0x-address receiving, secure-element key generation, and a backup card tied to the same generated seed. USDe still has to be added once because it is not pre-programmed on the card.
You can order the Cryptnox Crypto Hardware Wallet – Dual-Card Set from the Cryptnox shop and add USDe after initialising the cards.
No. Ethena USDe is not pre-programmed on the card. After setup, add it once through Add a Network or Add a Token as an ERC-20 token on Ethereum. Use contract 0x4c9EDD5852cd905f086C759E8383e09bff1E68B3 and receive to your Cryptnox-controlled Ethereum 0x address.
For Ethena USDe on Ethereum, use contract address 0x4c9EDD5852cd905f086C759E8383e09bff1E68B3. The token standard is ERC-20 on Ethereum. The receiving address is not a separate USDe format; it is a 0x-prefixed 20-byte EVM address.
No. USDe uses the Ethereum address controlled by your Cryptnox card. Adding the token tells the wallet to recognise the USDe ERC-20 contract at that address. It does not create a separate USDe address format or a separate USDe network account.
During Dual-Card Set setup, the seed is generated inside both secure elements. Because USDe is an ERC-20 balance tied to the Ethereum address controlled by that seed, the second card is the backup for the same USDe-holding Ethereum account.
No. In the default Dual-Card Set setup, the seed is generated inside both secure elements and the second card is the backup. Importing a 12 or 24-word BIP39 seed is available as an advanced option, but it is not the default setup route.
Yes. The free Cryptnox app is available on iOS and Android for setup and wallet management. For Web3 use, Cryptnox connects through WalletConnect and works with MetaMask, allowing USDe to be used through Ethereum wallet-connection flows.
The card is a contact and NFC smart card. For a USDe transaction, tap it to a phone or insert it into a reader while the app or connected wallet prepares the Ethereum ERC-20 action. The card signs while the Ethereum private key remains 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.