Yes—Cryptnox supports OKB as native OKB on X Layer after you add X Layer or OKB once in the Cryptnox app; it is not pre-programmed on the card. X Layer uses a 0x-prefixed 20-byte EVM address. The Cryptnox Crypto Hardware Wallet – Dual-Card Set generates private keys inside the secure element, and the second card becomes the backup because the seed is created inside both secure elements during setup.
CRYPTNOX products are also available worldwide through our official Amazon stores.
OKB support on Cryptnox is for native OKB on X Layer. X Layer is an EVM L2, so the address you use for OKB is a 0x-prefixed 20-byte EVM address. The asset is not pre-programmed on the card, and setup begins by adding X Layer or OKB once in the Cryptnox app.
This matters because OKB has a network-specific custody route. Legacy Ethereum L1 OKB is being phased out and should not be treated as the canonical form for this OKB wallet setup. For planning, receiving, and sending, use native OKB on X Layer rather than assuming any older Ethereum L1 OKB entry is the right destination.
OKX describes X Layer as its EVM L2, and OKX has published an X Layer upgrade and OKB gas optimisation announcement. Those network details are the reason this OKB wallet page is centred on X Layer rather than on a generic EVM token path.
The OKB setup route is explicit: initialise the Dual-Card Set, open the Cryptnox app, then add X Layer through “Add a Network” or add OKB through “Add a Token”. The card does not arrive with OKB already selected, so the first practical step for an OKB buyer is choosing the X Layer route in the app.
The free Cryptnox app is available on iOS and Android. For OKB, the app is where the X Layer entry is added, where the 0x-prefixed account is used, and where WalletConnect or MetaMask access can be reached after configuration. Unlocking uses the phone’s own face or fingerprint unlock through the app; the card itself has no fingerprint reader or face sensor.
If you want to confirm the wider asset list before configuring OKB, the Cryptnox coin and blockchain support page gives the broader network coverage context. For step-by-step product handling before adding X Layer, use the Cryptnox hardware wallet tutorials alongside the app.
For native OKB on X Layer, the controlling private key is generated inside the secure element and never leaves it. That custody model applies to the 0x-prefixed EVM address used for the OKB account, so the key is not created as a normal phone or computer file during the default setup flow.
Each card uses an EAL6+-certified chip. For an OKB buyer, the relevant point is the chip-level protection around the key that controls the X Layer account. The card signs from the secure element, while the app provides the screen and connection flow needed to add X Layer, view the account, and work with WalletConnect or MetaMask.
The Dual-Card Set also changes the recovery model for OKB storage. During initialisation, the seed is generated inside both secure elements, which makes the second card the backup for the same X Layer OKB wallet. By default, there is no recovery phrase to write down. Importing an existing BIP39 recovery phrase is an advanced option, not the normal flow for a new Dual-Card Set.
OKB on X Layer is controlled by the private key behind the EVM address. If that key is lost, the address can no longer be controlled. The Dual-Card Set is built so the backup exists as a second secure element from setup, rather than as a written phrase created during the normal setup path.
The Cryptnox card is a contact and NFC smart card. For OKB, that means the same X Layer account can be used by tapping the card to a phone or by inserting the card into a reader. The card is dual-interface, so OKB custody is not limited to a single card interaction method.
On mobile, the OKB flow starts in the Cryptnox app: add X Layer or OKB, use the 0x-prefixed account, and tap the card when the app asks for card interaction. The phone can use its own face or fingerprint unlock in the app flow, while the card’s role remains key protection inside the secure element.
With a reader, the contact interface gives another way to use the same card form factor for the X Layer account. In either interaction style, the OKB private key remains inside the secure element and the asset route remains native OKB on X Layer.
The Cryptnox app connects to Web3 through WalletConnect and works with MetaMask. For OKB, this becomes useful after X Layer or OKB has been added in the app, because the account you use is the X Layer EVM account represented by a 0x-prefixed 20-byte address.
WalletConnect provides the Web3 connection route from the Cryptnox app. MetaMask also works with the Cryptnox app environment. The important OKB-specific step is selecting X Layer before you rely on the address, because a 0x-prefixed address can appear on more than one EVM network.
If you are comparing other EVM-style custody pages, the Cryptnox Polygon hardware wallet page is a useful comparison because Polygon also uses an EVM address style. OKB remains specific to X Layer in this setup.
The product for this setup is the Cryptnox Crypto Hardware Wallet – Dual-Card Set, sold through the official Cryptnox Dual-Card Set shop page. For OKB buyers, the purchase decision should be based on adding native OKB on X Layer through the app, not on expecting OKB to be preloaded on arrival.
The set ships uninitialised. When you initialise it for an OKB wallet, the seed is generated inside both secure elements, so the second card controls the same wallet as the first. After setup, the second card is the backup for the X Layer OKB address and should be kept separately from the card used day to day.
The cards are Swiss-engineered and use a smart card form factor rather than a cable-style device. The practical result for OKB custody is a thin dual-interface card that can be tapped to a phone or inserted into a reader while the X Layer private key remains inside the secure element.
If you are deciding whether Cryptnox is the right hardware wallet across more than one asset, the Cryptnox hardware wallet collection gives the wider product context. For a non-EVM contrast, compare OKB on X Layer with the Cryptnox Bitcoin hardware wallet page.
Before receiving OKB, confirm that the sender is using native OKB on X Layer and that the receiving address is the 0x-prefixed 20-byte EVM address shown after you add X Layer or OKB in the Cryptnox app. The address format alone is not enough, because EVM networks can share the same visible address style.
The older Ethereum L1 OKB route should not be the default storage plan. Native OKB on X Layer is the holdable form for this setup, and the account should be prepared through the app before any transfer is attempted. That avoids treating OKB as if it were already present in a wallet menu or as if any EVM address were automatically the correct destination.
For another network comparison, the Cryptnox Tron hardware wallet page covers a different address environment. The Cryptnox Ronin hardware wallet page offers another asset-specific comparison while this OKB setup remains tied to X Layer.
Cryptnox supports native OKB on X Layer. X Layer is an EVM L2, so the OKB account uses a 0x-prefixed 20-byte EVM address. Legacy Ethereum L1 OKB is being phased out and should not be treated as the main holdable form for this setup.
No. OKB is not pre-programmed on the card. Add X Layer or OKB once in the Cryptnox app through “Add a Network” or “Add a Token”. That setup step matters because OKB custody should use the X Layer route.
Native OKB on X Layer uses a 0x-prefixed 20-byte EVM address. The address may look like addresses on other EVM networks, but the selected network still matters. For this OKB wallet setup, the network should be X Layer.
The Dual-Card Set ships uninitialised. During setup, the seed is generated inside both secure elements, so the second card becomes the backup for the same X Layer OKB wallet. The default setup does not require writing down a recovery phrase.
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 private keys for the OKB wallet are generated inside the secure element and never leave it. For native OKB on X Layer, that key controls the 0x-prefixed EVM address used by the account after X Layer or OKB has been added in the app.
No. The card itself has no fingerprint reader or face sensor. Unlocking uses the phone’s own face or fingerprint unlock through the Cryptnox app. The card’s role is to protect the OKB private key inside the secure element.
Yes. The free Cryptnox app on iOS and Android connects to Web3 through WalletConnect and works with MetaMask. For OKB, first add X Layer or OKB in the app, then use the X Layer account with its 0x-prefixed EVM 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.
