Yes. The Cryptnox Crypto Hardware Wallet – Dual-Card Set can hold SDN by adding Shiden Network manually as an EVM network. Shiden is not pre-programmed on the card; you add it once through Add a Network or Add a Token. SDN is held as the native coin on Shiden Network, using chainId 336 and a 0x-prefixed 20-byte EVM address, not a Polkadot/Substrate SS58 account form.
CRYPTNOX products are also available worldwide through our official Amazon stores.
Shiden support on Cryptnox is a manual EVM-network setup for SDN, not a preloaded asset profile. You initialise the Cryptnox Crypto Hardware Wallet – Dual-Card Set, then add Shiden Network in the wallet interface you use with the card. Once Shiden is added, SDN is handled as the native coin of that network at a 0x-prefixed 20-byte EVM address.
This distinction matters because Shiden is an EVM-compatible Kusama parachain while the supported Cryptnox route uses the Shiden EVM network. It is not the Polkadot/Substrate SS58 account form, and the address you prepare for SDN should start with 0x.
If you are comparing SDN with other assets before choosing a card wallet, the Cryptnox coin and blockchain support page is the right place to review supported network routes. For Shiden, the buying point is specific: SDN is added manually as Shiden EVM, then controlled through the Cryptnox card setup.
Shiden is not enabled automatically when the cards arrive. The Dual-Card Set ships uninitialised, so there is no SDN account, Shiden network entry, or ready-made Shiden balance view before setup. After you initialise the cards, add Shiden once through Add a Network or Add a Token, depending on the software screen you are using.
The value to verify during that step is the chain identifier. Shiden Network uses chainId 336, and SDN is the native coin for that network. A Shiden receiving address in this setup is a 0x-prefixed EVM address. If a screen asks you for a Substrate-style account, that is not the Shiden support route used for this Cryptnox setup.
Shiden endpoint information appears in the Astar documentation for Shiden network endpoints. Those endpoint details belong to the network configuration step; the Cryptnox card protects the key for the 0x address you use after the network is added.
For SDN on Shiden EVM, the important secret is the private key behind your 0x-prefixed address. When the Cryptnox Dual-Card Set is initialised, private keys are generated inside the secure element and never leave it. The Shiden network entry tells the wallet interface which chain you are viewing; the card protects signing authority for the SDN address.
The secure element uses an EAL6+-certified chip. That rating applies to the chip platform, which is the part relevant to storing and using the private key for your Shiden address. The finished product is the Cryptnox smart-card wallet system, used with the Cryptnox app and the Shiden network entry you add manually.
Unlocking the SDN wallet flow is handled through the phone in the Cryptnox app. The card itself has no biometric sensor. Your phone performs the app unlock step, while the Shiden EVM private key remains inside the secure element on the card. That separation is useful for SDN holders because adding Shiden in software does not move the private key into the phone or into MetaMask.
The card is a contact and NFC smart card. For Shiden use, that means you can tap it to a phone when using the Cryptnox app, or insert it into a contact reader when that is the chosen setup. The form factor does not change the Shiden details: SDN remains the native coin on Shiden Network, and the address remains the 0x EVM address you added.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set is designed so the second card is the backup for the same wallet you use with Shiden. During initialisation, the seed is generated inside both secure elements. For an SDN buyer, that means the backup is another card from the same setup process, not a default written recovery phrase step.
This matters for Shiden because the network is added manually after the cards are prepared. Adding Shiden through Add a Network or Add a Token affects the software view of SDN; it does not create a separate backup method for Shiden. The underlying seed is already present inside both secure elements from setup, and the private key for the 0x address stays inside the secure element.
For everyday SDN custody, the practical habit is to use one card for normal signing and store the second card separately. Both cards relate to the same Shiden EVM wallet after setup, so the backup card is not a second SDN account and does not need a separate Shiden address.
The Cryptnox app is available on iOS and Android, and it is the app used when the card is required for the wallet flow. For SDN, you first prepare the Cryptnox cards, then add Shiden Network manually in the software interface. The Cryptnox app connects to Web3 through WalletConnect and works with MetaMask, so the Shiden EVM account can be used through that route after the network is configured.
MetaMask and other EVM interfaces can show similar 0x addresses across multiple networks. For SDN, the address format alone is not enough; the selected network must be Shiden Network and the chain identifier must be 336. If you are viewing the same 0x address on another EVM chain, you are not viewing SDN on Shiden.
If you want to understand the card and app flow before adding Shiden, the Cryptnox hardware wallet tutorials cover product setup and usage. After that product setup, the Shiden-specific part is the manual EVM network entry for SDN.
Shiden should not be treated as a generic EVM entry without checking the chain. SDN is the native coin of Shiden Network, and the Cryptnox support route uses Shiden EVM with chainId 336. That is different from assets where the network is already familiar, and it is also different from Polkadot/Substrate SS58 account handling.
The contrast is clearest when comparing Shiden with other networks. Polygon also uses an EVM address style, but it is not Shiden and it does not use SDN; the Polygon hardware wallet page is separate because the network identity is different. Ronin also has its own route, covered on the Ronin hardware wallet page.
Shiden is also not comparable to Bitcoin from a setup perspective. Bitcoin does not use a 0x EVM address, while SDN on this page does. The Bitcoin hardware wallet page belongs to a different account model, and the Tron hardware wallet page covers another separate network model. For SDN, stay with Shiden Network, chainId 336, and the 0x EVM address.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set is the product to choose if you want SDN held through a smart-card hardware wallet and you are comfortable adding Shiden manually. The product decision is not about Shiden arriving pre-programmed. It is about using a secure-element card setup for the private key behind your Shiden EVM address, with the second card created as the backup during initialisation.
For an SDN buyer, the main purchase checks are concrete. You want Shiden Network as the chain, SDN as the native coin, chainId 336, and a 0x-prefixed 20-byte EVM address. You also want to know that Shiden is added once in software and that the card keeps the Shiden private key inside the secure element.
If you are still deciding how Cryptnox fits across your portfolio, the Cryptnox hardware wallet collection gives the parent overview. For Shiden specifically, the relevant decision is whether you want SDN on Shiden EVM, added manually, with signing tied to the Cryptnox smart-card setup.
No. Shiden is not pre-programmed on the card. You add Shiden Network manually through Add a Network or Add a Token, depending on the wallet interface. For SDN, verify Shiden Network, chainId 336, and a 0x-prefixed 20-byte EVM address.
Use a 0x-prefixed 20-byte EVM address for SDN on Shiden Network. The support route here is Shiden EVM, where SDN is the native coin. Do not use a Polkadot/Substrate SS58 account form for this Cryptnox SDN setup.
Yes. The Cryptnox app works with MetaMask and connects to Web3 through WalletConnect. After the cards are initialised, add Shiden manually in the wallet interface, confirm chainId 336, and use the 0x EVM address for SDN on Shiden Network.
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.
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 wallet. Shiden still needs to be added manually in the interface, but both cards relate to the same underlying SDN address.
No. The card itself has no biometric sensor. Fingerprint or face unlock is handled by the phone through the Cryptnox app, while the private key for the Shiden EVM address is generated inside the secure element and never leaves it.
Not for this Cryptnox route. SDN is held as the native coin on the Shiden EVM network, using a 0x-prefixed 20-byte EVM address. Shiden is an EVM-compatible Kusama parachain, but the account form used here is the EVM address form.
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.