|Price||$0.0172 (222 sats)|
|24H Mkt. Cap ($MM)||$31.21 MM|
|30 Day Avg. Mkt. Cap ($MM)||$26.07 MM|
|24H Volume ($MM)||$4.47 MM|
|30 Day Avg. Volume ($MM)||$4.38 MM|
|Circ. Supply||1,813,658,595 FTM (91.27%)|
|Total Supply||1,987,133,655 FTM|
|Max Supply||3,175,000,000 FTM|
|All-time High USD||$0.03 (29 May 19)|
|All-time High BTC||2,515 sats (29 May 19)|
Fantom (or the "Project") is building a platform consisting of a fast, scaleable, and secure DAG-based distributed ledger using aBFT principles to achieve consensus, and a new verifiable compiler and register-based virtual machine for smart contract execution.
The vision of FANTOM is to grant compatibility between all transaction bodies around the world using DAG technology, and to create new infrastructure with high reliability that allows for real-time transactions and data sharing. The Project also aims to develop a new verifiable compiler and register-based virtual machine, which automatically checks for correctness, generates proofs of smart contract behavior, and execute instructions more efficiently than existing models.
|Token Type||ERC-20 and BEP2|
|Seed Sale Allocation||3.15% of Total Supply|
|Seed Token Sale Date||Feb - Mar 2018|
|Seed Sale Price||$0.016|
|Private Sale Allocation||37.04% of Total Supply|
|Private Token Sale Date||Apr - Jun 2018|
|Private Sale Price||Private Sale 1 - $0.031, Private Sale 2 - $0.035|
|Amount Raised in Private Sale||Private Sale Round 1 - $24.7 MM, Private Sale Round 2 - $12.9 MM|
|Public Sale Allocation||1.57% of of Total Supply|
|Public Token Sale Date||15 Jun 2018|
|Public Token Sale Price||$0.04|
|Amount Raised in Public Sale||~$2.2MM (4,947 ETH)|
|Circulating Supply||12,013,965,609 (41.7%)|
As of May 2019, Fantom has used approximately 28.2% of TGE funds according to the allocations below:
Fantom holds its cryptocurrency funds in a number of single-signature wallets held by different persons within the organization, whose identity the team chose not to disclose for security reasons. Fantom's fiat currencies are held in a bank account that requires the approval of two of three individuals within Fantom for payments to go out. The payment of cryptocurrency funds also requires the approval of two of three individuals, and transaction records are shared with all three individuals to provide a complete audit trail of all funds spent.
The following chart represents the number and breakdown of all FTM tokens that are to be released into circulation on a monthly basis.
The native token is envisioned to have the following functionalities:
The most recent balances of ERC-20 and BEP2 FTM tokens can be found here:
|PLANNED DATE||MILESTONE||ACTUAL DATE||TIMING||COMMENTS|
|2018: Q2||Validate Lachesis protocol and the Fantom architecture||2019: Q2||Late||Paper on OPERA Paper on Fantom Paper on ONLAY|
|2018: Q2||Private and public token Sale||2018: Q2||On time||Medium|
|2018: Q2||FANTOM Wallet development and distribution||2018: Q4||Late||Web Wallet Desktop Wallet Mobile Wallet|
|2018: Q3||Open main Middleware and release API||2018: Q3||On time||API|
|2019: Q1||Achieve virtual Machine EVM Compatibility||2019: Q1||On time||EVM EVM in Rust|
|2019: Q3||Begin Lachesis mainnet development, complete consensus model and fee model||In progress||On time||Lachesis Fantom PoS|
Commercial Partnerships and Business Development Progress
Some developers' Github profiles are not available, as most of their work is done via Sfxdx's Github account.
The FTM token is currently listed on 10 exchanges, according to CoinMarketCap. Core crypto trading pairs include FTM/BTC, FTM/USDT, and FTM/ETH.
Fantom has 53 public and 71 private repositories. The team has mostly been using its public Github repositories.
Golang build of the Fantom's distributed ledger.
Rust build of the Fantom's distributed ledger.
Java build of the Fantom's distributed ledger (used mainly for research purposes).
EVM implementation in Golang
Register-based virtual machine in LLVM with translators from higher level object-oriented programming languages.
Fantom pay mobile application
Backend api for the Fantom network
Api for merchants to ineract with the Fantom pay application
WebAssembly (WASM) Virtual Machine for execution of smart contracts
Implementation of pairing-based cryptography in golang
A detailed description on how the native token will be used on the network is available here.
Planed use cases include the following:
Currently, Fantom has a wallet available on iOS and Android connected to an earlier version of Fantom's distributed ledger. It allows a user to transfer testnet tokens between accounts, with sub-second confirmations.
Fantom has developed a general framework named Lachesis for DAG-based consensus to build scalable distributed systems. The Fantom team has also developed a new consensus protocol ONLAY based on the Lachesis framework. ONLAY guarantees practical Byzantine fault tolerance in the presence of up to one-third of the participants that are compromised. The key challenge Fantom aims to address is a fast consensus and reliable ordering for events.
For the ONLAY Protocol, the Fantom team states that its initial experiments have shown that leveraging the assigned layers of event blocks can help achieve more deterministic ordering of blocks and that the new layer-based protocol is a promising alternative to achieve deterministic, resilient distributed ledgers.
The following are some steps for a transaction to reach finality in the Fantom network:
Mainchain and Atropos of Lachesis DAG
Thus, there will be a total of five confirmations to be sent and the fifth receipt is the final confirmation of a successful transaction.
The team notes there are some cases that a submitted transaction can fail to reach finality. Examples include a transaction does not pass the validation, e.g. insufficient account balance, or violation of account rules. The other kind of failure is when the integrity of a DAG structure and event blocks is not complied due to the existence of compromised or faulty nodes. In such unsuccessful cases, the event blocks are marked for removal and detected issues are notified to all nodes. Receipts of the failure will be sent to the client.
The Fantom network consists of nodes that are distinguished into users and validators. The ONLAY framework introduces graph layering on the DAG to achieve reliable ordering of event blocks.
ONLAY framework leverages the assigned layers of event blocks in order to achieve consensus of final ordering of event blocks and transactions across distributed systems. Each node maintains its own DAG and computes the main chain of finality event blocks. The consensus protocol achieves optimized pBFT with deterministic DAG-based finality on valid transactions and honest nodes. Once a block is finalized in ONLAY, it is final without further need of several block confirmations like in the probabilistic finality in Nakamoto consensus (in BTC, ETH).
There are three blockchains in the Fantom architecture: the Node Service ("NS") blockchain, the OPERA chain, and the Mainchain ("MC") blockchain. The NS blockchain stores the node identifiers of the network. The OPERA is the directed acyclic graph consisting of event blocks. The MC blockchain is the main chain, which stores the event blocks that are validated and finalized by the network.
For the three blockchains listed above:
Key features of the new programming language toolchain include:
Fantom is planning to implement Proof of Stake to secure the network. It will be permissionless, allowing anyone to participate in it by running or delegating to a validating node.
Nodes that participate to achieve consensus are called "validator nodes". A user can run a validating node by staking a minimum of 3,175,000 native FTM tokens. A user can also delegate to a validating node any amount of FTM, and the account running the validator account will receive a fixed 15% fee from all rewards generated by the delegator's tokens.
Yearly returns for validator nodes (block rewards only)
Validator rewards have two components:
Validator rewards are also influenced by a Proof of Importance score. This score is a multi-factor model that influences the rewards earned by validators. A validator earns rewards not simply based on the number of native FTM that is staked, but also by a number of other factors including:
1. Validation performance: Given that block finality is reached when an event block has reached the validating threshold of two-thirds of the network's validating power, a validator effectively participated in a block validation if such validation occurred before the validation threshold was reached. An efficient validator should, on average, effectively participate in validating two-thirds of all event blocks. Those who consistently do not participate, or participate after the validation threshold is reached, will be penalized, earn fewer block rewards, and will ultimately be pruned from the network.
2. Originating transactions: Validators will be expected to accept new transactions being submitted to the network and act as originators of such transactions. Those who consistently do not originate transactions will be penalized, receive fewer block rewards, and will ultimately be pruned from the network.
3. Processing power: The processing power of validators will be measured on a regular basis.
Nodes that do not participate in consensus are called "non-validating", or "listening" nodes. These nodes are able to synchronize with the network, submit, and receive transactions. However, they do not contribute to any voting rounds to confirm transactions. Because they do not participate in consensus, running a non-validating node does not earn any rewards.
The Fantom team lists the following as its current and future community strategies:
Telegram (English) | 18K Members
Twitter (English) | 14K Followers
Medium (English) | 1.6k Subscribers
Telegram (Chinese) | 2K Members
Telegram (Korean) | 736 Members
Discord | 250 Members
Facebook (English) | 894 Members
Reddit | 1.7K Subscribers
Fantom sees Hashgraph, IOTA, NANO, and Ethereum as its main competitors.
|Average Confirmation Time||Sub-second||Sub-second||1-60 seconds||1-10 seconds||16 seconds|
|Degree of Decentralization||Permissionless, Proof of Stake, Anyone can join or leave||Permissioned. Nodes must be known in advance of consensus||Partial - Checkpointing Coordinators are closed source||Permissioness, PoW, Anyone can join or leave||Permissionless, PoW, Anyone can join or leave|
|Spam Protection||Fees||Fees||PoW when attaching a transaction||PoW when attaching or receiving a block||Fees|
|Open / Closed Source||Open source||Closed source||Open source||Open source||Open source|
|State of the Network||Testnet available||Testnet deployed privately||Mainnet available||Mainnet available||Mainnet available|
|Smart Contract Support||Yes||Yes||Yes||No||Yes|