Yes. The Cryptnox Crypto Hardware Wallet – Dual-Card Set can hold KelpDAO Restaked ETH as the ERC-20 rsETH token on Ethereum mainnet after you add its token contract manually. rsETH is not enabled on arrival. Add 0xA1290d69c65A6Fe4DF752f95823fae25cB99e5A7 once in the Cryptnox app, then receive rsETH to your 0x Ethereum address and approve rsETH actions with the card.
CRYPTNOX products are also available worldwide through our official Amazon stores.
KelpDAO Restaked ETH is held on Cryptnox as rsETH, an ERC-20 token on Ethereum mainnet. The card does not arrive with rsETH already listed, so the first rsETH-specific step is adding the Ethereum token contract before you receive a transfer. For this asset, the contract address is the detail that separates Ethereum rsETH from similarly named or separately deployed assets.
The Ethereum rsETH token uses the 0x-prefixed 20-byte EVM address format. Your receiving address for rsETH is therefore an Ethereum-style 0x address controlled through your Cryptnox card. Before adding the token, you can check the Ethereum contract on the rsETH token page on Etherscan and then enter the same contract in the Cryptnox app.
If you are checking which chains and assets can be managed before moving rsETH, review the Cryptnox coin and blockchain support page and then add the Ethereum rsETH contract manually in the app. The supported route for this page is Ethereum mainnet rsETH, not an automatically enabled asset listing.
Because rsETH is not pre-programmed, setup is a manual token-add step. Open the free Cryptnox app on iOS or Android, use the route for adding a token, choose Ethereum mainnet, and enter the rsETH contract exactly as 0xA1290d69c65A6Fe4DF752f95823fae25cB99e5A7. Do this before sending rsETH to the address shown in the app.
For KelpDAO Restaked ETH, do not rely on the token name alone. ERC-20 assets on Ethereum are identified by contract address, and other EVM-chain representations can require different network and token details. The contract above is the Ethereum mainnet rsETH contract; another EVM network must be handled as a separate manual addition.
For app and card workflow help, use the Cryptnox hardware wallet tutorials while keeping the rsETH-specific contract address above as the asset detail you enter. The tutorial route helps with the wallet workflow; the rsETH route still depends on entering the Ethereum ERC-20 contract correctly.
The rsETH support route here is Ethereum mainnet first: ERC-20 token, Ethereum contract, and 0x receiving address. Other EVM-chain representations are not enabled automatically. If the rsETH you intend to manage is on another EVM network, add that network through Add a Network or add the correct token contract through Add a Token after the network is available.
This distinction matters because an EVM address can look similar across networks while the token contract and chain context are different. Sending based only on the ticker can create confusion. For Ethereum rsETH, use 0xA1290d69c65A6Fe4DF752f95823fae25cB99e5A7; for any other EVM representation, use the network and contract details for that representation.
KernelDAO has published guidance about recovering rsETH from sunset networks, which makes the chain context important when handling rsETH outside a straightforward Ethereum mainnet transfer. On Cryptnox, Ethereum rsETH and another EVM-chain representation should be treated as different setup paths even when the visible ticker is the same.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set is the product to choose when you want the second card to act as the backup for the wallet address that receives Ethereum rsETH. The set ships uninitialised. During setup, the seed is generated inside both secure elements, so both cards are prepared for the same wallet without making written recovery words the default backup method.
For KelpDAO Restaked ETH, that means the Ethereum 0x address you use after adding the rsETH token contract can be backed by the second card from the start. The backup card is not a separate rsETH account; it is the paired backup for the same wallet setup created during initialisation. Importing an existing 12- or 24-word BIP39 recovery phrase is available as an advanced option, but the default Dual-Card Set flow creates the backup through the second card.
This is especially relevant for rsETH buyers who want the backup method decided before sending the first transfer. Initialise the Dual-Card Set, add the Ethereum rsETH contract, and only then send rsETH to the displayed 0x address.
Cryptnox is a contact and NFC smart card. For rsETH, that gives you two ways to present the card when approving an Ethereum token action: tap it to a phone, or insert it into a reader. The token you add remains the Ethereum ERC-20 rsETH contract, and the receiving address format remains the 0x EVM address shown by the wallet.
Private keys for the address that can receive rsETH are generated inside the secure element and never leave it. The card uses an EAL6+-certified chip. Unlock uses the phone’s biometrics through the Cryptnox app; the card itself has no biometric sensor. That keeps the phone unlock step separate from the card’s role in approving rsETH actions for the Ethereum address.
When you approve an rsETH send or another rsETH-related Ethereum action, check the network and token details before approval. The network should be Ethereum mainnet for the contract 0xA1290d69c65A6Fe4DF752f95823fae25cB99e5A7. If a different EVM chain is shown, treat it as a separate rsETH representation that must have its own correct contract.
The Cryptnox app connects to Web3 through WalletConnect and works with MetaMask, which matters when rsETH is used through an Ethereum interface instead of only being received as a token transfer. In that flow, confirm that the connected network is Ethereum mainnet when you intend to use the ERC-20 rsETH contract at 0xA1290d69c65A6Fe4DF752f95823fae25cB99e5A7.
The key point for an rsETH holder is to separate viewing and routing from approval. WalletConnect or MetaMask can provide the Web3 route, while the Cryptnox card approves the action for the 0x address that controls the token. The private key for that address stays inside the secure element.
If you are comparing rsETH handling with other EVM assets, the Polygon hardware wallet page and Ronin hardware wallet page show how network-specific setup can differ from Ethereum rsETH. Those comparisons are useful because rsETH depends on the Ethereum ERC-20 contract route unless you intentionally add another EVM representation.
Buy Cryptnox for rsETH if your priority is holding the Ethereum ERC-20 token at 0xA1290d69c65A6Fe4DF752f95823fae25cB99e5A7 with a card-based signing setup and a second card prepared as the backup during initialisation. The rsETH work you perform after unboxing is specific: initialise the Dual-Card Set, add the Ethereum token contract, then receive to the 0x address controlled by your card.
The broader Cryptnox hardware wallet collection is useful if you are deciding between supported asset routes before choosing the Dual-Card Set. For KelpDAO Restaked ETH itself, the decisive details remain Ethereum mainnet, ERC-20, the exact contract address, and the 0x-prefixed receiving address format.
If your portfolio combines rsETH with assets that do not follow the same Ethereum ERC-20 model, review their setup separately. Bitcoin does not use the 0x EVM address format, so the Bitcoin hardware wallet page is a better comparison for that chain. Tron also has its own route, covered on the Tron hardware wallet page. Keep rsETH on its intended Ethereum setup unless you intentionally add another EVM representation.
Cryptnox is Swiss-engineered, and the cards are made in Switzerland. For an rsETH buyer, the practical purchase decision still comes down to the Ethereum support route: add the correct ERC-20 contract, use the 0x address, and keep the backup card ready from initialisation.
No. rsETH is not enabled on arrival. Add it manually as an Ethereum ERC-20 token with contract 0xA1290d69c65A6Fe4DF752f95823fae25cB99e5A7 before receiving a transfer. After the token is added, use the 0x Ethereum address controlled by your Cryptnox card.
Choose Ethereum mainnet for the rsETH route described here. The asset is held as an ERC-20 token on Ethereum at 0xA1290d69c65A6Fe4DF752f95823fae25cB99e5A7. If your rsETH is represented on another EVM chain, add that network or token manually with its own details.
Ethereum rsETH uses a 0x-prefixed 20-byte EVM address. That is the receiving address format for ERC-20 rsETH on Ethereum mainnet. Before receiving funds, confirm that the rsETH token contract has been added and that the displayed address is controlled by your Cryptnox card.
The Dual-Card Set ships uninitialised. During setup, the seed is generated inside both secure elements, making the second card the backup for the wallet that controls your rsETH receiving address. Written recovery words are not the default backup method, although importing an existing 12- or 24-word BIP39 recovery phrase is an advanced option.
No. Unlock uses the phone’s biometrics through the Cryptnox app, and the card itself has no biometric sensor. For rsETH, the card’s role is to approve actions for the Ethereum 0x address while the private key remains inside the secure element.
Yes. The Cryptnox app connects to Web3 through WalletConnect and works with MetaMask. When using rsETH, confirm that the Web3 interface is on Ethereum mainnet for contract 0xA1290d69c65A6Fe4DF752f95823fae25cB99e5A7, unless you intentionally added another EVM-chain representation.
Other EVM-chain representations are possible only when that network or token contract is manually added. Use Add a Network when the EVM chain must be added first, or Add a Token when the network is already available. Do not reuse the Ethereum rsETH contract for a different network.
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.