Yes. Cryptnox supports rETH when you add ERC-20 rETH on Ethereum, or an EVM-chain rETH representation, through the app after setup. rETH is not pre-programmed on the card. For Ethereum rETH, use contract 0xae78736cd615f374d3085123a210448e74fc6393 and receive to an 0x-prefixed 20-byte EVM address controlled by your Cryptnox card-backed wallet. The private key for that address is generated inside the secure element and never leaves it.
CRYPTNOX products are also available worldwide through our official Amazon stores.
Rocket Pool ETH, shown as rETH, is handled on Cryptnox as an asset you add after the Dual-Card Set is initialised. It does not arrive as a pre-programmed token on the cards. The normal route is Ethereum ERC-20 rETH, using contract 0xae78736cd615f374d3085123a210448e74fc6393. That contract is listed on Etherscan for Ethereum rETH, and the rETH token contract is also visible in Rocket Pool’s RocketTokenRETH.sol contract file.
For a buyer, the important distinction is that rETH support depends on adding the correct token or network, not on finding a preloaded rETH account on the card. If you hold Ethereum rETH, add the ERC-20 token entry for the Ethereum contract. If you hold an EVM-chain rETH representation, add that network or that token representation instead.
The broader Cryptnox coin and blockchain support page is useful when rETH is only one asset in the wallet and you want to review support across other chains and token standards.
Ethereum rETH uses the same account shape as other EVM assets: a receiving address beginning with 0x and representing a 20-byte account address. The token itself is identified by its ERC-20 contract, so the address and the contract work together. The address tells Ethereum which account receives the token; the contract identifies that the asset is rETH.
When you prepare Cryptnox for Ethereum rETH, the token entry should match 0xae78736cd615f374d3085123a210448e74fc6393. A different EVM network may also show 0x-style addresses, so the address format alone is not enough to identify the route. For Ethereum ERC-20 rETH, the network is Ethereum and the standard is ERC-20. For an EVM-chain rETH representation, the network and token entry must match that representation.
This is why rETH setup should be treated as a network-and-contract task. The Cryptnox card protects the account key, while the app entry tells the interface which rETH token or representation to display and use.
Holding rETH means controlling the Ethereum-style account that can sign transactions for that token. With the Cryptnox Dual-Card Set, the private key for that 0x account is generated inside the secure element and never leaves it. The EAL6+-certified chip is the evaluated chip platform inside the card, so the security statement applies to the chip rather than turning the finished card into a separately certified wallet.
The rETH transaction flow separates the interface from the signing key. The app or connected Web3 flow can prepare an Ethereum or EVM transaction involving rETH, but the card is the signing device for the account. The card is a contact and NFC smart card, so a user can tap it to a phone or insert it into a reader when the rETH transaction requires a card signature.
For rETH activity in the Cryptnox app, the phone provides the unlock step with its own fingerprint or face unlock. The card itself has no fingerprint or face sensor. After the phone-side unlock, the card still remains the place where the rETH account’s private key is generated and retained.
This matters for ERC-20 rETH because the asset is moved by signing with the account key, not by carrying rETH inside the card. The token stays on Ethereum, or on the relevant EVM chain for a representation, while the card protects the key that controls the 0x address.
The Dual-Card Set ships uninitialised, so rETH is added only after the wallet is prepared. During initialisation, the seed is generated inside both secure elements. The second card is therefore the backup for the same wallet that controls the rETH address, rather than a separate token account or a later copy of a written recovery phrase.
For Ethereum rETH, that means the same card-backed wallet can control the 0x-prefixed address that receives the ERC-20 token. If the primary card is not available, the paired backup card is designed to serve as the backup access route for that same wallet after setup. The backup card is not a second rETH balance; it is the second physical card tied to the same wallet seed generated inside the two secure elements.
If rETH is already associated with an existing phrase outside Cryptnox, importing a BIP39 recovery phrase is a deliberate advanced choice. If you use the default setup, the rETH address is created under the Dual-Card Set’s internal generation model, and the second card is the backup from the start.
The free Cryptnox app for iOS and Android is where the rETH token or EVM route is added after the cards are initialised. Use Add a Token when Ethereum is already the network you are using and the missing item is the ERC-20 rETH token entry. Use Add a Network when the rETH representation you intend to use depends on an EVM network that must be added first.
The Cryptnox hardware wallet tutorials are the practical starting point for the app and setup flow before adding rETH. Once the wallet is ready, the rETH-specific task is to match the route: Ethereum plus contract 0xae78736cd615f374d3085123a210448e74fc6393, or the exact EVM-chain representation you intend to use.
The Cryptnox app connects to Web3 through WalletConnect and works with MetaMask. For rETH, that lets the card-backed EVM account be used in flows that request an Ethereum or EVM signature. The connected interface prepares the request, and the card signs for the 0x address whose private key was generated inside the secure element.
Because rETH can be viewed as Ethereum ERC-20 rETH or as an EVM-chain representation, the selected network is part of the transaction context. A familiar 0x address does not remove the need to check whether the token entry is the Ethereum contract or a representation on another EVM chain.
The product used for this setup is the Cryptnox Crypto Hardware Wallet – Dual-Card Set. For rETH buyers, the fit is clearest when you want an Ethereum-style 0x account controlled by a smart card, with a second paired smart card as the default backup. The cards are made in Switzerland, and the product is Swiss-engineered.
rETH should be added because you intend to hold ERC-20 rETH on Ethereum or an EVM-chain rETH representation. It should not be treated as a token that appears automatically when the package arrives. The sequence is: initialise the two cards, confirm the wallet account, add the Ethereum rETH contract or the chosen EVM representation, then use the app and card together for rETH signing.
If you are comparing rETH storage with the wider Cryptnox product range, the Cryptnox hardware wallet collection gives the parent view before you move into asset-specific setup pages.
rETH has an EVM account format, but not every asset you may hold uses the same assumptions. A buyer who stores rETH as ERC-20 on Ethereum may also want to compare how other networks handle addresses, token entries, and network selection before adding them to the same wallet workflow.
For an EVM comparison, the Polygon hardware wallet page is relevant because it keeps the discussion close to EVM-style address handling while shifting the network context. The Ronin hardware wallet page is another useful comparison when you want to think carefully about network choice around an 0x-style account.
For contrast outside the rETH route, the Bitcoin hardware wallet page helps separate ERC-20 token storage from a non-EVM asset model, while the Tron hardware wallet page gives another asset-specific path to review. Those comparisons matter because rETH setup is contract-and-network specific: Ethereum ERC-20 rETH uses the Ethereum contract, while EVM-chain rETH representations must be added according to their own route.
No. rETH is not pre-programmed on the card. The Dual-Card Set ships uninitialised, and you add rETH after the wallet is set up. For Ethereum rETH, add the ERC-20 token using contract 0xae78736cd615f374d3085123a210448e74fc6393. For an EVM-chain rETH representation, add the relevant network or token.
Cryptnox supports rETH as ERC-20 rETH on Ethereum and as EVM-chain rETH representations that you add through the app. The Ethereum standard is ERC-20, and the Ethereum contract is 0xae78736cd615f374d3085123a210448e74fc6393. The receiving account uses an 0x-prefixed 20-byte EVM address.
Use Add a Token when you are adding Ethereum ERC-20 rETH to an available Ethereum account view. Use Add a Network when the rETH representation is on an EVM chain that must be added first. The card does not ship with rETH enabled, so this app step is part of the normal rETH setup.
The private key controlling the rETH 0x address is generated inside the secure element and never leaves it. The card uses an EAL6+-certified chip. rETH remains an Ethereum ERC-20 token, or an EVM-chain representation, while the card protects the account key used to sign transactions.
During Dual-Card Set initialisation, the seed is generated inside both secure elements. The second card is the backup for the same wallet that controls the rETH address. It is not a separate rETH account. Under the default setup, there is no recovery phrase to write down.
No. The card itself has no fingerprint or face sensor. Unlocking for app use relies on the phone’s own fingerprint or face unlock through the Cryptnox app. The rETH account’s private key remains inside the card’s secure element, and the card signs when the transaction requires it.
Yes. The free Cryptnox app on iOS and Android connects to Web3 through WalletConnect and works with MetaMask. For rETH, check that the selected route matches Ethereum ERC-20 rETH or the EVM-chain representation you added before approving a transaction request.
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.