<aside> 🧑‍🚀 Fantom is part of a new batch of chains to be added to The Graph’s decentralized network! 🎉

</aside>

<aside> ⚠️ Fantom MIPs Subgraphs on Goerli are expected to be announced during the 1st week of April (see timeline in Fantom | Phase 1 (Testnet) Mission 2 [✅ DONE ]). This will start at the beginning of Mission 2.

Note on Fantom timelines and scoring

• As always, for Phase 1, scoring will only be based on how subgraphs are served (query latency, success rate, and data freshness). While you will not be penalised or rewarded for when the node is ready or syncing starts, please plan ahead knowing when Mission 2 is planned to start. You’ll be scored for Fantom’s Phase 1 only if participating in Mission 2.
• ****From the moment Fantom is announced, everyone has a total of 29 days to have a node ready, which usually takes 2-3 weeks to sync from scratch - Subgraphs may be published to Goerli while nodes may still be syncing.

Due to potentially long syncing times or any other unforeseen software issue, the duration of this Phase may be extended.

</aside>

Missions

There are 2 missions for this Fantom Phase 1:

1. ACTIVE Setting up a Fantom archive node
2. [Soon] Serve Fantom subgraphs and strive for quality of service

Mission #1 | Set up a Fantom archive node & connect to Graph Node [Active]

💻 Hardware Requirements

• CPU: 4 fast CPUs (3.1GHz)
• RAM: 16GB
• Storage: 8TB (equivalent to Amazon EBS General Purpose SSD (gp2) storage, or better)

⏳ Syncing time:

• 2-3 weeks from scratch, if using the full-mpt genesis file mentioned below and with trace transactions included.

📸 Snapshots

• https://download.fantom.network/ (you’ll need the ~~mainnet-109331-full-mpt.g~~ mainnet-5577-full-mpt.g file)

  ⚠️ March 10 update:

  • Please make sure you use the full 5577 genesis file and not 109331.
  • You’ll need to delete all your data if you started with 109331 and restart with 5577.

Updates on community-based archive snapshots:

April 3, 2023

• There is now a community-based archive snapshot available. This is now the fastest way to get a an archive node synced from scratch. Find it here: ftp://[email protected]/storage/mips/fantom-datadir

Step 1/2 : Deploy and sync a Fantom Archive node

Official guides available @ https://docs.fantom.foundation/node/run-an-api-node

In order to serve subgraphs on The Graph’s network, you need to run a “Transaction tracing API” which is a full node with trace transactions generated at transaction processing time. Unfortunately, there’s no snapshot for such type of nodes, but you can sync one from the Full Mainnet Genesis File mentioned above (~~mainnet-109331-full-mpt.g~~ mainnet-5577-full-mpt.g).

Setting up a “Tracing Node”

The recommended setup shared by the Fantom core development team can be found below. Make sure you set it up properly to ensure transaction traces are generated and stored from block 1 at transaction processing time.