Skip to main content
Version: Old ArrowSquid docs

Run a subgraph


This tutorial uses alpha-quality software. If you encouter any issues while using it please let us know at the SquidDevs Telegram chat.

Dependencies: Docker, Git, NodeJS, Yarn.

It is now possible to run subgraphs using Subsquid data sources such as Archives and the Subsquid network. To do this, run a regular Graph node against firehose-grpc, our drop-in replacement for Firehose.

The easiest way to do so is to use our graph-node-setup repo. Here's how:

  1. Clone the repo and install the dependencies:

    git clone
    cd graph-node-setup
    npm ci
  2. Interactively configure the environment with

    npm run configure

    Configuring the environment

    You will be asked to select a network and provide a node RPC endpoint. You can pick any network from our supported EVM networks; networks that are not currently supported by TheGraph will be available their under Subsquid names.

    The RPC endpoint will only be used to sync a few thousands of blocks at the chain end, so it does not have to be a paid one. However, firehose-grpc does not limit its request rate yet, so using a public RPC might result in a cooldown.

  3. Download and deploy your subgraph of choice! For example, if you configured the environment to use Ethereum mainnet (eth-mainnet), you can deploy the well known Gravatar subgraph:

    git clone
    cd example-subgraph

    # the repo is a bit outdated, giving it a deps update
    rm yarn.lock
    npx --yes npm-check-updates --upgrade
    yarn install

    # generate classes for the smart contract
    # and events used in the subgraph
    npm run codegen

    # create and deploy the subgraph
    npm run create-local
    npm run deploy-local

    GraphiQL playground will be available at

Disabling RPC ingestion

If you would like to use firehose-grpc without RPC ingestion, you can configure the environment to do so by running

npm run configure -- --disable-rpc-ingestion

You will still have to supply an RPC URL, but it won't be used for ingestion, so a public RPC will suffice.

Disabling RPC ingestion introduces a delay of several thousands of blocks between the highest block available to the subgraph and the actual block head.


Do not hesitate to let us know about any issues (whether listed here or not) at the SquidDevs Telegram chat.

  • If your subgraph is not syncing and you're getting
    thread 'tokio-runtime-worker' panicked at 'called `Option::unwrap()` on a `None` value', src/
    errors in the graph-node-setup-firehose container logs, that likely means that the chain RPC is not fully Ethereum-compatible and a workaround is not yet implemented in firehose-grpc. You can still sync your subgraph with RPC ingestion disabled.