Snabbstart

Learn how to easily build, publish and query a subgraph on The Graph.

Prerequisites

• En kryptoplånbok
• A smart contract address on a supported network
• Node.js⁠ installed
• A package manager of your choice (npm, yarn or pnpm)

How to Build a Subgraph

1. Create a subgraph in Subgraph Studio

Go to Subgraph Studio and connect your wallet.

Subgraph Studio lets you create, manage, deploy, and publish subgraphs, as well as create and manage API keys.

Click “Create a Subgraph”. It is recommended to name the subgraph in Title Case: “Subgraph Name Chain Name”.

2. Installera Graph CLI

Kör ett av följande kommandon på din lokala dator:

Using npm⁠:

1npm install -g @graphprotocol/graph-cli@latest

Using yarn⁠:

1yarn global add @graphprotocol/graph-cli

3. Initialize your subgraph

The graph init command will automatically create a scaffold of a subgraph based on your contract’s events.

The following command initializes your subgraph from an existing contract:

1graph init

If your contract is verified on the respective blockscanner where it is deployed (such as Etherscan⁠), then the ABI will automatically be created in the CLI.

When you initialize your subgraph, the CLI will ask you for the following information:

• Protocol: Choose the protocol your subgraph will be indexing data from.
• Subgraph slug: Create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
• Directory: Choose a directory to create your subgraph in.
• Ethereum network (optional): You may need to specify which EVM-compatible network your subgraph will be indexing data from.
• Contract address: Locate the smart contract address you’d like to query data from.
• ABI: If the ABI is not auto-populated, you will need to input it manually as a JSON file.
• Start Block: You should input the start block to optimize subgraph indexing of blockchain data. Locate the start block by finding the block where your contract was deployed.
• Contract Name: Input the name of your contract.
• Index contract events as entities: It is suggested that you set this to true, as it will automatically add mappings to your subgraph for every emitted event.
• Add another contract (optional): You can add another contract.

Se följande skärmdump för ett exempel för vad du kan förvänta dig när du initierar din subgraf:

4. Edit your subgraph

The init command in the previous step creates a scaffold subgraph that you can use as a starting point to build your subgraph.

When making changes to the subgraph, you will mainly work with three files:

• Manifest (subgraph.yaml) - defines what data sources your subgraph will index.
• Schema (schema.graphql) - defines what data you wish to retrieve from the subgraph.
• AssemblyScript Mappings (mapping.ts) - translates data from your data sources to the entities defined in the schema.

For a detailed breakdown on how to write your subgraph, check out Creating a Subgraph.

5. Deploy your subgraph

When you deploy a subgraph, you push it to Subgraph Studio, where you can test, stage and review it. A deployed subgraph’s indexing is performed by the Upgrade Indexer, which is a single Indexer owned and operated by Edge & Node, rather than by the many decentralized Indexers in The Graph Network. A deployed subgraph is free to use, rate-limited, not visible to the public, and meant to be used for development, staging, and testing purposes.

När din subgraf är skriven, kör följande kommandon:

1```sh2graph codegen && graph build3```

Authenticate and deploy your subgraph. The deploy key can be found on the subgraph’s page in Subgraph Studio.

1```sh23graph auth <DEPLOY_KEY>45graph deploy <SUBGRAPH_SLUG>6```

The CLI will ask for a version label. It’s strongly recommended to use semantic versioning⁠, e.g. 0.0.1.

6. Review your subgraph

If you’d like to test your subgraph before publishing it, you can use Subgraph Studio to do the following:

• Run a sample query.

• Analyze your subgraph in the dashboard to check information.

• Check the logs on the dashboard to see if there are any errors with your subgraph. The logs of an operational subgraph will look like this:

  

7. Publish your subgraph to The Graph Network

When your subgraph is ready for a production environment, you can publish it to the decentralized network. Publishing is an onchain action that does the following:

• It makes your subgraph available to be to indexed by the decentralized Indexers on The Graph Network.
• It removes rate limits and makes your subgraph publicly searchable and queryable in Graph Explorer.
• It makes your subgraph available for Curators to curate it.

Publishing with Subgraph Studio

To publish your subgraph, click the Publish button in the dashboard.

Select the network to which you would like to publish your subgraph.

Publishing from the CLI

As of version 0.73.0, you can also publish your subgraph with the Graph CLI.

Open the graph-cli.

Use the following commands:

1```sh2graph codegen && graph build3```45Then,67```sh8graph publish9```

3. A window will open, allowing you to connect your wallet, add metadata, and deploy your finalized subgraph to a network of your choice.

To customize your deployment, see Publishing a Subgraph.

Adding signal to your subgraph

1. To attract Indexers to query your subgraph, you should add GRT curation signal to it.

   • This action improves quality of service, reduces latency, and enhances network redundancy and availability for your subgraph.

2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount.

   • It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on subgraph feature usage and supported networks.

To learn more about curation, read Curating.

To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option:

8. Query your subgraph

You now have access to 100,000 free queries per month with your subgraph on The Graph Network!

You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button.

For more information about querying data from your subgraph, read Querying The Graph.