Yes—Cryptnox supports swETH as an ERC-20 token on Ethereum after you add the token once with contract 0xf951E335afb289353dc249e82926178EaC7DEd78. swETH is not pre-programmed on the card. It uses an Ethereum 0x-prefixed 20-byte EVM address, and the private key for that address is generated inside the secure element and never leaves it. In the Dual-Card Set, the second card is the backup created during setup.

swETH is held with Cryptnox through the Ethereum ERC-20 route. It is not a pre-programmed asset on the card, so the setup step is to add the token once by contract address after the Ethereum account is ready. The contract to use for swETH is 0xf951E335afb289353dc249e82926178EaC7DEd78, and the address format is the Ethereum 0x-prefixed 20-byte EVM format.
The Swell Network developer resources list the Ethereum swETH contract, and Etherscan shows the swETH token contract on Ethereum. Those references are useful because swETH is added by contract address rather than selected from something already prepared on the card.
The Cryptnox coin and blockchain support page is the right place to compare supported routes when swETH is part of a wider portfolio. For this asset, the route is Ethereum first, ERC-20 token second, and contract verification before relying on the token display.
Because swETH is not pre-programmed, the card does not arrive with a swETH asset entry already prepared. Start from the Ethereum account controlled by your Cryptnox card, then add swETH using the ERC-20 contract. If the app or connected wallet asks for a network first, use Ethereum. If it asks for a token contract, enter 0xf951E335afb289353dc249e82926178EaC7DEd78.
That setup route keeps the token and the account separate. swETH is the ERC-20 token identified by the contract on Ethereum. The Ethereum address is the 0x-prefixed account that can hold the token. The private key for that address is generated inside the secure element and never leaves it, so adding the token does not move the signing key into the app.
If you want to understand the order of card setup, app use, and signing before adding the swETH contract, the Cryptnox hardware wallet tutorials are the best starting point. They are useful before you rely on a newly added ERC-20 token view for receiving or signing swETH actions.
For swETH, the card protects the Ethereum private key that controls the 0x-prefixed address associated with the ERC-20 token. The swETH contract identifies the token on Ethereum, but the authority to sign from the address comes from the private key. Cryptnox generates that private key inside the secure element, and the key remains inside the secure element.
The chip platform used by the card includes an EAL6+-certified chip. For a swETH holder, the practical point is that the Ethereum signing key is created inside a secure element rather than created in a software-only wallet. The finished card is the signing device you use, while the EAL6+ statement belongs to the chip platform.
swETH does not use a separate address format from Ethereum. It is held through the same 0x-prefixed 20-byte EVM address format used by the Ethereum account. When a swETH-related ERC-20 action needs approval or signing from that address, the card-protected Ethereum key is the signing key involved in the action.
Unlocking the workflow uses the phone’s fingerprint or face check through the Cryptnox app. The card itself has no fingerprint or face sensor. This distinction matters for swETH because the phone can guide the Ethereum token flow while the smart card remains the signing device for the address that holds the token.
The Dual-Card Set matters for swETH because the backup is tied to the wallet that controls the Ethereum address, not to the swETH token contract itself. 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 from the start.
For a new swETH setup, there is no recovery phrase to write down by default. The backup card is created through the initialisation process, and the private key is not exported from the secure element to make that backup. If the Ethereum address controlled by the set holds swETH, the second card is part of access to that same address.
Advanced users may import an existing BIP39 recovery phrase, but that is not the default path for a new Dual-Card Set. For a buyer setting up swETH from scratch, initialise both cards together, confirm the Ethereum address, and add swETH by contract.
The free Cryptnox app on iOS and Android is the mobile path for using the card-protected Ethereum account with swETH. The app connects to Web3 through WalletConnect and works with MetaMask, so swETH can be managed through Ethereum wallet flows after the token has been added by its contract address.
WalletConnect and MetaMask are relevant to swETH because the asset is an ERC-20 token on Ethereum. The connected flow should point to Ethereum, the token should match contract 0xf951E335afb289353dc249e82926178EaC7DEd78, and the account should be the same 0x-prefixed address secured by the Cryptnox card.
If you also hold assets that do not follow the same Ethereum ERC-20 route, compare the chain-specific setup before sending funds. The Cryptnox pages for Polygon hardware wallet support and TRON hardware wallet support are useful comparisons because swETH remains an Ethereum token while those assets use different routes.
The Cryptnox card used for swETH is a contact and NFC smart card. For mobile management of a swETH Ethereum address, you can tap the card to a phone. For contact access, you can insert the card into a reader. The same wallet model applies in both cases: swETH is an ERC-20 token associated with the Ethereum account secured by the card.
This dual-interface form factor fits a swETH setup because the token does not need to be prepared on the card before shipment. Once the wallet is initialised, the Ethereum address can be used for swETH after the token contract is added to the relevant app or connected wallet view.
The broader Cryptnox hardware wallet collection can help buyers compare card-based wallet use cases. If your comparison includes non-Ethereum assets, the Bitcoin hardware wallet page shows a different account model from swETH, while the Ronin hardware wallet page should be treated separately from swETH’s Ethereum ERC-20 route.
The product for this swETH setup is the Cryptnox Crypto Hardware Wallet – Dual-Card Set. It gives you two Swiss-engineered smart cards: one card for everyday signing and a second card prepared as the backup during initialisation. For swETH, those cards secure the Ethereum account key; the swETH token is added afterward as an ERC-20 token on Ethereum.
Buy this setup if you want swETH held through an Ethereum address whose private key is created inside the secure element and kept there. Do not expect swETH to arrive already enabled on the card. The token entry step is part of your wallet configuration: use Ethereum, add the token, and verify 0xf951E335afb289353dc249e82926178EaC7DEd78 before relying on the display.
For a first swETH setup, initialise the Dual-Card Set, confirm the 0x-prefixed Ethereum address, add swETH with contract 0xf951E335afb289353dc249e82926178EaC7DEd78, and keep the second card as the backup for the wallet created at setup.
No. swETH is not pre-programmed on the card. It is held as an ERC-20 token on Ethereum after you add the token once with contract 0xf951E335afb289353dc249e82926178EaC7DEd78. The card secures the private key for the Ethereum address associated with the token.
Choose Ethereum for swETH. The asset is held as an ERC-20 token on Ethereum, and the account address uses the 0x-prefixed 20-byte EVM format. If your setup asks for token details, use contract 0xf951E335afb289353dc249e82926178EaC7DEd78.
The second card backs up the wallet that controls the Ethereum address, not the swETH contract. The Dual-Card Set ships uninitialised, and the seed is generated inside both secure elements during setup. If that Ethereum address holds swETH, the second card is the backup for access to the same wallet.
No. The card itself has no fingerprint or face sensor. Unlock uses the phone’s fingerprint or face check through the Cryptnox app, while the smart card remains the signing device for the Ethereum address that can hold swETH.
Yes. The Cryptnox app on iOS and Android connects to Web3 through WalletConnect and works with MetaMask. For swETH, add the Ethereum ERC-20 token by contract address first, then use the card-protected Ethereum account when the wallet flow asks for signing.
Not by default with a new Dual-Card Set. During setup, the seed is generated inside both secure elements, so the second card serves as the backup. Importing an existing BIP39 recovery phrase is an advanced option, not the normal setup path.
Verify that the chain is Ethereum, the token standard is ERC-20, and the contract is 0xf951E335afb289353dc249e82926178EaC7DEd78. The receiving address should be a 0x-prefixed 20-byte EVM address controlled by the Cryptnox card-secured wallet.
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.