Cryptnox supports Filecoin (FIL) as native FIL on Filecoin EVM/FEVM using a 0x Ethereum-style address. FIL is not pre-programmed on the cards; the user adds the Filecoin network or FIL token once, then uses the FEVM account. This is not legacy Filecoin f1 or f3 wallet-address signing. Private keys for the FIL account are generated inside the card secure element and never leave it.
Buy it from CRYPTNOX shop directly
Accepts:
Preferred shopping solution for US:
Also available on other Amazon shops:
DE, FR, IT, BE, SE, ES, PL, NL, CA, MX, AU
Cryptnox supports FIL through Filecoin’s EVM-compatible L1 environment, commonly called FEVM. The asset remains native FIL on the Filecoin chain, but the account used with Cryptnox is the Ethereum-style 0x address form for Filecoin EVM.
FIL is not pre-programmed on the Cryptnox cards. A buyer adds the Filecoin network or the FIL token once through the app flow, then uses the FEVM account created from the Cryptnox wallet. That distinction matters because Filecoin also has f1 and f3 wallet-address routes, and those are not the signing route for this product page.
Filecoin documentation describes the Filecoin EVM runtime as the EVM execution environment on Filecoin. For Cryptnox, the practical FIL route is native coin, Filecoin chain, 0x address form, and a private key generated inside the card secure element.
Buyers comparing FIL with other supported assets can review the Cryptnox coin and blockchain support page, but the Filecoin setup decision stays specific: use the FEVM route and the 0x account form.
For FIL on Cryptnox, the usable account is a 0x-prefixed 20-byte EVM address. On Filecoin, that 0x address is equivalent to an f410 delegated address. The same FEVM account can therefore appear in a Filecoin-specific delegated form, while the Cryptnox user works from the 0x address path.
This address rule is the most important operational detail before sending FIL. If a service expects a 0x FEVM address, it matches the Cryptnox Filecoin route. If a workflow requires signing from a legacy f1 or f3 Filecoin wallet address, it is a different Filecoin address path.
Filecoin’s explanation of FEVM address types covers the relationship between 0x Ethereum-style addresses and Filecoin delegated addresses. That is why the Cryptnox FIL setup should be treated as Filecoin EVM use, not as a general substitute for every Filecoin address form.
FIL therefore behaves differently from a simple token listing. The coin is native FIL, yet the wallet account is still the EVM-style Filecoin account used for FEVM.
The Cryptnox app is free on iOS and Android. For FIL, setup starts by adding the Filecoin network or FIL token because the cards do not ship with Filecoin already enabled. After that one-time addition, the Filecoin account to use is the 0x FEVM address.
The app connects to Web3 through WalletConnect and works with MetaMask. For Filecoin, those connections should be used through the FEVM route: the account is EVM-style, the address begins with 0x, and the signing path is not f1 or f3 Filecoin wallet-address signing.
If you are preparing the Dual-Card Set for FIL, the Cryptnox hardware wallet tutorials are the right place to review app and card setup. During that setup, the Filecoin-specific choice is the network route: native FIL on Filecoin EVM, added by the user rather than shipped as a pre-set card asset.
Once Filecoin has been added, keep using the same 0x account for the FEVM wallet route. The address form used in the app, in WalletConnect sessions, and with MetaMask should remain the Filecoin EVM account form.
For the Cryptnox Filecoin route, the private key controlling the 0x FEVM account is generated inside the secure element and never leaves it. The phone can display the Filecoin account and start the app flow, while the private key for the FIL account remains in the card.
The card platform uses an EAL6+-certified chip. That certification applies to the chip platform. For a FIL buyer, the practical point is that the FEVM account key is generated inside a secure element rather than on the phone.
Unlock for Filecoin use is handled through the Cryptnox app with the phone’s face or fingerprint unlock. The card itself has no fingerprint sensor and no face sensor. This keeps the user unlock flow on the phone while the private key for the FIL account remains inside the card’s secure element.
The physical product is a contact and NFC smart card. For a FIL holder, the same FEVM account can be used by tapping the card to a phone or by inserting it into a reader. The form factor is dual-interface, which is separate from the Filecoin address decision but important when choosing how the card will be used.
The product used for this FIL route is the Cryptnox Crypto Hardware Wallet – Dual-Card Set. It pairs the FEVM account with a second card backup during setup.
The Dual-Card Set ships uninitialised. During setup for a Filecoin FEVM account, the seed is generated inside both secure elements, so the second card becomes the backup for the same wallet. The result is one FIL account route backed by two smart cards.
By default, the buyer does not write down a recovery phrase before using the wallet. Instead, the second card is retained as the backup card for the same FEVM account. For FIL, that means the 0x address used on Filecoin EVM is backed by the Dual-Card Set rather than by a written phrase in the default flow.
Importing an existing BIP39 phrase with 12 or 24 words is available as an advanced option. That is not the default setup for the Dual-Card Set. The standard path creates the wallet inside both secure elements, which is why the second card is already part of the Filecoin backup design.
This backup model is especially relevant for FIL because the buyer must preserve access to the same 0x Filecoin EVM account. The second card is not a separate Filecoin address; it is the backup for the wallet created during setup.
Cryptnox is a fit for FIL buyers who want native Filecoin through FEVM and are ready to use the 0x address form. It is not the right Filecoin route for a workflow that depends on f1 or f3 wallet-address signing.
The product is also a fit for buyers who want a smart card for their FEVM account. The Cryptnox card can be tapped to a phone by NFC or inserted into a reader through its contact interface, so the Filecoin account is used from a dual-interface card rather than from a plug-in device. The cards are made in Switzerland.
If FIL is one asset in a broader hardware-wallet comparison, the Cryptnox crypto hardware wallet hub helps place Filecoin beside other supported chains. The decision for Filecoin remains narrower than the general category decision: confirm that the intended FIL workflow accepts FEVM and 0x addresses.
For buyers comparing EVM-style account handling, the Polygon hardware wallet page is a useful internal comparison because Polygon also uses EVM-style accounts. Filecoin still requires its own FEVM check because its 0x address has an f410 delegated-address equivalent on Filecoin.
FIL should not be treated as just another ticker added to a card. On Cryptnox, the Filecoin route is defined by native FIL, FEVM, a 0x-prefixed EVM address, and equivalence to an f410 delegated address. Those details are not shared by every supported asset.
Bitcoin is the clearest contrast. A buyer who holds both BTC and FIL should separate the Bitcoin wallet model from the Filecoin EVM route. The Bitcoin hardware wallet page is the better reference for BTC, while this FIL page is focused on FEVM and the 0x Filecoin account.
Tron is also a separate chain decision. If a portfolio includes TRX and FIL, the address forms should not be assumed interchangeable. The Tron hardware wallet page covers that asset route, while Filecoin on Cryptnox remains tied to FEVM.
Ronin is another chain-specific comparison point. Buyers who hold Ronin assets as well as FIL can review the Ronin hardware wallet page, then keep Filecoin setup focused on the 0x FEVM account.
Before using the Cryptnox Dual-Card Set for FIL, confirm that the destination workflow uses Filecoin EVM and accepts a 0x address. The Cryptnox FIL route is native Filecoin through FEVM, with an address equivalent on Filecoin to an f410 delegated address.
Next, initialise the Dual-Card Set so the seed is generated inside both secure elements. The second card is the backup for the same FEVM wallet, which protects access to the same 0x Filecoin account created during setup.
Finally, add Filecoin in the Cryptnox app. Use the 0x address for FIL activity on the Filecoin EVM route, and keep f1 or f3 wallet-address signing separate from this setup.
For the right buyer, the value is specific: FIL on FEVM, a card-based secure element for the 0x account, and a second smart card retained as the backup.
No. FIL is not pre-programmed on the cards. The user adds the Filecoin network or FIL token once in the Cryptnox app, then uses the FEVM account. The supported Filecoin route is native FIL on Filecoin EVM with a 0x Ethereum-style address.
Use the 0x-prefixed 20-byte EVM address for FIL on Cryptnox. On Filecoin, that address is equivalent to an f410 delegated address. Do not treat a legacy f1 or f3 Filecoin address as the same signing route.
No. Cryptnox supports FIL through the FEVM route, not legacy Filecoin f1 or f3 wallet-address signing. The FIL account used with Cryptnox is the EVM-style 0x address, with an f410 delegated-address equivalent on Filecoin.
For the FEVM FIL account, the private key is generated inside the card’s secure element and never leaves it. The app and phone provide the interface for setup, unlock, and Web3 connection, while the key controlling the 0x Filecoin account remains in the smart card.
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 FEVM wallet. By default, the Filecoin setup does not rely on writing down a recovery phrase.
Importing an existing BIP39 phrase with 12 or 24 words is an advanced option. The default Dual-Card Set workflow generates the seed inside both secure elements, making the second card the backup for the same 0x Filecoin EVM account.
No. The card has no fingerprint sensor and no face sensor. Unlock uses the phone’s face or fingerprint unlock through the Cryptnox app. The private key for the FIL account still remains inside the card’s secure element.
The free Cryptnox app connects to Web3 through WalletConnect and works with MetaMask. For FIL, use those connections through the Filecoin EVM route and the 0x address form, not through legacy f1 or f3 Filecoin wallet-address signing.
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.
