Fantom Opera Hardware Wallet

Does the Cryptnox wallet support Fantom Opera?

Yes. Fantom Opera is pre-programmed in the free Cryptnox app for iOS and Android, so FTM on Opera does not need manual network entry. The Cryptnox Crypto Hardware Wallet – Dual-Card Set signs for a 0x-prefixed EVM address while private keys are generated inside the secure element and never leave it. The Fantom ecosystem has moved to Sonic, but Opera still runs; Sonic is a separate EVM chain and must be added as a custom network if you use it.

Fantom Opera support in the Cryptnox app

Fantom Opera is available as a pre-programmed network in the Cryptnox app, which matters for buyers who still hold or receive FTM on Opera after the ecosystem moved to Sonic. During use, select Fantom Opera in the app instead of creating a custom network entry for Opera. The app is free on iOS and Android, and the network route for Opera is already present.

FTM is the native coin of Fantom Opera, an EVM Layer 1. The account format is a 0x-prefixed 20-byte EVM address, so a Fantom Opera receiving address can look like an address used on other EVM networks. That address similarity does not make the chains interchangeable. For FTM on Opera, the important choice is the Fantom Opera network in the app.

Cryptnox lists supported networks and assets on the coin and blockchain support page, where Fantom Opera belongs with EVM networks rather than with chains that use a different address model. If you are comparing wallet options for FTM on Opera, confirm that Opera is directly selectable and that signing stays tied to the card.

• Network: Fantom Opera, pre-programmed in the Cryptnox app.
• Native coin: FTM on Opera.
• Standard: EVM Layer 1 native coin.
• Address format: 0x-prefixed 20-byte EVM address.
• Sonic status: separate EVM chain, added manually through Add a Network when needed.

Opera after the move to Sonic

Fantom Opera and Sonic are not the same chain

The Fantom ecosystem has moved to Sonic, whose mainnet launched with S as the new native token. FTM upgrades to S at a 1:1 rate, as described in the Sonic migration documentation. That migration does not turn Opera into Sonic. Sonic is a new chain, while Fantom Opera remains its own network.

This distinction affects wallet setup. Fantom Opera is pre-programmed in Cryptnox, so FTM on Opera can be managed by selecting Opera directly. Sonic is not pre-programmed in the Cryptnox app. Because Sonic is an EVM network, it can be added through Add a Network as a custom EVM network, and once added its native coin and ERC-20 tokens deployed on that chain can be managed.

Opera still runs

Fantom Opera has not stopped operating just because the ecosystem moved to Sonic. Sonic Labs reversed an earlier shutdown plan and said Opera stays live at least through the end of 2026 in its update on Opera and Sonic. FTM remains tradeable, although many venues have moved to S.

For a Cryptnox user, the practical rule is simple: select Fantom Opera for FTM that is on Opera, and add Sonic as a custom EVM network only when the asset or transaction is on Sonic. A 0x address by itself does not identify the chain. Before receiving or signing, check that the app and the connected Web3 session are using the network you intend.

How Cryptnox secures FTM on Opera

When you initialise the Cryptnox Crypto Hardware Wallet – Dual-Card Set for Fantom Opera, the key material for the 0x EVM account is created inside the secure elements in the two cards. Private keys are generated inside the secure element and never leave it while you use the card for a Fantom Opera address, an FTM transfer, an Opera ERC-20 token, or a Fantom Opera transaction approval.

The two-card model is especially relevant for FTM holders who do not want the default setup to depend on writing down a recovery phrase. 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 same Fantom Opera wallet from the start. Importing a 12/24-word BIP39 seed is available as an advanced option, not as the normal first-run path.

• FTM key creation: the private keys for the Fantom Opera address are generated inside the secure element.
• FTM key containment: those private keys never leave the secure element while the app handles Opera activity.
• Opera backup model: the second card backs up the seed generated during initialisation, instead of asking for a recovery phrase by default.
• Chip assurance: the cards use an EAL6+-certified chip; that property applies to the chip platform.

Unlocking uses the phone’s biometrics through the Cryptnox app when that phone feature is used. The card itself has no biometric sensor. For Fantom Opera, this keeps the phone as the interface for selecting Opera and checking transaction details, while the card remains the signing device for the FTM account.

The Cryptnox Crypto Hardware Wallet – Dual-Card Set is the two-card product used for this setup, including Fantom Opera and other supported networks.

Setting up Fantom Opera in practice

Select Opera rather than adding it

After the Dual-Card Set is initialised, Fantom Opera is chosen from the networks already present in the Cryptnox app. You do not need to enter Opera chain data through Add a Network. That manual route is reserved for EVM networks that are not already programmed in the app, such as Sonic when you need the new Sonic chain.

The first-card setup flow is covered in the Cryptnox startup guide. For an FTM buyer, the key point after setup is to use the Fantom Opera network entry for Opera assets and not to treat Sonic as a renamed Opera network.

Tokens on Fantom Opera

FTM is the native coin on Fantom Opera. ERC-20 tokens deployed on Fantom Opera can be managed, and ERC-20 tokens can be added manually through Add a Token when they are not shown. Adding a token is different from adding a network: Opera itself is already there, while individual token contracts may still need manual entry.

• Initialise the Dual-Card Set with the Cryptnox app.
• Select Fantom Opera in the app for FTM on Opera.
• Use the displayed 0x-prefixed address for Fantom Opera receiving activity.
• Add ERC-20 tokens deployed on Opera through Add a Token when needed.
• Add Sonic through Add a Network only if you are using Sonic and S.

If you also use another EVM network, the Cryptnox hardware wallet for Polygon page is a useful comparison because Polygon also uses an EVM-style address model while remaining a separate network choice.

WalletConnect, MetaMask, and Fantom Opera sessions

Feature	Adoption Rate	Benefit for Fantom Users
Biometrics	40%	Faster, secure access
Air-Gapped	35%	Blocks online hacks
Open-Source	50%	Transparency in code
Multi-Sig	25%	Extra transaction safety

The Cryptnox app connects to Web3 through WalletConnect and works with MetaMask. For Fantom Opera, that means you can use an Opera 0x address in a Web3 flow while the FTM private key remains inside the card’s secure element. The phone displays the session and transaction request; the card signs for the Fantom Opera account.

The Sonic transition makes the network check more important than usual. A Web3 session may show a 0x address while the selected chain is not Opera. If the transaction is meant for FTM on Fantom Opera, confirm that Opera is the active network before approving. If the session is for S on Sonic, add Sonic as a custom EVM network rather than using the Opera entry.

Before approving an Opera transaction

• Network shown: Fantom Opera for FTM on Opera.
• Address type: 0x-prefixed 20-byte EVM address.
• Native coin: FTM, not S.
• Token handling: Opera ERC-20 tokens can be added through Add a Token.
• Chain distinction: Sonic is a separate EVM chain, not the Opera network under a new name.

For buyers building a broader card-based setup, the Cryptnox crypto hardware wallet collection places Fantom Opera beside other supported chains, while this page focuses on the Opera-specific support route.

Contact and NFC card use for Fantom Opera

The Cryptnox Crypto Hardware Wallet – Dual-Card Set uses a contact and NFC smart card form factor. For Fantom Opera, you can tap a card to a phone when using the mobile app, or insert the card into a reader. That dual-interface design fits the way Opera users move between app-based account viewing, WalletConnect sessions, and MetaMask-related flows.

In a typical Fantom Opera approval flow, the Cryptnox app shows the Opera network, the 0x address, and the FTM or ERC-20 transaction request. The phone provides the app interface and the unlock flow. The card provides the secure signing environment for the Opera account, without adding a sensor to the card itself.

The cards are Swiss-engineered and use an EAL6+-certified chip. For a Fantom Opera buyer, the relevant outcome is that the same two-card setup used to protect FTM on Opera can also support other networks available in the Cryptnox app or added through the EVM Add a Network path.

If you hold assets with a different account model, compare Opera’s 0x EVM address with the Cryptnox hardware wallet for Tron page or the Cryptnox hardware wallet for Bitcoin page. Those comparisons help separate address format, network selection, and asset handling before you receive funds.

Who should choose Cryptnox for Fantom Opera

Cryptnox is a good fit for a buyer who still needs Fantom Opera directly in the wallet app, rather than treating the move to Sonic as the end of Opera support. If your FTM activity is on Opera, the pre-programmed Opera network avoids custom network entry. If your activity has moved to Sonic, use Add a Network for Sonic because it is a separate EVM chain.

The Dual-Card Set is also suited to an FTM holder who wants the backup to be another card created during the initial setup. The second card is not an afterthought for Fantom Opera access; it is the backup produced when the seed is generated inside both secure elements. Keep both cards secure, because either card can matter for access to the same wallet.

• Choose Cryptnox if your FTM is on Fantom Opera and you want Opera already listed in the app.
• Use the Opera network for FTM and Opera ERC-20 tokens.
• Use Add a Network for Sonic and S.
• Use Add a Token for ERC-20 tokens deployed on Fantom Opera when manual token entry is required.
• Check the network before signing, especially when a Web3 session uses a 0x address.

If you also manage Ronin, the Cryptnox hardware wallet for Ronin page gives another EVM-style comparison. Fantom Opera remains different because it is already pre-programmed in the Cryptnox app, while Sonic must be added as a custom EVM network.

Frequently asked questions

Is Fantom Opera pre-programmed in the Cryptnox app?

Yes. Fantom Opera is pre-programmed in the free Cryptnox app for iOS and Android. Select Fantom Opera when you want to manage FTM on Opera. You do not need to add Opera through Add a Network, although other EVM networks can be added manually when they are not already present.

Does Cryptnox support Sonic the same way it supports Fantom Opera?

No. Fantom Opera is already programmed in the Cryptnox app, while Sonic is a separate EVM chain and is not pre-programmed. If you need Sonic, add it through Add a Network as a custom EVM network. Use Fantom Opera for FTM activity on Opera, not for S on Sonic.

What address format does Fantom Opera use?

Fantom Opera uses a 0x-prefixed 20-byte EVM address. That format may look like other EVM network addresses, but the chain still matters. Use the Fantom Opera network in the Cryptnox app when receiving or signing for FTM on Opera, and check the selected network before approving a transaction.

How does the Dual-Card Set back up an FTM wallet?

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 same Fantom Opera wallet. The default flow does not ask you to write down a recovery phrase. Importing a 12/24-word BIP39 seed is an advanced option.

Can I manage ERC-20 tokens on Fantom Opera?

Yes. Fantom Opera is an EVM network, and ERC-20 tokens deployed on that chain can be managed. Opera itself is already present in the Cryptnox app. If a specific token is not shown, add it manually through Add a Token while keeping Fantom Opera selected as the network.

Where are the private keys for my Fantom Opera address kept?

The private keys for the Fantom Opera account are generated inside the secure element and never leave it. The Cryptnox app is used for the Opera account, network, tokens, WalletConnect session, and MetaMask-related flow, while signing stays tied to the card for the 0x EVM address.

Is Fantom Opera still live after the Sonic move?

Yes. The ecosystem has moved to Sonic, but Fantom Opera still runs. Sonic is a new chain with S as its native token, while Opera remains a separate network for FTM. Many venues have moved to S, so always check whether the asset and transaction are on Opera or Sonic.

Is the Cryptnox wallet an HD wallet with a new receive address for each transaction?

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.

Does Cryptnox ship worldwide, and will I pay import duties?

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.