Cryptnox supports STORJ by adding it as an ERC-20 token on Ethereum to an 0x-prefixed EVM address. STORJ is not pre-programmed on the card at delivery; after the Dual-Card Set is initialised, add the token once through Add a Token. The STORJ-holding Ethereum account is controlled by private keys generated inside the secure elements, and the free Cryptnox app for iOS and Android connects to Web3 through WalletConnect and works with MetaMask.
Buy it from CRYPTNOX shop directly
Accepts:
Preferred shopping solution for US:
Also available on other Amazon shops:
DE, FR, IT, BE, SE, ES, PL, NL, CA, MX, AU
STORJ is held with Cryptnox through Ethereum, using the ERC-20 token standard. The receiving address is an 0x-prefixed 20-byte EVM address, so a buyer setting up STORJ should treat it as an Ethereum token rather than a separate native coin with its own address family. Storj documentation identifies STORJ as an ERC-20 token, which matches the route used when adding STORJ to a Cryptnox card-backed Ethereum account.
The important purchase detail is that STORJ is not waiting on the card as a pre-enabled asset. The Cryptnox Crypto Hardware Wallet – Dual-Card Set ships uninitialised, and the token is added after the Ethereum account has been created. That keeps the STORJ setup tied to the address generated during initialisation, not to a preconfigured token list on the card.
If you are comparing STORJ with other assets before deciding what to add, the Cryptnox coin and blockchain support page helps you review how Ethereum tokens and other networks are organised.
The STORJ flow begins only after the two-card wallet has been initialised. During that setup, the Ethereum account that can receive STORJ is created under the control of the card secure elements. After that account exists, add STORJ as an Ethereum ERC-20 token so the wallet interface can show the token against the 0x address.
For a STORJ buyer, this distinction matters because adding a token is not the same as creating a new blockchain account. The account is the Ethereum-style 0x address controlled by the Cryptnox cards; STORJ is the ERC-20 token associated with that address after the token has been added. If you later use MetaMask with the same card-backed account, the same STORJ token route applies because the address remains an Ethereum EVM address.
For product walkthroughs before receiving tokens, use the Cryptnox hardware wallet tutorials; they are the right starting point for card initialisation and app-led setup before adding STORJ.
A STORJ receiving address in this setup should begin with 0x because Cryptnox handles STORJ as an ERC-20 token on Ethereum. The address is not a Storj-specific address format. It is the same EVM address type used by Ethereum accounts, with STORJ added at the token level after the account is created.
Storj guidance on holding STORJ tokens points users toward holding the token through the Ethereum token model. With Cryptnox, the token balance is associated with the card-controlled Ethereum account, while the card protects the private key that controls that account.
This is where STORJ differs from coins that use their own native address patterns. The buyer does not need a separate STORJ-only account type on the card. The buyer needs an Ethereum account controlled by the card and a token entry for STORJ on that account.
Control of a STORJ balance depends on control of the Ethereum account that holds the ERC-20 token. In the Cryptnox setup, the private keys for that STORJ-holding Ethereum account are generated inside the secure element and never leave it. The phone, MetaMask, and connected Web3 sites can be part of the interface, but they do not receive the private key for the address that holds STORJ.
The chip used for the card platform is an EAL6+-certified chip. For a STORJ holder, the practical point is that the signing key for the 0x address is kept in the card’s secure-element environment while ERC-20 activity is approved through the card-backed account flow.
Unlocking uses the phone’s biometrics through the Cryptnox app. The card itself has no biometric sensor. That division is useful for STORJ use: the phone gives the buyer a familiar unlock step, while the card remains the device that protects the Ethereum private key and signs without handing that key to the phone.
The Dual-Card Set arrives uninitialised, so the STORJ-ready Ethereum account is created during the buyer’s own setup. The seed is generated inside both secure elements during that process, which makes the second card the backup for the same account. For STORJ, the result is straightforward: the backup card protects access to the same 0x address that can hold the ERC-20 token after it has been added.
The default flow does not require the buyer to write down a recovery phrase. The backup is the second smart card created during initialisation. Importing an existing 12/24-word BIP39 seed is an advanced route for users who deliberately choose that path, but it is not the default way the Dual-Card Set creates a new STORJ-holding account.
This backup model is especially relevant for an ERC-20 token because the STORJ balance remains on Ethereum at the 0x address. If the daily-use card is unavailable, the second card is already tied to the same generated secret from setup. The token does not need to be held at a second address just to have a backup card.
Buyers evaluating this backup approach can review the Cryptnox Crypto Hardware Wallet – Dual-Card Set, which is the product sold for this two-card setup.
The Cryptnox card is a contact and NFC smart card, so a STORJ holder can tap the card to a phone or insert it into a reader. That dual-interface format fits an Ethereum ERC-20 token workflow because the card-backed 0x account can be used through the free Cryptnox app, WalletConnect, MetaMask, or the contact interface.
The Cryptnox app is free on iOS and Android. For STORJ, the app is the phone-side tool used with the card while the ERC-20 token remains tied to the Ethereum address. When a Web3 connection is needed for that STORJ-holding address, the app can connect through WalletConnect and the account works with MetaMask.
The card format is relevant for buyers who want a smart-card signing device for Ethereum token custody. STORJ is still handled as an Ethereum token; the difference is the way the signing device is presented and used. You can tap for phone-based use or insert the card into a reader for the contact interface, while the private key for the STORJ-holding address remains inside the secure element.
If you are still choosing between card-based storage options for multiple assets, start from the broader Cryptnox hardware wallet collection and then return to STORJ once you are ready to add the Ethereum ERC-20 token.
STORJ should be planned as an Ethereum ERC-20 token, not as a native network with a separate Cryptnox setup path. That is why the buyer’s checklist is specific: initialise the Dual-Card Set, use the Ethereum 0x address, add STORJ once as a token, and keep the second card as the backup for that same account.
Other assets can require different assumptions, so it is worth keeping each network route separate before moving funds. Cryptnox has a separate page for TRON hardware wallet support because TRON is not the same setup route as STORJ on Ethereum. The Polygon hardware wallet page is also separate because Polygon network handling is not identical to adding an ERC-20 token on Ethereum.
The same distinction applies when comparing STORJ with non-Ethereum assets. A buyer considering Bitcoin hardware wallet storage is not choosing the same address model as STORJ, and Ronin hardware wallet support involves different network assumptions from STORJ as an Ethereum ERC-20 token.
For a STORJ buyer who wants card-based Ethereum token custody, the relevant product details are the two-card backup, the secure-element key generation, the contact and NFC smart card format, and Web3 access through WalletConnect and MetaMask. The product is Swiss-engineered, and the cards are made in Switzerland.
No. STORJ is not pre-programmed on the card. The Dual-Card Set ships uninitialised, and the Ethereum account is created during setup. After that, add STORJ once as an ERC-20 token and use the 0x-prefixed EVM address controlled by the card-backed account.
Use Ethereum. STORJ is held as an ERC-20 token on Ethereum, so the receiving address is an 0x-prefixed 20-byte EVM address. In the wallet interface, STORJ should be added as a token connected to that Ethereum-style address.
Yes. During Dual-Card Set setup, the seed is generated inside both secure elements. The second card is therefore the backup for the same Ethereum account that can hold STORJ after the token has been added. The backup is not a separate STORJ address.
No. In the standard Dual-Card Set setup, the backup is the second card created during initialisation. Importing an existing 12/24-word BIP39 seed is available as an advanced option for users who choose that route, but it is not the default setup path.
The Ethereum private key that controls the STORJ address is generated inside the secure element and never leaves it. The card platform uses an EAL6+-certified chip, and signing is handled without sending the private key to the phone, MetaMask, or a connected Web3 site.
Yes. The Cryptnox app connects to Web3 through WalletConnect and works with MetaMask. For STORJ, add the token as an ERC-20 asset on Ethereum so MetaMask can show the balance for the 0x address controlled by the Cryptnox card.
No. Unlocking uses the phone’s biometrics through the Cryptnox app. The card has no biometric sensor. For STORJ, the card’s job is to protect the Ethereum private key for the 0x address and sign without releasing that key.
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.
