Indexing Data on Fuse

Fuse is an EVM-compatible chain focused on payments and real-world business use cases, with fast, low-cost transactions and FUSE as its native token. The Graph can index that onchain activity — DEX swaps, pools, and liquidity; lending and borrowing positions; token transfers and holder balances; and contract events — and serve it over GraphQL with Subgraphs.

Fuse is supported by The Graph with Subgraphs — open APIs you publish to The Graph Network, where Indexers sync and serve the data while you manage your service in Subgraph Studio.

Indexing Fuse with Subgraphs

Getting smart contract data is hard. You write your own indexer, run your own database, and handle chain reorganizations yourself. The Graph removes that work, giving you an open API, called a Subgraph, that you query with GraphQL.

Fuse is EVM-compatible, so the Subgraph workflow is the same as on most EVM chains. You point a Subgraph at your Fuse contract, define the entities you want, and Indexers on The Graph Network keep those entities current and queryable.

Quick Start: Build Your Own Subgraph

Building a Subgraph for Fuse takes three steps:

1. Initialize a Subgraph project from your Fuse contract.
2. Publish it to The Graph Network for decentralized indexing.
3. Query it over GraphQL with an API key.

See the Subgraph pricing page for current query rates and free-tier limits.

Step 1: Initialize your Subgraph project

Install the Graph CLI with the package manager you prefer:

1# npm2npm install -g @graphprotocol/graph-cli@latest34# or yarn5yarn global add @graphprotocol/graph-cli

Verify the install:

1graph --version

Initialize from your Fuse contract:

1graph init

The CLI walks you through a set of prompts:

• Protocol: choose ethereum. Fuse is EVM-compatible.
• Subgraph slug: an identifier for your Subgraph, for example my-fuse-subgraph.
• Directory: where the project is scaffolded.
• Ethereum network: select fuse from the list of supported networks.
• Contract address: the address of the contract you want to index. Find it on explorer.fuse.io.
• ABI: if the CLI cannot fetch the ABI, export it from your build artifacts or the Blockscout contract page. Supply it as a JSON file.
• Start block: the block your contract was deployed at. Set this so indexing does not scan from genesis. The explorer shows the deployment block.
• Contract name: the name of your contract.
• Index contract events as entities: set this to true. The CLI then scaffolds entities and mappings for every emitted event.

Step 2: Write and build your Subgraph

You work with three files:

• Manifest: subgraph.yaml defines which data sources your Subgraph indexes.
• Schema: schema.graphql defines the entities you want to query.
• Mappings: src/mapping.ts uses AssemblyScript that translates on-chain events into your entities.

Point the manifest at Fuse:

1dataSources:2- kind: ethereum3  name: MyContract4  network: fuse5  source:6    address: '0xYourFuseContractAddress'7    abi: MyContract8    startBlock: 123456 # your contract's deployment block

For a full walkthrough of schema and mapping authoring, see Creating a Subgraph.

Generate types and build:

1graph codegen && graph build

Optional: verify locally before publishing. You can test indexing with a local Graph Node⁠ pointed at an RPC endpoint for Fuse. In your docker-compose.yml, set the Ethereum environment to Fuse:

1environment:2ethereum: 'fuse:https://rpc.fuse.io'

Create and deploy to your local node:

1graph create --node http://localhost:8020/ my-fuse-subgraph2graph deploy --node http://localhost:8020/ --ipfs http://localhost:5001 my-fuse-subgraph

Query the local endpoint until your entities look right, then publish.

Step 3: Publish & Curate on The Graph Network

Publishing is an on-chain action that:

• makes your Subgraph available for decentralized Indexers to index,
• makes it publicly searchable and queryable in Graph Explorer,
• and makes it available for Curators to add signal.

Build, then publish from the Graph CLI:

1graph codegen && graph build2graph publish

A browser window opens. Connect your wallet, add metadata (name, description, image), and publish your Subgraph. The --protocol-network flag refers to where The Graph’s protocol contracts live (Arbitrum One), not to Fuse.

Step 4: Query your Subgraph

After you publish, open your Subgraph in Graph Explorer and copy its query URL from the Query button.

1. Create an API key from the API Keys dashboard at thegraph.com/studio. This dashboard handles API keys and billing for The Graph Network.
2. Send GraphQL queries to the query URL with your API key.

See the Subgraph pricing page for query rates, and Querying The Graph for the full query API.