The Cryptnox Crypto Hardware Wallet – Dual-Card Set supports Tellor TRB as an ERC-20 token on Ethereum, not as native TRB on Tellor Layer. TRB is not pre-programmed on the cards; you add it once through Add a Token or Add a Network, depending on your setup. Your TRB uses an 0x-prefixed 20-byte EVM address, with private keys generated inside the secure element and kept there.
CRYPTNOX products are also available worldwide through our official Amazon stores.
Tellor TRB can be held with Cryptnox when it is the ERC-20 token on Ethereum. Native TRB on Tellor Layer, also known as tellor-1, is a non-EVM Layer 1 token route and is not holdable on the Cryptnox card. This distinction matters before you receive, withdraw, bridge, or move TRB, because the address format and chain route must match the asset you are sending.
The Ethereum TRB route uses an 0x-prefixed 20-byte EVM address. That is the address type you use when adding and receiving TRB as an ERC-20 token. If an exchange, bridge, or wallet presents Tellor Layer as the withdrawal route, that route is not the one to use with this card setup. Tellor’s own documentation separates Tellor’s protocol information from its bridging guidance, including TRB movement between environments, so the chain selection should be checked before signing a transfer.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set is not shipped with Tellor TRB already enabled. You add TRB once, using Add a Token or Add a Network as appropriate for your app and wallet flow. After the asset route is added, the card signs from the secure element for that Ethereum address. The card does not expose the private key to the phone or reader during that signing flow.
For the current broader asset list, use the Cryptnox coin and blockchain support page before moving funds. If you are comparing this Tellor page with other asset routes, the hardware wallet collection hub is the best place to start.
Tellor is associated with TRB, and the chain context is not just a label in the wallet interface. The Cryptnox card holds the Ethereum ERC-20 version of TRB. The native token on Tellor Layer is a different route for custody and movement, and it should not be treated as interchangeable when choosing where to send funds. A correct route starts with the chain, then the token standard, then the address format.
On Ethereum, TRB uses an EVM address beginning with 0x. That matches the Ethereum account model used by the Cryptnox setup for this asset. If you copy a receiving address from your Cryptnox-connected Ethereum account, you are preparing to receive TRB as an ERC-20 token. If a service asks you to choose a network, Ethereum is the route that corresponds to this support path.
Tellor Layer, also referred to as tellor-1, is a non-EVM Layer 1. Native TRB on that chain is not held by the Cryptnox card. That means you should not send native Tellor Layer TRB to an Ethereum address controlled by your Cryptnox card. The presence of the same ticker does not make the route the same.
The official Tellor bridging documentation is relevant when you are checking how TRB moves between environments. Use it before transferring if your TRB is not already on Ethereum as an ERC-20 token. Once TRB is on Ethereum, the Cryptnox card can protect the signing key for the Ethereum address that holds that token.
TRB is not preloaded on the Cryptnox Crypto Hardware Wallet – Dual-Card Set. The Dual-Card Set ships uninitialised, and token visibility is set up by the user. For Tellor, that means adding TRB as an Ethereum ERC-20 token through Add a Token, or using Add a Network where that is the required route in your wallet flow. The key point is that the added asset must point to Ethereum ERC-20 TRB, not native Tellor Layer TRB.
Before sending TRB to the card-controlled account, confirm that the receiving address is an Ethereum-style 0x-prefixed address. The app and connected wallet flow should be showing the Ethereum route for TRB. If the service sending funds offers multiple TRB network choices, choose the Ethereum ERC-20 route for this setup.
The free Cryptnox app is available on iOS and Android. It is used with the card for setup and signing, and it can unlock the wallet experience using the phone’s biometrics. The card itself has no biometric sensor. The app also connects to Web3 through WalletConnect and works with MetaMask, which is useful when you need an Ethereum wallet interface that can show ERC-20 token balances and prepare transactions for card signing.
If you are setting up the card for the first time, follow the Cryptnox hardware wallet tutorials rather than guessing at the token route. The tutorial area is also useful when pairing the card with the app or when using a reader.
The product used for this setup is the Cryptnox Crypto Hardware Wallet – Dual-Card Set.
When you hold TRB as an ERC-20 token with Cryptnox, the asset is controlled by the private key for the Ethereum address. That private key is generated inside the secure element and never leaves it. The phone, reader, and connected wallet interface can prepare and request a signature, but the signing key remains inside the card’s secure element.
The Cryptnox card uses an EAL6+-certified chip. That certification applies to the chip platform, not to the finished wallet product. For a TRB holder, the practical point is simple: the key controlling the Ethereum TRB address is created and used inside the secure element, while the transaction request is reviewed through the app or connected wallet flow before signing.
The Dual-Card Set ships uninitialised. During setup, the seed is generated inside both secure elements, so the second card is the backup. By default, there is no recovery phrase to write down. Importing a BIP39 recovery phrase of 12 or 24 words is an advanced option rather than the standard setup path.
This backup design is relevant for Tellor TRB because ERC-20 tokens are account-based assets on Ethereum. The second card gives you another way to control the same Ethereum account without requiring a default paper recovery process. You should still store the second card separately and protect access to the Cryptnox app environment used with it.
The app can use the phone’s biometrics to unlock the user experience, while the card itself remains a smart card without a biometric sensor. Transaction signing still depends on the card and its secure element. This separates phone access from private-key custody: the phone helps you interact with the wallet, while the card protects the key that controls the TRB-holding Ethereum address.
The Cryptnox hardware wallet is a contact and NFC smart card. You can tap it to a phone or insert it into a reader. That dual-interface form factor is useful for Tellor TRB because the same Ethereum ERC-20 account can be managed through a mobile workflow or a reader-based workflow, while the private key remains inside the secure element.
For mobile use, the free Cryptnox app on iOS and Android guides the card interaction. When a TRB transaction is prepared through a supported Ethereum wallet flow, the card is used for signing. The TRB token itself is not stored as data on the card; what matters is the private key for the Ethereum address that holds the ERC-20 token on-chain.
For a reader-based setup, the card can be inserted into the reader and used with the connected wallet flow. This is helpful if you prefer to review Ethereum account activity on a larger screen while keeping signing tied to the card. In both cases, the interface choice does not change the supported Tellor route: it remains TRB as an ERC-20 token on Ethereum.
If you manage several networks, keep the route differences visible. A Polygon asset setup is covered separately on the Cryptnox Polygon hardware wallet page, while the Cryptnox Tron hardware wallet page addresses a different network family. Those pages should not be used as instructions for native Tellor Layer TRB.
Before receiving TRB, verify three things: the token is Tellor TRB, the network is Ethereum, and the address begins with 0x. That combination matches the Cryptnox support route for this asset. If a withdrawal screen offers Tellor Layer or tellor-1, do not use that option for the Cryptnox Ethereum address.
To receive TRB, use the Ethereum address controlled by your Cryptnox card. The sender or exchange should be set to Ethereum ERC-20. If the TRB token is not visible immediately in your wallet interface, add the token rather than assuming the transfer route was wrong. Token visibility and token custody are not the same thing: the card controls the Ethereum address, while the interface displays the ERC-20 balance after the token is added.
When sending TRB, the wallet interface prepares an Ethereum transaction for the ERC-20 token. The card signs the transaction through the secure element after you review the details in the app or connected wallet flow. Because the asset is on Ethereum in this setup, the recipient address should also be valid for the intended Ethereum transaction route.
The Tellor documentation describes the Tellor protocol, while Cryptnox handles the hardware-wallet signing path for the Ethereum ERC-20 version of TRB. Keep those two concerns separate: protocol information explains Tellor, and the Cryptnox card protects the key used to sign from your Ethereum address.
If you also hold assets that use very different address models, compare the Tellor setup with the Cryptnox Bitcoin hardware wallet page. Bitcoin does not use the same ERC-20 token route or 0x address format as Tellor TRB on Ethereum.
This setup is for buyers who want to hold Tellor TRB on Ethereum with private keys generated and kept inside a smart-card secure element. It is a strong fit when your TRB is already on Ethereum as an ERC-20 token, or when you plan to move TRB to that route before receiving it. It is not the right route for holding native TRB on Tellor Layer.
The Dual-Card Set is also suited to buyers who want a backup card from the start. Because the seed is generated inside both secure elements during setup, the second card is the backup by design. There is no default requirement to write down a recovery phrase before using the wallet for TRB. That reduces the setup burden while still keeping a second physical card available if the first one cannot be used.
Buyers who interact with Ethereum wallets can use WalletConnect and MetaMask with the Cryptnox app flow. This is useful for adding the TRB token, reviewing Ethereum account details, and preparing transactions that the card signs. The card remains the signing device; the phone or wallet interface is the place where you view and initiate actions.
Choose this setup if your checklist is clear: TRB as ERC-20, Ethereum network, 0x address, card-based signing, and dual-card backup. If your requirement is native Tellor Layer custody, this is not the supported route. If your requirement is a Swiss-engineered contact and NFC smart card for Ethereum TRB, the Cryptnox Dual-Card Set is the product to evaluate.
Yes, you can hold Tellor TRB as an ERC-20 token on Ethereum with the Cryptnox Crypto Hardware Wallet – Dual-Card Set. Native TRB on Tellor Layer is not held by the card. Use the Ethereum route and an 0x-prefixed EVM address when receiving TRB.
No. TRB is not pre-programmed on the cards. After setup, you add it once through Add a Token or Add a Network, depending on the wallet flow you are using. The asset route must be Ethereum ERC-20 TRB, not native TRB on Tellor Layer.
Use an 0x-prefixed 20-byte EVM address for Tellor TRB on Ethereum. That address format matches the ERC-20 route supported by Cryptnox for TRB. Do not use a native Tellor Layer route when sending funds to the Ethereum address controlled by your card.
Yes. The Dual-Card Set ships uninitialised, and during setup the seed is generated inside both secure elements. The second card is the backup. By default, there is no recovery phrase to write down. Importing a BIP39 recovery phrase is an advanced option.
Private keys are generated inside the secure element and never leave it. The app or connected wallet flow can prepare a TRB transaction, but signing is performed by the card. The chip platform used by the card is an EAL6+-certified chip.
Yes. The free Cryptnox app is available on iOS and Android. It works with the card for setup and signing, connects to Web3 through WalletConnect, and works with MetaMask. The app can use the phone’s biometrics to unlock the experience; the card has no biometric sensor.
No. Native TRB on Tellor Layer, also known as tellor-1, is not the holdable route for this card. Use Ethereum ERC-20 TRB only. If a sending service asks for a network, choose Ethereum for the Cryptnox-controlled TRB address.
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.