Skip to main content

How to start at a different block height?

SubQuery TeamLess than 1 minute

How to start at a different block height?

Video guide


By default, all starter projects start synchronising the blockchain from the genesis block. In otherwords, from block 1. For large blockchains, this can typically take days or even weeks to fully synchronise.

To start a SubQuery node synchronising from a non-zero height, all you have to do is to modify your project.yaml file and change the startBlock key.

Below is a project.yaml file where the start block has been set to 1,000,000.

specVersion: 0.0.1
description: ""
repository: ""
schema: ./schema.graphql
  endpoint: wss://
  - name: main
    kind: substrate/Runtime
    startBlock: 1000000
        - handler: handleBlock
          kind: substrate/BlockHandler

Why not start from zero?

The main reason is that it can reduce the time to synchronise the blockchain. This means that if you are only interested in transactions in the last 3 months, you can only synchronise the last 3 months worth meaning less waiting time and you can start your development faster.

What are the drawbacks of not starting from zero?

The most obvious drawback will be that you won’t be able to query for data on the blockchain for blocks that you don’t have.

How to figure out the current blockchain height?

If you are using the Polkadot network, you can visit visit this siteopen in new window, select the network, and then view the "Finalised Block" figure.

Do I have to do a rebuild or a codegen?

No. Because you are modifying the project.yaml file, which is essentially a configuration file, you will not have to rebuild or regenerate the typescript code.