Yes. Rocket Pool RPL is pre-programmed in the free Cryptnox app as an ERC-20 token on Base Mainnet. For that RPL route, you do not need to add the token manually. The Cryptnox Crypto Hardware Wallet – Dual-Card Set protects the account private keys inside its secure element, while the app on iOS and Android provides the RPL interface. Other EVM networks and ERC-20 tokens can be added separately in the app when needed.

Rocket Pool RPL is available in Cryptnox through a specific route: the token is pre-programmed in the Cryptnox app as an ERC-20 token on Base Mainnet. That is the key point for an RPL buyer, because the supported entry is already present in the app instead of requiring a custom token setup for this Base Mainnet route.
RPL is handled here as an ERC-20 asset on an EVM network. The app provides the RPL token entry for Base Mainnet, and the card controls the account keys used with that entry. When you open the RPL asset view, the phone is the interface; when a transaction must be signed, the card remains the private-key device.
The wider Cryptnox asset coverage is listed on the coin and blockchain support page, which is the right place to compare RPL on Base Mainnet with other supported networks and assets. If you are still choosing the product category before setting up RPL, the Cryptnox hardware wallet hub gives the broader view of the card-based wallet range.
The important detail is not only the RPL ticker. It is the pairing of Rocket Pool RPL with Base Mainnet in the Cryptnox app. The pre-programmed route means the user should select the RPL entry that belongs to Base Mainnet, rather than treating every ERC-20 token listing as interchangeable across EVM networks.
That matters because the Cryptnox app also supports manual EVM setup. Any EVM network can be added through Add a Network. After that network is added, its native coin and any ERC-20 deployed on that chain can be managed. ERC-20 tokens can also be added through Add a Token. For the RPL route covered here, that manual token step is not the normal path, because the Base Mainnet RPL token is already programmed in the app.
This gives the RPL setup a clear separation: the Base Mainnet RPL entry is already present, while the EVM network and token tools remain available for other routes and other ERC-20 assets.
An RPL-on-Base account in Cryptnox is controlled by private keys created inside the card’s secure element. Those private keys do not leave the secure element when the app displays the RPL entry, when the account is managed, or when the app prepares an ERC-20 action for the card to sign.
Each card uses an EAL6+-certified chip. That chip-level certification is part of the platform used for key generation and key storage. For an RPL buyer, the practical meaning is that the app can show the Base Mainnet token route without becoming the place where the private keys are stored.
The Cryptnox app can use the phone’s biometrics to unlock the app experience. The RPL keys are not moved into the phone for that purpose. The card itself has no biometric sensor, and the private keys remain in the secure element inside the card.
This split is especially relevant for an ERC-20 token such as RPL on Base Mainnet. The app identifies the token route and provides the iOS or Android interface. The card remains the object that holds the keys for the account used with that route.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set ships uninitialised. During setup, the seed is generated inside both secure elements. For an RPL wallet, that means the second card is already the backup for the same wallet created during the initial setup, rather than a separate card that needs a different recovery process by default.
The standard setup does not require writing down a recovery phrase. Instead, the two-card setup creates the backup relationship inside the secure elements during initialisation. Advanced users can import a 12 or 24 word BIP39 recovery phrase, but importing is not the default path for a new Dual-Card Set.
For RPL on Base Mainnet, the backup model and the token listing solve different parts of the setup. The pre-programmed RPL entry helps the app recognise the ERC-20 asset on Base Mainnet. The second card gives the same wallet a backup card from setup. Before sending RPL to the wallet, follow the Cryptnox startup guide so both cards are initialised correctly.
The Cryptnox wallet is a contact and NFC smart card. For RPL on Base Mainnet, that means you can tap the card to a phone when using the mobile app, or insert the card into a reader when using the contact interface. The product is dual-interface, so RPL management is not tied to a single way of presenting the card.
The form factor is simple but important for this token route. RPL is shown in the free Cryptnox app on iOS and Android as a Base Mainnet ERC-20 asset, while the card remains a separate signing object. The phone gives you the RPL interface; the card supplies the secure-element key boundary for the account.
The physical cards are made in Switzerland, and the product is Swiss-engineered. For an RPL buyer, those origin details apply to the cards used in the Dual-Card Set that is initialised for the Base Mainnet RPL route.
The product page for the Cryptnox Crypto Hardware Wallet – Dual-Card Set is the purchase page for the two-card setup described here.
The free Cryptnox app connects to Web3 through WalletConnect and works with MetaMask. For Rocket Pool RPL, the relevant app route remains the pre-programmed ERC-20 token on Base Mainnet. The wallet connection layer does not change where the private keys are held: the keys for the account are generated inside the card’s secure element and do not leave it.
When a Web3 flow involves RPL, check the network context before proceeding. The supported RPL entry in Cryptnox is Base Mainnet, and any connected wallet flow should match the route you intend to use. MetaMask support is useful when you want an EVM wallet interface, while WalletConnect provides the connection path from the Cryptnox app.
If your comparison is between EVM routes, the Polygon hardware wallet page is useful because Polygon is another EVM-network case. The Ronin RON hardware wallet page shows another asset route to compare against RPL on Base Mainnet.
The Dual-Card Set is the Cryptnox product for this RPL setup. It consists of two uninitialised contact and NFC smart cards. During setup, the seed is generated inside both secure elements, so the second card is the backup for the wallet that will manage the pre-programmed RPL entry on Base Mainnet.
For Rocket Pool RPL, the buying checklist is short and specific. The token route is already in the app as an ERC-20 on Base Mainnet. The app is free on iOS and Android. The account private keys are created inside the secure element and stay there. The cards can be tapped to a phone or inserted into a reader.
If your holdings include non-RPL assets, the Bitcoin hardware wallet page gives a non-EVM comparison point, while the TRON hardware wallet page covers a different network route. RPL buyers should still treat Base Mainnet as the specific supported route for the pre-programmed RPL token in Cryptnox.
Yes. Rocket Pool RPL is pre-programmed in the free Cryptnox app as an ERC-20 token on Base Mainnet. For that specific route, you do not need to add RPL manually through Add a Token. Manual token entry is for other ERC-20 tokens or routes that are not already listed.
Use the RPL entry for Base Mainnet in the Cryptnox app. That is the pre-programmed route for Rocket Pool RPL. Because RPL is handled as an ERC-20 token on an EVM network, confirm the Base Mainnet route before receiving or managing the token.
The Cryptnox app lets users add any EVM network through Add a Network. Once an EVM network is added, its native coin and any ERC-20 deployed on that chain can be managed. ERC-20 tokens can also be added manually through Add a Token. The pre-programmed RPL route remains Base Mainnet.
For an RPL account managed with the Dual-Card Set, the private keys are generated inside the card’s secure element and do not leave it. The app shows and manages the Base Mainnet RPL route, while the card remains the private-key holder. Each card uses an EAL6+-certified chip.
The Dual-Card Set ships uninitialised, and setup generates the seed inside both secure elements. That makes the second card the backup for the same wallet from the start. In the default setup, there is no recovery phrase to write down before using the RPL route.
No. The card itself has no biometric sensor. The Cryptnox app can use the phone’s biometrics to unlock the app experience, but that does not move the RPL account private keys into the phone. The private keys remain inside the secure element on the card.
Yes. The free Cryptnox app connects to Web3 through WalletConnect and works with MetaMask. For Rocket Pool RPL, use the pre-programmed Base Mainnet ERC-20 entry in the app and confirm that the connected flow matches the same network route.
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.