Yes. Cryptnox supports Lido DAO (LDO) as an ERC-20 token on Ethereum after you add the token once with Add a Token or Add a Network. LDO is not pre-programmed on the card. Use contract 0x5A98FcBEA516Cf06857215779Fd812CA3beF1B32 with an 0x-prefixed 20-byte EVM address. The Ethereum private key is created inside the secure element, and the second card in the Dual-Card Set is the backup.
CRYPTNOX products are also available worldwide through our official Amazon stores.
Lido DAO (LDO) is held on Cryptnox through the Ethereum ERC-20 route. You are not setting up a separate Lido chain on the card. You add LDO once as an Ethereum token, then use the Ethereum address controlled by your Cryptnox card.
The contract to add is 0x5A98FcBEA516Cf06857215779Fd812CA3beF1B32. Lido lists the LDO token in its deployed-contract information, and the address can be checked in the Lido deployed contracts documentation. The same Ethereum token contract is also visible on Etherscan’s LDO token page.
Because LDO is added by contract address, the first setup step matters more than the label shown in a wallet interface. Confirm that the token is on Ethereum and that the address begins with 0x. The Cryptnox coin and blockchain support page is useful when you want to see the Ethereum ERC-20 route beside other supported asset routes.
An LDO balance is tied to an Ethereum address. The practical security question is therefore whether the private key for that address is exposed to the phone or computer used to manage the token. With the Cryptnox Crypto Hardware Wallet – Dual-Card Set, the Ethereum private key for the address that can move LDO is created within the secure element and is not exported.
The card contains an EAL6+-certified chip. That certification belongs to the chip platform. For an LDO holder, the point is that the Ethereum signing key is protected inside the card’s secure element while the LDO balance remains recorded on Ethereum for the corresponding 0x address.
The card does not need to store the LDO token contract as a permanent factory setting in order to protect the key. LDO is added in the app or wallet interface, while the card’s job is to keep the Ethereum private key inside the secure element. This is why the LDO contract address and the Ethereum address format are both central to setup.
Unlock for an LDO action happens through the Cryptnox app using the fingerprint or face unlock capability on your phone. The card itself has no fingerprint or face sensor. After that phone-side unlock step, the card is used for the protected key operation without releasing the private key.
The Dual-Card Set is designed so that your LDO wallet is not dependent on a single physical card. The set ships uninitialised. During setup, the seed is generated inside both secure elements, so the second card becomes the backup for the same wallet rather than a separate wallet with a different Ethereum address.
That matters for LDO because the token balance is associated with one Ethereum address. If the backup card is used, it gives access to the same wallet address and therefore to the same LDO balance recorded on Ethereum. You do not have to create a new address just because you are using the backup card.
For LDO, this keeps the backup simple: add the Ethereum ERC-20 token contract, use the 0x-prefixed address, and keep the second card available for the same wallet. Buyers who want this two-card recovery model should choose the Cryptnox Crypto Hardware Wallet – Dual-Card Set.
The free Cryptnox app is available on iOS and Android. For LDO, the app is where you handle the card unlock flow and add the Ethereum ERC-20 token route. The card stays responsible for the Ethereum private key, while the app and connected wallet interface show the LDO token you added.
The card is a contact and NFC smart card. For an LDO workflow, you can tap the card to a phone or insert it into a smart-card reader. This dual-interface format lets the same card-based Ethereum wallet be used in a phone flow or a reader flow without changing the LDO address.
Cryptnox connects to Web3 through WalletConnect and works with MetaMask. Since LDO is an ERC-20 token on Ethereum, those routes are useful when you want an Ethereum wallet interface while keeping the private key inside the Cryptnox secure element.
If you are setting up the cards before adding LDO, the Cryptnox hardware wallet tutorials provide the product walkthroughs for the app and card process.
LDO is not pre-programmed on the card, so the token you add is defined by the Ethereum contract address you choose. For Lido DAO on this product page, that contract is 0x5A98FcBEA516Cf06857215779Fd812CA3beF1B32. The receiving address should be an Ethereum-style address that starts with 0x.
Do not treat an LDO setup as a native-coin setup. The card controls the Ethereum address; the LDO balance is the ERC-20 token balance linked to that address on Ethereum. The contract identifies the token, and the private key inside the secure element controls the address.
These checks are specific to LDO because the asset is added as a contract-based Ethereum token. The card protects the key for the address; it does not turn LDO into a separate chain or change the Ethereum address format.
If your main use case is Lido DAO, buy for the Ethereum ERC-20 workflow and the two-card backup model. The product used for this route is the Cryptnox Crypto Hardware Wallet – Dual-Card Set: two contact and NFC smart cards that initialise together for one wallet.
The LDO workflow is straightforward once the wallet is set up. Add the Ethereum ERC-20 token contract, use the 0x-prefixed Ethereum address, and keep the second card as the backup for that same address. The Ethereum private key that controls LDO is generated inside the secure element and stays there.
The broader Cryptnox hardware wallet collection explains the card-based hardware wallet range. To buy the two-card product used for LDO through Ethereum ERC-20, use the Cryptnox Crypto Hardware Wallet – Dual-Card Set product page.
LDO on Cryptnox uses Ethereum ERC-20 handling. That makes it different from assets that use another network, another address format, or a native-coin route. Keeping those routes separate helps prevent an Ethereum token setup from being confused with a different asset page.
Bitcoin is not an 0x-address ERC-20 token, so a buyer who also holds BTC should use the separate Cryptnox Bitcoin hardware wallet page for that asset. Polygon uses EVM-style addressing but is not the same as adding the Ethereum LDO contract; the Cryptnox Polygon hardware wallet page covers that network route separately.
The same distinction applies to Tron. LDO on this page means the Ethereum ERC-20 token at 0x5A98FcBEA516Cf06857215779Fd812CA3beF1B32, while Tron has its own handling described on the Cryptnox Tron hardware wallet page. If you also use Ronin, review the Cryptnox Ronin hardware wallet page rather than reusing the LDO contract details.
No. LDO is not pre-programmed on the card. You add it once as an Ethereum ERC-20 token using Add a Token or Add a Network. Use contract 0x5A98FcBEA516Cf06857215779Fd812CA3beF1B32 and confirm that the receiving address is an 0x-prefixed Ethereum address.
Add the Ethereum ERC-20 Lido DAO token contract 0x5A98FcBEA516Cf06857215779Fd812CA3beF1B32. That is the LDO token route for this wallet setup. The address format for receiving LDO is an 0x-prefixed 20-byte EVM address on Ethereum.
The Ethereum private key for the address that controls LDO is generated inside the card’s secure element and is not exported. The LDO balance is recorded on Ethereum for that address, while the Cryptnox card protects the private key used to approve activity from it.
The Dual-Card Set ships uninitialised, and the seed is generated inside both secure elements during setup. The second card is the backup for the same wallet and the same Ethereum address. By default, you do not have to write down a recovery phrase.
Yes. The free Cryptnox app connects to Web3 through WalletConnect and works with MetaMask. Because LDO is an Ethereum ERC-20 token, these routes give you an Ethereum wallet interface while the private key remains protected inside the Cryptnox secure element.
LDO uses an Ethereum address because it is held as an ERC-20 token on Ethereum. The address is an 0x-prefixed 20-byte EVM address. The LDO contract identifies the token; the Cryptnox-secured Ethereum address is what receives and controls the token balance.
No. The card itself has no fingerprint or face sensor. Unlock happens through the Cryptnox app using the fingerprint or face unlock capability on your phone. The card remains the place where the Ethereum private key for the LDO address is protected.
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.