SubQuery is a fast, flexible, and reliable open-source data indexer that provides you with custom APIs for your web3 project across all of our supported networks. To learn about how to get started with SubQuery, visit our docs.
This SubQuery project indexes all TokenCreated events for the Multitokenlauncher (0x6fCc46E73E5B96479F6fA731893534b6Ec6bf5E1
) on Asset Chain Testnet
First, install SubQuery CLI globally on your terminal by using NPM npm install -g @subql/cli
You can either clone this GitHub repo, or use the subql
CLI to bootstrap a clean project in the network of your choosing by running subql init
and following the prompts.
Don't forget to install dependencies with npm install
or yarn install
!
Although this is a working example SubQuery project, you can edit the SubQuery project by changing the following files:
- The project manifest in
project.yaml
defines the key project configuration and mapping handler filters - The GraphQL Schema (
schema.graphql
) defines the shape of the resulting data that you are using SubQuery to index - The Mapping functions in
src/mappings/
directory are typescript functions that handle transformation logic
SubQuery supports various layer-1 blockchain networks and provides dedicated quick start guides as well as detailed technical documentation for each of them.
If you get stuck, find out how to get help below.
The simplest way to run your project is by running yarn dev
or npm run-script dev
. This does all of the following:
yarn codegen
- Generates types from the GraphQL schema definition and contract ABIs and saves them in the/src/types
directory. This must be done after each change to theschema.graphql
file or the contract ABIsyarn build
- Builds and packages the SubQuery project into the/dist
directorydocker-compose pull && docker-compose up
- Runs a Docker container with an indexer, PostgeSQL DB, and a query service. This requires Docker to be installed and running locally. The configuration for this container is set from yourdocker-compose.yml
You can observe the three services start, and once all are running (it may take a few minutes on your first start), please open your browser and head to http://localhost:3000 - you should see a GraphQL playground showing with the schemas ready to query. Read the docs for more information or explore the possible service configuration for running SubQuery.
For this project, you can try to query with the following GraphQL code to get a taste of how it works.
query GetAllTokensCreated {
tokenCreateds{
edges {
node {
id
tokenAddress
owner
name
symbol
}
}
}
}
query GetSingleTokenCreated {
tokenCreated(id: "0xbb5d708468aefcbca97711c99d7c7db270c7c521059367c64703b7edf785472c") {
id
tokenAddress
owner
name
symbol
}
}
You can play around with the Deployed project on The Subquery Explorer