- Network name
- Fantom Opera
- Chain ID
- Block explorer
Like many of the other smart contract-enabled layer 1 blockchains that are now making their way towards the top of crypto market cap rankings--Solana, Cardano, and Avalanche amongst them--Fantom aims to address the key challenges facing the original smart contract network, Ethereum. This mainly includes scalability and speed, accommodating greater transaction volumes whilst retaining affordable transaction costs and security.
Fantom's approach to delivering scalability is modular. Whereas transactions on Ethereum (and many other networks) are all on the same network, sharing infrastructure, Fantom allows new projects to be launched on their own blockchain, almost as layer 2 (L2) networks over the mainnet. Operating independently avoids new projects clogging up Fantom Opera over time by funnelling ever-higher volumes of high traffic through the same channel. Instead, Fantom's approach is to create a 'network of networks'.
So how is this done? Well, the main contributor is what they call Lachesis, an asynchronous byzantine fault tolerance (aBFT) consensus algorithm. Quite the mouthful. BFT refers to the Byanztine Generals Problem, a logic problem commonly cited in crypto circles: how do a set of generals, hampered by the limitations of medieval communication, reach consensus on whether or not they should attack a fortress? And, more critically, how can each general trust the others when they say they will attack, especially when a lack of coordination may result in defeat? Applied to decentralized blockchains, BFT essentially refers to the question of how we can trust a decentralized network's validity when there is the possibility of deceitful actors.
The Lachesis aBFT consensus mechanism gets around the challenges of many alternative mechanisms through being asynchronous. Rather than syncing a validated block with every other node connected to Lachesis (i.e. the Fantom mainnet)--just as every Ethereum validator will sync with all others, post-Merge--the Lachesis node only has to complete blocks within its own network. You can read more about Lachesis and how it works here.
Fantom uses a Proof-of-Stake system to underpin its validator community, and in turn the security and function of the network as a whole. You can stake as little as 1 FTM using the official Fantom wallet, delegating your stake to a validator. To become a validator, you would need to stake at least 1,000,000 FTM.
Both Fantom mainnet (Opera) and the L2 networks built on top of it (Lachesis nodes, powering dapps) are EVM-compatible, meaning you can interact with them using MetaMask.
Fantom's native token FTM is necessary to pay for transactions when connected to Fantom Opera. However, constituent blockchains in the 'network of networks' can create and require use of their own native tokens.
As with adding any network to MetaMask, there are two ways to approach this:
- Add the network using Chainlist.
- Add the network manually. The details you need are at the top of this page.
Once the network is added, you'll be able to select it at any time in future from your previously accessed networks in MetaMask.
Please note the below instructions assume you have already added Fantom to your MetaMask (see above).
On Mobile: On your wallet page, find where it says 'Wallet' centrally at the top of the screen. Immediately below 'Wallet', it will display the network you're currently connected to. Tap here to open a list of the networks you've already added. Scroll until you find Fantom, and tap to set it as your current network.
On Extension: Find the network selector at the top of the app -- it will currently display the network you're connected to, such as 'Ethereum Mainnet', or any other you used last. Access the drop down down menu here, then locate and select Fantom in the list:
Assuming you are using the same account within MetaMask, your wallet address is the same regardless of the network you're connected to.
Fantom Opera's EVM-compatibility means MetaMask can connect to it just as you would to Ethereum mainnet.
However, take care to not confuse your MetaMask address with your address for Fantom Wallet (if you use it). Fantom shares the same address format as Ethereum and EVM-compatible networks (i.e. beginning with 0x) but is different.
No. MetaMask can be used to:
- Store FTM (see below for the different forms this token could be in)
- Interact with dapps that are connected to Fantom mainnet.
To stake FTM, you will need to use the Fantom wallet.
As explained on the Fantom FAQ, FTM can only exist in three formats:
- FTM (native, on Fantom Opera)
- ERC-20: On Ethereum
- BEP-2: On the Binance Chain.
However, and in contradiction to this list, you may be able to bridge FTM onto other networks which have their own version of the ERC-20 standard. For example, you can get a BEP-20 version of FTM on Binance Smart Chain.
When you buy FTM on a centralized exchange, you may also have a choice of networks for your withdrawal. Binance, for example, supports FTM withdrawals to BSC (as a BEP-20 token), Ethereum (ERC-20), and Fantom Opera/mainnet itself. See here for more information.
As with any other network you will use, barring some exceptions, you cannot simply send tokens from one network to another without bridging. In all likelihood, you will lose your tokens if you don't bridge them.
This is because FTM on the Fantom Opera is a fundamentally different token to FTM ERC-20 tokens on Ethereum, for example. Bridging involves moving the token from one format into another.
To do this, Fantom recommend you use multichain.xyz.
Relevant support articles
The Ultimate Guide to FTM (The Fantom Foundation)