Yes. Cryptnox supports iExec RLC by holding RLC as an ERC-20 token on Ethereum after you add the token or network once in the Cryptnox app. RLC is not pre-programmed on the card. Use the Ethereum contract address 0x607F4C5BB672230e8672085532f7e901544a7375 and a 0x-prefixed 20-byte EVM address. With the Cryptnox Crypto Hardware Wallet – Dual-Card Set, private keys are generated inside the secure element and never leave it.
CRYPTNOX products are also available worldwide through our official Amazon stores.
iExec RLC is held on Cryptnox as the RLC ERC-20 token on Ethereum. The RLC route is not pre-programmed on the card, so the buyer setup step is to add RLC once in the Cryptnox app through Add a Token or Add a Network.
For this RLC route, the chain is Ethereum, the standard is ERC-20 on Ethereum, and the receiving address is a 0x-prefixed 20-byte EVM address. The token contract is 0x607F4C5BB672230e8672085532f7e901544a7375. Etherscan lists that token at the RLC ERC-20 contract address on Ethereum, and the token repository is available at the iExecBlockchainComputing RLC token repository.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set protects the private key for the Ethereum account that controls the RLC-holding address. The RLC token balance is associated with that Ethereum address, while the private key is generated inside the secure element and never leaves it.
RLC should be added as an Ethereum ERC-20 token, not treated as an asset already configured on the card. The Dual-Card Set ships uninitialised, and the RLC token is not enabled on arrival. After the wallet is set up, add RLC once in the Cryptnox app through Add a Token or Add a Network.
The important RLC value to check is the Ethereum contract address: 0x607F4C5BB672230e8672085532f7e901544a7375. The receiving address for RLC is the Ethereum-style 0x address controlled by your Cryptnox wallet. A ticker alone is not enough for a transfer decision because this RLC setup depends on the Ethereum chain and the ERC-20 contract.
If you want the card and app workflow before adding RLC, use the Cryptnox hardware wallet tutorials before entering the token details. If you are checking other coins or networks before transferring, the Cryptnox coin and blockchain support page helps you compare supported routes.
RLC is controlled through an Ethereum account. On the Cryptnox Crypto Hardware Wallet – Dual-Card Set, the private key for that Ethereum account is generated inside the secure element and never leaves it. For RLC, this means the key that controls the 0x-prefixed Ethereum address holding the ERC-20 token stays inside the card’s secure element.
The card uses an EAL6+-certified chip. That certification applies to the chip platform. For an RLC holder, the practical point is that the Ethereum account key is created and kept inside the secure element rather than exposed as a file, typed secret, or default recovery phrase.
When the Cryptnox app requests an unlock step during RLC wallet use, the face or fingerprint check happens on the phone. The card itself has no biometric sensor. The card remains a contact and NFC smart card while the app uses the phone’s unlock check during the wallet flow.
The Dual-Card Set is shipped uninitialised. During setup, the seed is generated inside both secure elements, so the second card becomes the backup for the same wallet. For RLC, that backup card protects access to the same Ethereum account address used to hold the RLC ERC-20 token.
There is no recovery phrase to write down by default. The default backup is the second card. Importing an existing BIP39 seed phrase with 12 or 24 words is an advanced option, not the default setup route for a new Dual-Card Set.
RLC is held at an Ethereum address. If the private key for that address is unavailable, the RLC at that address is unavailable. The Dual-Card Set reduces reliance on a written secret by creating the seed inside both secure elements during initialisation, making the second card the backup for the RLC-holding Ethereum address.
For day-to-day RLC use, one card can be used for the Ethereum address while the second card remains available as the backup created during setup. The buyer decision is whether this dual-card backup model is the right fit for the Ethereum account that will hold RLC.
The Cryptnox product used for RLC is a contact and NFC smart card. You can tap the card to a phone for app-based RLC management, or insert the card into a reader for contact-card use. In both cases, the RLC token remains tied to the Ethereum address whose private key is protected by the card’s secure element.
The free Cryptnox app runs on iOS and Android, connects to Web3 through WalletConnect, and works with MetaMask. For RLC, this gives the Ethereum account a Web3 connection route after the RLC token has been added as an ERC-20 token on Ethereum with the correct contract address.
Because RLC uses a 0x-prefixed EVM address, it can look similar at the address level to assets on other EVM networks. The token route still matters: RLC here is the ERC-20 token on Ethereum at 0x607F4C5BB672230e8672085532f7e901544a7375. For comparison with another EVM-address environment, the Polygon hardware wallet page explains a different network path, while this RLC setup uses Ethereum.
The product for holding RLC with Cryptnox is the Cryptnox Crypto Hardware Wallet – Dual-Card Set. It is a Swiss-engineered contact and NFC smart card product, and the cards are made in Switzerland. For an RLC buyer, the relevant setup path is to initialise the two-card wallet first, then add RLC as an ERC-20 token on Ethereum.
The broader Cryptnox hardware wallet hub is useful when choosing the physical wallet, while this RLC page defines the asset route: Ethereum chain, ERC-20 standard, RLC contract address, and 0x-prefixed EVM address format.
If your portfolio includes assets with different address formats, compare the RLC route with the Bitcoin hardware wallet page. Bitcoin does not use the RLC ERC-20 route described here, so the RLC contract address and Ethereum 0x address format are specific to this token setup.
RLC setup on Cryptnox is defined by three asset-specific facts: Ethereum, ERC-20, and the contract address 0x607F4C5BB672230e8672085532f7e901544a7375. A ticker alone is not enough information for adding the token because the Cryptnox app needs the token route that matches the chain and contract.
RLC differs from assets that are managed through another native chain route. The TRON hardware wallet page is a useful contrast because the RLC instructions here are specifically for an Ethereum ERC-20 token. The Ronin hardware wallet page is another comparison point for buyers checking EVM-style address environments while keeping the RLC route on Ethereum clear.
Once those RLC-specific checks are complete, the wallet role is clear: the Cryptnox card protects the Ethereum account private key inside the secure element, and the second card serves as the backup created during setup.
No. RLC is not pre-programmed on the card. Add it once through Add a Token or Add a Network in the Cryptnox app. Use Ethereum as the chain, ERC-20 on Ethereum as the token route, and 0x607F4C5BB672230e8672085532f7e901544a7375 as the RLC contract address.
Use the Ethereum ERC-20 contract address 0x607F4C5BB672230e8672085532f7e901544a7375. RLC held through this route uses an Ethereum-style account address, so the receiving address is a 0x-prefixed 20-byte EVM address controlled by the Cryptnox wallet.
No separate RLC-specific address format is used for this route. RLC is an ERC-20 token on Ethereum, so it is held at a 0x-prefixed 20-byte EVM address. The card protects the private key for that Ethereum address.
The Dual-Card Set ships uninitialised. During setup, the seed is generated inside both secure elements, so the second card becomes the backup for the same wallet. For RLC, that means the backup card protects access to the Ethereum address that holds the ERC-20 token.
No. The card itself has no biometric sensor. When the Cryptnox app needs an unlock step, the face or fingerprint check happens on the phone. The card remains a contact and NFC smart card protecting the Ethereum account key used for RLC.
The Cryptnox app connects to Web3 through WalletConnect and works with MetaMask. For RLC, first add the token as an ERC-20 on Ethereum with the correct contract address, then use the card-protected Ethereum account through the supported connection route.
Use the Cryptnox Crypto Hardware Wallet – Dual-Card Set. It is a contact and NFC smart card set with two uninitialised cards. Private keys are generated inside the secure element and never leave it, and the second card becomes the backup during setup.
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.
