Yes. Cryptnox can hold Reserve Rights (RSR) as an ERC-20 token on Ethereum by adding the RSR token contract, 0x320623b8e4ff03373931769a31fc52a4e78b5d70, once in the Cryptnox app or a connected Web3 wallet. RSR is not pre-programmed on the card. The card signs for your 0x-prefixed Ethereum address, while private keys are generated inside the secure element and never leave it.

Reserve Rights, ticker RSR, is holdable with the Cryptnox Crypto Hardware Wallet – Dual-Card Set as an ERC-20 token on Ethereum. The token contract to add is 0x320623b8e4ff03373931769a31fc52a4e78b5d70, the same RSR contract shown on Etherscan. The Reserve documentation also lists RSR among Reserve’s core components in its own protocol materials.
RSR is not a separate native-chain account in this setup. It is a token entry under an Ethereum account, so the receiving address is the same 0x-prefixed 20-byte EVM address format used by Ethereum accounts. When RSR is added correctly, the wallet view shows the token balance at that Ethereum address, and the Cryptnox card signs transactions from the private key controlling that address.
The practical buying point is that Cryptnox secures the Ethereum private key used to control the address where RSR is held. The RSR balance itself is recorded on Ethereum at that address, while transaction signing is performed with the card.
The Dual-Card Set does not arrive with Reserve Rights already enabled as a pre-set asset. Add RSR once by using Add a Token, or by using Add a Network only where your wallet interface first asks for the Ethereum view before the token entry is created. The token data that matters is the Ethereum ERC-20 contract address: 0x320623b8e4ff03373931769a31fc52a4e78b5d70.
For an RSR holder, the setup order is Ethereum first, RSR second. Create or open the Ethereum account controlled by the Cryptnox card, then add the Reserve Rights token entry under that account. The receiving address remains the Ethereum 0x address; there is no separate RSR-only address format.
If you are following Cryptnox operating steps while adding Reserve Rights, use the hardware wallet tutorials for the card workflow, then apply the RSR-specific token details above when the interface asks for the ERC-20 contract. The coin and blockchain support page is also useful when checking whether an asset path is a network account or a token entry; for RSR, the path is Ethereum ERC-20.
Before receiving Reserve Rights, check two details together: the selected chain must be Ethereum, and the token contract must be 0x320623b8e4ff03373931769a31fc52a4e78b5d70. Those two details define the RSR route described here. The receiving address shown to the sender is your normal Ethereum address, beginning with 0x.
An RSR token entry does not create a new type of account on the card. It displays a token balance tied to the Ethereum account controlled by the card-held private key. That distinction matters when copying an address: send RSR to the Ethereum 0x address controlled by your Cryptnox wallet, not to a different address format.
If your browsing path includes the Polygon hardware wallet page or the Tron hardware wallet page, keep the RSR setup separate from those buying paths. Reserve Rights in this setup is added by its Ethereum ERC-20 contract, and the address you use for receiving it is the Ethereum 0x address controlled by your Cryptnox card.
For Reserve Rights, the asset-specific security question is where the Ethereum private key is created and kept. With the Cryptnox Crypto Hardware Wallet – Dual-Card Set, private keys are generated inside the secure element and never leave it. The RSR balance is on Ethereum at the 0x address, and the card protects the private key that can sign from that address.
The card uses an EAL6+-certified chip. That certification applies to the chip platform, not to the finished card. For an ERC-20 token such as RSR, the chip is relevant because the same Ethereum private key controls the account used for the token balance and for signing RSR-related transactions.
Unlocking through the Cryptnox app can use the phone’s face or fingerprint unlock. The card itself has no fingerprint or face sensor. The phone provides the familiar unlock step in the app, while the card remains the signing device for the Ethereum key used with Reserve Rights.
This separation is the reason the form factor is useful for RSR holders: the phone or Web3 wallet can display the request, but the private key used to approve that request is generated inside the card’s secure element and stays there.
The Dual-Card Set is designed so the second card is the backup for the same wallet. The set ships uninitialised, and during setup the seed is generated inside both secure elements. For an RSR holder, that means the backup is a second card controlling the same Ethereum account, not a written phrase by default.
Reserve Rights is recorded on Ethereum at the 0x address controlled by the wallet. The cards do not store an RSR balance as a separate object; they hold the signing authority for the Ethereum address where the token is held. If one initialized card is unavailable, the second card can be used to sign from the same Ethereum account and access the RSR associated with it.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set is the purchase option for this two-card model. For Reserve Rights buyers, the key benefit is straightforward: both cards are initialized to control the Ethereum address where the RSR token entry is held.
RSR can be used through the free Cryptnox app on iOS and Android, and the app connects to Web3 through WalletConnect and works with MetaMask. In an RSR workflow, that means the connected wallet can show the Ethereum account, the Reserve Rights token entry, and the transaction request, while the Cryptnox card remains the device that signs from the Ethereum address.
For Reserve Rights, review the token contract whenever adding the asset or checking a token entry: 0x320623b8e4ff03373931769a31fc52a4e78b5d70. If a Web3 interface shows an RSR transfer or approval request, the request should relate to the Ethereum account whose 0x address is controlled by the Cryptnox card.
WalletConnect and MetaMask are connection paths for the wallet interface. They do not move the Ethereum private key out of the Cryptnox card. The private key used for RSR signing is generated inside the secure element and never leaves it.
Cryptnox is a contact and NFC smart card. You can tap it to a phone or insert it into a reader. For Reserve Rights, both modes serve the same purpose: the card signs Ethereum transactions from the 0x address that holds the RSR ERC-20 token.
The dual-interface form factor fits an RSR workflow because the token is added under an Ethereum account rather than installed as a separate card application. The card can be kept as the signing object, while the app or connected Web3 wallet displays the RSR balance, contract entry, transfer request, or approval request.
The product is Swiss-engineered. Its RSR-specific value is not that Reserve Rights is preloaded, because it is not; the value is that the Ethereum private key controlling the RSR address is generated inside the secure element, stays there, and is backed up by the second initialized card in the set.
The broader Cryptnox hardware wallet collection includes buying paths for several assets, but Reserve Rights should be evaluated through its Ethereum ERC-20 route. A buyer comparing RSR with a non-Ethereum asset such as the one covered on the Bitcoin hardware wallet page should focus on the operational difference that RSR uses an Ethereum 0x address and the ERC-20 contract above.
No. Reserve Rights is not pre-programmed on the card. Add RSR once as an ERC-20 token on Ethereum using contract 0x320623b8e4ff03373931769a31fc52a4e78b5d70. After that, RSR is shown under the Ethereum account controlled by your Cryptnox card.
Use Ethereum, and add Reserve Rights as an ERC-20 token. The RSR contract is 0x320623b8e4ff03373931769a31fc52a4e78b5d70. The receiving address is your Ethereum account address, which uses the 0x-prefixed 20-byte EVM address format.
Yes. The Dual-Card Set ships uninitialised, and the seed is generated inside both secure elements during setup. The second card is the backup for the same Ethereum account. Since RSR is held at that Ethereum address, either initialized card can sign from it.
No recovery phrase has to be written down by default. In the default Dual-Card Set setup, the seed is generated inside both secure elements, making the second card the backup. Importing an existing BIP39 phrase of 12 or 24 words is an advanced option.
Yes. The free Cryptnox app connects to Web3 through WalletConnect and works with MetaMask. You can add RSR as an Ethereum ERC-20 token in the wallet interface, then use the Cryptnox card to sign while the private key remains inside the secure element.
Reserve Rights uses the Ethereum address format in this setup because it is held as an ERC-20 token on Ethereum. Your receiving address is a 0x-prefixed 20-byte EVM address controlled by the private key generated inside the Cryptnox 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.