The Subgraphs are essential for querying blockchain data efficiently, enabling dApps to fetch and display data seamlessly. This guide is designed to help you create and deploy a subgraph your network built by Thanos Stack. This step-by-step tutorial will walk you through the prerequisites, setup, and deployment process to get your graph node.

1. Prerequisites:

   • Install graph-cli: Ensure you have graph-cli version 0.31.0 or higher installed, as it's essential for managing subgraphs.

     # install
     ## latest version 0.90.1 (2024-12-04)
     npm install -g @graphprotocol/graph-cli
     

   • Range

     <https://$>{graph-node endpoint}/deploy
     <https://$>{graph-node endpoint}/deploy/*
     <https://$>{ipfs endpoint}
     <https://$>{ipfs endpoint}/*
     

2. Define Network Endpoints:

   • Set the Graph Node and IPFS endpoints where your subgraph will be deployed.
     • Graph Node Endpoint: https://{graph-node endpoint}/deploy
     • IPFS Endpoint: https://{ipfs endpoint}

3. Workflow Overview:

   • The general process for creating and deploying a subgraph includes:
     1. Generate code resource to build:

        • Navigate to your subgraph's root directory and run:

          cd <YOUR_SUBGRAPH_ROOTPATH>
          
          graph codegen
          

        • This command generates the necessary code in a generated directory. You can specify a different output directory if needed.

     2. Build the Subgraph:

        • Compile your subgraph by executing:

          graph build
          

        • This step ensures that your subgraph is ready for deployment.

     3. Create the Subgraph:

        • Register your subgraph with the Graph Node:

          graph create --node https://{graph-node endpoint} {subgraph-name}
          

        • Replace {subgraph-name} with your desired subgraph identifier.

     4. Deploy the Subgraph:

        • Deploy your subgraph to the specified Graph Node:

          graph deploy --node https://{graph-node endpoint} --ipfs https://{ipfs endpoint} {subgraph-name}
          

        • Ensure that the network name in your subgraph configuration is set to match the network name in your helm value file.