Yes. Cryptnox supports sDAI as an Ethereum ERC-20 token after you add the token once in the Cryptnox app. sDAI is not pre-programmed on the card, so add contract 0x83F20F44975D03b1b09e64809B757c47f942BEeA before receiving it. The Cryptnox Crypto Hardware Wallet – Dual-Card Set protects the private keys inside secure elements, with the second card acting as the backup for the same Ethereum address.
CRYPTNOX products are also available worldwide through our official Amazon stores.
sDAI SavingsDai is held on Cryptnox through Ethereum token support. It is not a native coin account on the card and it is not pre-programmed before setup. To use it, add sDAI once as an ERC-20 token on Ethereum through the Cryptnox app, using the contract address 0x83F20F44975D03b1b09e64809B757c47f942BEeA.
The receiving address for sDAI is a standard Ethereum address: a 0x-prefixed 20-byte EVM address. The token balance belongs to that Ethereum address, while the Cryptnox card protects the private key that controls the address. The sDAI contract can be checked on the Ethereum token contract view at Routescan.
When checking whether sDAI belongs in your Cryptnox setup, use the Cryptnox coin and blockchain support page to verify the Ethereum token route before sending an ERC-20 token to a card-controlled address.
The card does not arrive with sDAI already visible as an asset. The practical setup is to initialise the Dual-Card Set, open the free Cryptnox app on iOS or Android, and add sDAI through the app using either the token route or the network route required by the interface. For sDAI, the important entry is the Ethereum ERC-20 contract address.
Do not treat sDAI as a separate blockchain account. The address you give to a sender is the Ethereum address controlled by your Cryptnox setup. It begins with 0x and follows the 20-byte EVM address format. Sending sDAI to an address from a different route would not match the support route described here.
Before you enter the sDAI contract for the first time, the Cryptnox hardware wallet tutorials can help you follow the card-and-app workflow instead of guessing during token setup.
Holding sDAI means controlling the private key for the Ethereum address where the ERC-20 token balance is recorded. With the Cryptnox Dual-Card Set, private keys are generated inside the secure element and never leave it. The phone shows the app flow, but the private key for the 0x-prefixed sDAI address stays inside the card.
The Cryptnox card uses an EAL6+-certified chip. That certification belongs to the chip platform. For an sDAI holder, the practical result is that key generation and signing take place in the secure element rather than in the phone app.
When an sDAI transaction needs approval, the card signs for the Ethereum address that holds the token. The Cryptnox app provides the token view and transaction context, and the card performs the signing action. The private key is not exported to the phone.
The app can use the phone’s face or fingerprint check to unlock the app experience. The card itself has no fingerprint or face sensor. That distinction matters for sDAI storage because the phone is the interface, while the smart card is the signing device for the Ethereum address.
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 first card. For sDAI, that means both cards are tied to the same Ethereum address that can hold the ERC-20 token.
This backup model avoids making a written recovery phrase the default setup step. If the first card cannot be used, the second card is the backup for the same card-controlled Ethereum address. Importing a BIP39 recovery phrase is available as an advanced option, but the normal Dual-Card Set flow generates the seed inside both secure elements.
If your purchase decision depends on having that second smart card as the backup for an Ethereum address holding sDAI, the Dual-Card Set product page is the purchase page for this Cryptnox hardware wallet.
The free Cryptnox app on iOS and Android is where you add sDAI and handle the card interaction. Because sDAI is an Ethereum ERC-20 token, the app needs the token contract address before sDAI is part of your working asset view. The card remains responsible for signing with the private key held in the secure element.
Cryptnox connects to Web3 through WalletConnect and works with MetaMask. For sDAI, that means the Ethereum address controlled by the card can be used in Web3 flows that rely on WalletConnect or MetaMask, while sDAI remains the ERC-20 token at 0x83F20F44975D03b1b09e64809B757c47f942BEeA.
If MetaMask or another connected interface asks you to add the token, use Ethereum as the network and the sDAI ERC-20 contract address. The card does not ship with sDAI already enabled, so the token still has to be added where the interface requires it.
The project repository for sDAI on GitHub is useful when you want to check the asset name and project context before adding the Ethereum token to your Cryptnox-controlled address.
The Cryptnox hardware wallet is a contact and NFC smart card. For sDAI, you can tap the card to a phone when using the mobile app, or insert the card into a reader when using the contact interface. The support route does not change: sDAI remains an ERC-20 token on Ethereum at a 0x-prefixed address.
This dual-interface form factor matters because sDAI is not stored as a separate card applet or a preloaded coin. The card protects the private key for the Ethereum address, and the app or connected wallet interface presents the token action that the card signs.
If you are choosing hardware specifically for an Ethereum ERC-20 token such as sDAI, the Cryptnox crypto hardware wallet collection gives the broader product context, while this sDAI page gives the contract and Ethereum route needed before receiving the token.
sDAI belongs on this page because its supported route is Ethereum ERC-20 token support. The contract address, the 0x-prefixed address format, and the requirement to add the token once are the details that matter before receiving it. A native-asset page is not a substitute for the sDAI token setup route.
If you are researching TRON, use the hardware wallet for Tron page for that asset instead of copying anything from the sDAI Ethereum contract flow. If you are researching Polygon, use the hardware wallet for Polygon page rather than treating the sDAI Ethereum contract as a Polygon instruction.
The same separation applies to the hardware wallet for Ronin page and the hardware wallet for Bitcoin page. Those pages are for their own assets. For sDAI, use Ethereum, add the ERC-20 contract once, and receive to the 0x-prefixed Ethereum address controlled by the Cryptnox card setup.
Before sending sDAI to a Cryptnox-controlled address, confirm that the address is an Ethereum address beginning with 0x and that the token you added is sDAI at 0x83F20F44975D03b1b09e64809B757c47f942BEeA. The card is not shipped with the token already enabled, so the add-token step should happen before funds are sent.
After setup, the sDAI balance is controlled by the Ethereum address whose private key was generated inside the Cryptnox secure element. When approval is needed, the card signs for that address and the private keys never leave the secure element.
No. sDAI is not pre-programmed on the card. Add it once as an Ethereum ERC-20 token in the Cryptnox app, using contract address 0x83F20F44975D03b1b09e64809B757c47f942BEeA. After that, use the 0x-prefixed Ethereum address controlled by your card setup.
Use Ethereum. The supported sDAI route is the ERC-20 token on Ethereum, not a separate native blockchain account. The receiving address should be a 0x-prefixed 20-byte EVM address controlled by the private key generated inside the Cryptnox secure element.
Add sDAI with the Ethereum contract address 0x83F20F44975D03b1b09e64809B757c47f942BEeA. This is the token detail to use when the Cryptnox app or a connected wallet interface asks you to add the ERC-20 token.
Private keys are generated inside the Cryptnox secure element and never leave it. The card uses an EAL6+-certified chip, with that certification applying to the chip platform. The app shows the sDAI flow, while the smart card signs for the Ethereum address.
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 Ethereum address that can hold sDAI. The default setup does not require writing down a recovery phrase.
Yes. The free Cryptnox app connects to Web3 through WalletConnect and works with MetaMask. For sDAI, keep the route specific: add the Ethereum ERC-20 token contract, then use the Cryptnox card as the signing device for the Ethereum address.
No. The card itself has no fingerprint or face sensor. The Cryptnox app can use the phone’s face or fingerprint check to unlock the app experience, while the card remains the secure signing device for the Ethereum address holding sDAI.
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.