Yes. The Cryptnox Crypto Hardware Wallet – Dual-Card Set can hold native BONE after you manually add Shibarium as an EVM-compatible network in the Cryptnox app. Shibarium is not pre-programmed on the card. Ethereum ERC-20 BONE is also holdable by adding BONE as an EVM token. In both routes, the address uses the EVM 0x format, and private keys are generated inside the secure element and never leave it.
CRYPTNOX products are also available worldwide through our official Amazon stores.
BONE on Shibarium is held as the native gas coin of the Shibarium EVM L2. With the Cryptnox Crypto Hardware Wallet – Dual-Card Set, Shibarium is not a pre-programmed card profile. You add Shibarium once through Add a Network in the Cryptnox app, then use the card-backed wallet with a 0x-prefixed 20-byte EVM address for native BONE.
Ethereum ERC-20 BONE follows a separate route. It is not the native Shibarium coin entry; it is held as an EVM token on Ethereum. A buyer who wants both forms should add Shibarium for native BONE and add the Ethereum token entry for BONE separately.
The Cryptnox coin and blockchain support page is the place to check the current asset support list before funding a newly added Shibarium account. The Cryptnox Crypto Hardware Wallet – Dual-Card Set is the two-card product used for this Shibarium BONE setup.
Shibarium is an EVM-compatible L2, and its native BONE account uses the EVM address pattern: a 0x-prefixed 20-byte address. That is why the Cryptnox support route is to add Shibarium as an EVM network rather than search for a pre-loaded BONE card profile. The card protects the private key for the EVM address, while the app supplies the Shibarium network context for native BONE.
The official Shibarium architecture documentation describes Shibarium as an EVM-compatible L2. For a BONE holder, that matters because the address format looks familiar to Ethereum users, but the coin is native to Shibarium when Shibarium is selected as the network.
Native BONE on Shibarium and ERC-20 BONE on Ethereum should not be treated as the same wallet entry. Native BONE is the gas coin on Shibarium. ERC-20 BONE is an Ethereum token. The Cryptnox app can support both routes, but the user adds the correct network or token first.
This distinction is practical, not cosmetic. A Shibarium BONE deposit should be sent on Shibarium. An Ethereum ERC-20 BONE deposit should be sent on Ethereum. Both may use a 0x-style address, so the selected network label is the part that prevents confusion before a transfer is sent.
The Cryptnox app is free on iOS and Android, and it is where the Shibarium BONE setup begins. For native BONE, add Shibarium once through the app’s Add a Network route. For Ethereum ERC-20 BONE, add the token entry on Ethereum. The card is not shipped with Shibarium already enabled, so the first setup step is the network or token addition.
The same 0x-prefixed address format can appear in both Shibarium and Ethereum contexts. That can be convenient for EVM users, but it also makes the network selection important. If the asset is native BONE, the app view should be on Shibarium before receiving or sending. If the asset is ERC-20 BONE, the app view should be on Ethereum with the token entry added.
If you want the product workflow beside you while adding Shibarium or the Ethereum token entry, the Cryptnox hardware wallet tutorials cover the app and smart card flow for the Dual-Card Set.
When a Shibarium BONE account is created with the Cryptnox Dual-Card Set, the private keys are generated inside the secure element and never leave it. The Shibarium address that receives native BONE is visible because it must be shared for transfers, but the private key that controls that address is not exported to the phone app.
The chip platform uses an EAL6+-certified chip. For a Shibarium buyer, the point is that native BONE signing is built around a secure element rather than a phone-stored private key. The same key containment principle applies when Ethereum ERC-20 BONE is added as a token entry.
This matters when BONE is used beyond simple holding. Shibarium transactions still depend on control of the private key behind the 0x-prefixed address. Cryptnox keeps that key inside the smart card’s secure element while the app provides the Shibarium network interface.
The Dual-Card Set ships uninitialised. During setup, the seed is generated inside both secure elements, so the second card is the backup for the Shibarium BONE wallet. There is no recovery phrase to write down by default. For a manually added network such as Shibarium, that backup model keeps recovery aligned with the same smart card design used for daily BONE access.
If the main card is not available, the backup card is already part of the wallet structure created at setup. That is important for native BONE because access to the Shibarium 0x-prefixed address depends on the private key controlled by the card-backed wallet. The backup is not a later token setting and not a Shibarium network toggle; it is the second secure element created with the wallet from the start.
The backup card should be protected separately from the card used for regular Shibarium activity. Both cards are part of the same Dual-Card Set a buyer receives for the BONE wallet setup.
Cryptnox connects to Web3 through WalletConnect and works with MetaMask. For Shibarium BONE, a buyer can add Shibarium as the EVM network, keep the private key inside the card’s secure element, and use the supported connection routes for Web3 activity. The official Shibarium dapp documentation is written for applications built on Shibarium, so native BONE activity should be handled with Shibarium selected as the network.
WalletConnect and MetaMask interactions do not change the support route for BONE. Native BONE remains the Shibarium gas coin, and Ethereum ERC-20 BONE remains a token on Ethereum. The card-backed wallet signs through the Cryptnox flow while the app or connection interface presents the transaction request.
If you are comparing Shibarium with other EVM-style networks, the Polygon hardware wallet page covers a separate EVM network route, and the Ronin hardware wallet page covers another 0x-address chain context.
The Cryptnox hardware wallet for Shibarium BONE is a contact and NFC smart card. You can tap the card to a phone or insert it into a smart card reader. That dual-interface design fits the Shibarium setup route because the Cryptnox app handles the network addition while the card-backed secure element protects the private key for the 0x-prefixed address.
The card form factor is also relevant to the Dual-Card Set backup model. A BONE holder is not choosing between a phone-only wallet and a paper phrase by default; the second smart card is the backup created during setup. The product is Swiss-engineered and built around two uninitialised cards that become the wallet pair during setup.
Shibarium BONE is an EVM L2 native coin route, while ERC-20 BONE is an Ethereum token route. If you are still deciding which hardware wallet category fits your holdings, the Cryptnox best crypto hardware wallet collection groups broader asset pages in one place.
For contrast with Shibarium’s 0x-prefixed EVM address model, the Bitcoin hardware wallet page covers a different chain and address model, while the Tron hardware wallet page covers another non-Shibarium asset route.
No. Shibarium is not pre-programmed on the card. To hold native BONE, add Shibarium manually as an EVM-compatible network in the Cryptnox app. After the network is added, the card-backed wallet can use a 0x-prefixed 20-byte Shibarium address for native BONE.
Yes. Ethereum ERC-20 BONE is holdable as an EVM token. Add the token entry on Ethereum rather than using the Shibarium native coin route. Native BONE belongs to Shibarium, while ERC-20 BONE belongs to Ethereum, even though both use EVM-style address formatting.
Shibarium uses a 0x-prefixed 20-byte EVM address. That format can look similar to an Ethereum address, so the network choice matters. Use Shibarium for native BONE and Ethereum for ERC-20 BONE.
The private keys are generated inside the secure element and never leave it. The Shibarium address can be displayed for receiving native BONE, but the private key controlling that 0x-prefixed address remains inside the card-backed secure element.
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.
The Dual-Card Set ships uninitialised, and setup generates the seed inside both secure elements. The second card is the backup for the wallet. By default, there is no recovery phrase to write down, though importing an existing 12- or 24-word BIP39 recovery phrase is available as an advanced option.
No. The card itself has no fingerprint reader or face scanner. Unlocking uses the phone's face or fingerprint check through the Cryptnox app, while the smart card remains the hardware-backed device protecting the private key for the Shibarium address.
Yes. Cryptnox connects to Web3 through WalletConnect and works with MetaMask. Add Shibarium first for native BONE, then use the connection flow with Shibarium selected. For Ethereum ERC-20 BONE, use the Ethereum token route instead.
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.