Yes. Cryptnox supports Loopring (LRC) as an ERC-20 token on Ethereum after you add the token once with contract 0xBBbbCA6A901c926F240b89EacB641d8Aec7AEafD. LRC is not pre-programmed on the card at shipment. Your LRC uses a 0x-prefixed Ethereum address controlled by private keys generated inside the secure element, and those keys never leave it. In the Dual-Card Set, the second card is created as the backup during initialisation.
CRYPTNOX products are also available worldwide through our official Amazon stores.
Loopring (LRC) is held on the Cryptnox Crypto Hardware Wallet – Dual-Card Set as an ERC-20 token on Ethereum. This route uses an Ethereum account rather than a separate LRC-only address type. The receiving address is a 0x-prefixed 20-byte EVM address controlled by private keys generated inside the secure element.
The token contract to add is 0xBBbbCA6A901c926F240b89EacB641d8Aec7AEafD. Loopring Protocol smart-contract documentation lists LRC on Ethereum, and the same contract can be checked on Etherscan’s LRC contract page. Use the contract address, the Ethereum network, and the LRC ticker together when adding the token entry.
When reviewing the Cryptnox coin and blockchain support page for LRC, treat this asset through its Ethereum ERC-20 route. The important match is the Ethereum token contract and the 0x address controlled by the card, not a preloaded Loopring-only account at shipment.
LRC is not pre-programmed on the card when the Dual-Card Set ships. Initialise the two cards first, then add Loopring once through Add a Token or Add a Network. Use Ethereum as the chain and enter 0xBBbbCA6A901c926F240b89EacB641d8Aec7AEafD as the token contract.
This distinction matters for a buyer comparing hardware wallets for LRC. The Cryptnox card secures the private keys for the Ethereum address; the LRC token entry identifies which ERC-20 contract belongs to that address. The asset route is therefore Ethereum plus the LRC contract, not a factory-enabled Loopring profile.
If you are matching setup screens with the physical card and the Cryptnox app, the Cryptnox hardware wallet tutorials are the relevant place to review the card and app flow before you receive LRC to the Ethereum address.
After LRC has been added with the Ethereum contract, keep using that same 0x-prefixed address for this ERC-20 route. A different address format would not match the LRC path described for this Cryptnox setup.
For this Cryptnox setup, LRC is received to an Ethereum-style address. The address begins with 0x and follows the 20-byte EVM address format. The private keys controlling that address are generated inside the secure element and never leave it.
Before receiving LRC, match three details: Ethereum as the chain, ERC-20 as the token standard, and 0xBBbbCA6A901c926F240b89EacB641d8Aec7AEafD as the token contract. The ticker LRC is useful, but the contract address is the specific identifier for this ERC-20 token entry.
If your holdings include assets beyond LRC, keep the Ethereum ERC-20 setup here separate from other network pages. A buyer comparing EVM token holdings with Polygon assets can use the Cryptnox hardware wallet page for Polygon for that network path. A buyer who also holds Bitcoin should treat the Bitcoin hardware wallet page as a separate asset page, because Bitcoin does not use the LRC ERC-20 contract route described here.
When you initialise the Cryptnox Dual-Card Set, the private keys are generated inside the secure elements and never leave them. For LRC, those keys control the Ethereum address that holds the ERC-20 token at 0xBBbbCA6A901c926F240b89EacB641d8Aec7AEafD.
The card uses an EAL6+-certified chip. That is a property of the chip platform. For an LRC holder, the practical point is that the private key for the 0x-prefixed Ethereum address is created inside the secure element and is not exported to the phone, browser, app, or connected service.
Unlocking the Cryptnox app can use the phone’s fingerprint or face unlock, depending on the phone and app settings. The card itself has no fingerprint sensor or face sensor. The phone unlocks access to the app, while the card keeps the private keys inside the secure element.
This model is useful for an LRC buyer who wants a physical smart card to control the Ethereum address used for the token contract, while still using a mobile app for setup and Web3 access.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set ships uninitialised. During initialisation, the seed is generated inside both secure elements, so the second card is the backup for the same Ethereum address that can hold LRC.
For an LRC buyer, this means the backup is another smart card rather than a phrase to write down in the default setup. You initialise both cards together, then add Loopring as an ERC-20 token on Ethereum with contract 0xBBbbCA6A901c926F240b89EacB641d8Aec7AEafD.
Importing a BIP39 recovery phrase with 12 or 24 words is available as an advanced option. That is not the default path for the Dual-Card Set. The default path creates the seed inside both secure elements, making either card the route to the same LRC-holding Ethereum address after setup.
Buyers who want this exact two-card smart-card setup can review the Cryptnox Crypto Hardware Wallet – Dual-Card Set before adding LRC as an Ethereum ERC-20 token.
The Cryptnox card is a contact and NFC smart card. You can tap it to a phone or insert it into a reader. For LRC, either interface leads back to the same Ethereum address controlled by the secure element.
The free Cryptnox app is available on iOS and Android. After the Dual-Card Set is initialised and LRC has been added with the Ethereum contract, the app provides the mobile route for using the card with the 0x-prefixed address tied to the token.
The Cryptnox app connects to Web3 through WalletConnect and works with MetaMask. For LRC, that Web3 route still uses Ethereum and the ERC-20 token contract 0xBBbbCA6A901c926F240b89EacB641d8Aec7AEafD. The card controls the private keys for the address; the app and connected Web3 flow use that address for the LRC token route.
If LRC is part of a broader hardware-wallet purchase, the Cryptnox hardware wallet collection helps you compare the dual-card smart-card model before you decide where to anchor your ERC-20 holdings.
Cryptnox fits an LRC buyer who wants to hold Loopring through the Ethereum ERC-20 contract rather than through a pre-programmed card entry. You add the token once, verify the contract, and receive to the 0x-prefixed Ethereum address controlled by the secure element.
The product also fits a buyer who wants the backup to be a second smart card created during initialisation. Since the seed is generated inside both secure elements, the second card is the backup for the same Ethereum address that holds LRC.
This page’s LRC route is narrow on purpose: Loopring on Ethereum, standard ERC-20, contract 0xBBbbCA6A901c926F240b89EacB641d8Aec7AEafD, and a 0x-prefixed EVM address. That is the set of details to match before receiving the token to Cryptnox.
If you are separating hardware-wallet research by asset, keep this LRC contract setup apart from the Cryptnox hardware wallet page for Tron and the Ronin hardware wallet page, because this page is specifically about the Ethereum ERC-20 route for Loopring.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set is a contact and NFC smart card product for buyers who want a card-based hardware wallet. For LRC, the relevant setup is Ethereum ERC-20 support through a token entry you add after initialisation.
The key detail is the contract address. Loopring (LRC) must be added with 0xBBbbCA6A901c926F240b89EacB641d8Aec7AEafD on Ethereum. The address you receive to is a 0x-prefixed 20-byte EVM address, and the private keys for that address are generated inside the secure element.
For a buyer comparing the best wallet for LRC, the decision comes down to this route: a dual-interface smart card, an Ethereum ERC-20 token entry, an EAL6+-certified chip, private keys that never leave the secure element, and a second card that serves as the backup from the initial setup.
No. LRC is not pre-programmed on the card at shipment. Initialise the Dual-Card Set first, then add Loopring once as an ERC-20 token on Ethereum. Use contract 0xBBbbCA6A901c926F240b89EacB641d8Aec7AEafD and receive to the wallet’s 0x-prefixed Ethereum address.
Use Ethereum for the LRC route described here. LRC is held as an ERC-20 token on Ethereum, and the receiving address is a 0x-prefixed 20-byte EVM address. The token entry is identified by the Ethereum contract address, not by a separate LRC-only address format.
Add Loopring (LRC) on Ethereum with contract 0xBBbbCA6A901c926F240b89EacB641d8Aec7AEafD. Because this support route is ERC-20 on Ethereum, the contract address is the detail to verify before receiving the token through your Cryptnox-controlled 0x address.
The Dual-Card Set ships uninitialised. During setup, the seed is generated inside both secure elements, making the second card the backup. For LRC, both cards control the same Ethereum address after initialisation, and the default setup does not require writing down a recovery phrase.
Yes. Importing a BIP39 recovery phrase with 12 or 24 words is available as an advanced option. It is not the default setup path for the Dual-Card Set. The default setup generates the seed inside both secure elements so the second card serves as the backup from the start.
No. The smart card itself has no fingerprint sensor or face sensor. App unlocking can use the phone’s fingerprint or face unlock, depending on the phone and app settings. The card’s role is to protect the private keys inside the secure element and keep them from leaving it.
Yes. The free Cryptnox app on iOS and Android connects to Web3 through WalletConnect and works with MetaMask. For LRC, the asset remains the ERC-20 token on Ethereum, using the same 0x-prefixed address controlled by your Cryptnox card.
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.
