1. First login to the graph site with your github account, then go to Dashboard on the link here https://thegraph.com/explorer/dashboard and there you will have big button that says Add Subraph, click on it and fill the info needed to add subgraph.

2. After you add your boilerplate you will be provided with 3 additional step that you need to do.

3. so first install graph-cli locally with npm install -g @graphprotocol/graph-cli

4. Next you need to initialize your subgraph as this is probably your first time it is best to do that from example made by subgraph team so for the part where it says

graph init --from-example <GITHUB_USER>/<SUBGRAPH NAME> <DIRECTORY> we will run

graph init --from-example davekaj/example-subgraph

to copy from example and on next prompt add your subgraph name and local directory where it will go. This will install example code from Gravatar that is also used here in this video <https://www.youtube.com/watch?v=coa0Vw47qNc>

1. What you need to do after all this is to change your code to match the project you want to use, this is most difficult part.
   First you need to add abi for your project into /abis directory, so for example add Ren.json into that directory and add ABI you can find here on etherscan https://etherscan.io/address/0x408e41876cccdc0f92210600ef50372656052a38… just find your contract there and copy/paste ABI

2. Go into subgraph.yaml and change description and name under dataSources, address and abi under source, enteties, abis and eventHandlers under mapping. For me and REN contract it looks like this

   specVersion: 0.0.2
   description: Ren for Ethereum
   repository: https://github.com/graphprotocol/example-subgraph
   schema:
     file: ./schema.graphql
   dataSources:
     - kind: ethereum/contract
       name: Ren
       network: mainnet
       source:
         address: '0x408e41876cCCDC0F92210600ef50372656052a38'
         abi: Ren
         startBlock: 4827494
       mapping:
         kind: ethereum/events
         apiVersion: 0.0.4
         language: wasm/assemblyscript
         entities:
           - User
           - UserCounter
           - TransferCounter
           - TotalSupply
         abis:
           - name: Ren
             file: ./abis/Ren.json
         eventHandlers:
           - event: Transfer(indexed address,indexed address,uint256)
             handler: handleTransfer
         file: ./src/mapping.ts
   

3. So with this I changed subgraph yaml, what I need to change next is schema.graphql which needs to reflect info and enteties what you want to save to graph and consume later. So here we add entities that will be constructed or updated on our events.

4. How are we going to do all of this? We are going to borrow things a bit, as this is contract of ERC20 token and this are Standard ERC events, we will find some other ERC20 tokens and use their graph code to quickly solve our needs. So lets go to the https://github.com/centrehq/usdc-subgraph/blob/master/subgraph.yaml and use entities and eventHandlers that they use in their yaml. If you want more entities and events you can also check https://github.com/daostack/subgraph/blob/master/src/mappings/DAOToken/… and fetch those or find some other. Also best would be to code your own and not just copy but for learning purposes and first step, this is fine.

5. So we got subgraph yaml file ready but we need to setup our entites, so we can use it from this repo and set https://github.com/centrehq/usdc-subgraph/blob/master/schema.graphql so you will have this in your schema.graphql when you leave out mint and mintCounter as entities

   type User @entity {
     id: ID!
     address: String!
     balance: BigInt!
     transactionCount: Int!
   }
   
   type UserCounter @entity {
     id: ID!
     count: Int!
   }
   
   
   type TransferCounter @entity {
     id: ID!
     count: Int!
     totalTransferred: BigInt!
   }
   
   type TotalSupply @entity {
     id: ID!
     supply: BigInt!
     minted: BigInt!
     burned: BigInt!
   }
   

6. The last part we need to do is mappings, this will be a little harder as we cant just copy paste mappings from other subgraphs as they have their specific code https://github.com/centrehq/usdc-subgraph/blob/master/src/mapping.ts

   First thing we need to do is run graph codegen in terminal. This will generate an AssemblyScript class for every smart contract in the ABI files mentioned in subgraph.yaml, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. It will also generate a class for every contract event to provide easy access to event parameters as well as the block and transaction the event originated from. All of these types are written to <OUTPUT_DIR>/<DATA_SOURCE_NAME>/<ABI_NAME>.ts

   So unless we provide output dir it will be in default dir which is called "generated". In our example before it is not generated folder but types folder and then from there methods used in events are imported. So for our example we want to change those paths so we will change it to below

7. To have more knowledge on how to fill and manipulate data in your entities and mappings check the video from this specifi point https://youtu.be/e5OwjDao3MA?t=1556

   With that we can finally run again yarn codegen and deploy the code to subgraph, we will do this with this line. 4.1 First set the token with graph auth https://api.thegraph.com/deploy/ token is written on top of your dashboard. 4.2 Then you need to run this command to deploy the graph graph deploy -- debug \ - node https://api.thegraph.com/deploy/ \ - ipfs https://api.thegraph.com/ipfs/ \ <github / subgraph_name> which will be like below when proper parametars are added. graph deploy --debug --node https://api.thegraph.com/deploy/ --ipfs https://api.thegraph.com/ipfs/ adriadrop/ren-project If last line passes all the checks subgraph will be created and it will start to index data, if not you will get bunch of errors, probably some mappings will be wrong, maybe event wili miss some parameters or similar. For info how to debug this errors check here https://thegraph.com/docs/assemblyscript-api#logging-and-debugging

1. First login to the graph site with your github account, then go to Dashboard on the link here https://thegraph.com/explorer/dashboard and there you will have big button that says Add Subraph, click on it and fill the info needed to add subgraph.

2. After you add your boilerplate you will be provided with 3 additional step that you need to do.

3. so first install graph-cli locally with npm install -g @graphprotocol/graph-cli

4. Next you need to initialize your subgraph as this is probably your first time it is best to do that from example made by subgraph team so for the part where it says

graph init --from-example <GITHUB_USER>/<SUBGRAPH NAME> <DIRECTORY> we will run

graph init --from-example davekaj/example-subgraph

to copy from example and on next prompt add your subgraph name and local directory where it will go. This will install example code from Gravatar that is also used here in this video <https://www.youtube.com/watch?v=coa0Vw47qNc>

1. What you need to do after all this is to change your code to match the project you want to use, this is most difficult part.
   First you need to add abi for your project into /abis directory, so for example add Ren.json into that directory and add ABI you can find here on etherscan https://etherscan.io/address/0x408e41876cccdc0f92210600ef50372656052a38… just find your contract there and copy/paste ABI

2. Go into subgraph.yaml and change description and name under dataSources, address and abi under source, enteties, abis and eventHandlers under mapping. For me and REN contract it looks like this

   specVersion: 0.0.2
   description: Ren for Ethereum
   repository: https://github.com/graphprotocol/example-subgraph
   schema:
     file: ./schema.graphql
   dataSources:
     - kind: ethereum/contract
       name: Ren
       network: mainnet
       source:
         address: '0x408e41876cCCDC0F92210600ef50372656052a38'
         abi: Ren
         startBlock: 4827494
       mapping:
         kind: ethereum/events
         apiVersion: 0.0.4
         language: wasm/assemblyscript
         entities:
           - User
           - UserCounter
           - TransferCounter
           - TotalSupply
         abis:
           - name: Ren
             file: ./abis/Ren.json
         eventHandlers:
           - event: Transfer(indexed address,indexed address,uint256)
             handler: handleTransfer
         file: ./src/mapping.ts
   

3. So with this I changed subgraph yaml, what I need to change next is schema.graphql which needs to reflect info and enteties what you want to save to graph and consume later. So here we add entities that will be constructed or updated on our events.

4. How are we going to do all of this? We are going to borrow things a bit, as this is contract of ERC20 token and this are Standard ERC events, we will find some other ERC20 tokens and use their graph code to quickly solve our needs. So lets go to the https://github.com/centrehq/usdc-subgraph/blob/master/subgraph.yaml and use entities and eventHandlers that they use in their yaml. If you want more entities and events you can also check https://github.com/daostack/subgraph/blob/master/src/mappings/DAOToken/… and fetch those or find some other. Also best would be to code your own and not just copy but for learning purposes and first step, this is fine.

5. So we got subgraph yaml file ready but we need to setup our entites, so we can use it from this repo and set https://github.com/centrehq/usdc-subgraph/blob/master/schema.graphql so you will have this in your schema.graphql when you leave out mint and mintCounter as entities

   type User @entity {
     id: ID!
     address: String!
     balance: BigInt!
     transactionCount: Int!
   }
   
   type UserCounter @entity {
     id: ID!
     count: Int!
   }
   
   
   type TransferCounter @entity {
     id: ID!
     count: Int!
     totalTransferred: BigInt!
   }
   
   type TotalSupply @entity {
     id: ID!
     supply: BigInt!
     minted: BigInt!
     burned: BigInt!
   }
   

6. The last part we need to do is mappings, this will be a little harder as we cant just copy paste mappings from other subgraphs as they have their specific code https://github.com/centrehq/usdc-subgraph/blob/master/src/mapping.ts

   First thing we need to do is run graph codegen in terminal. This will generate an AssemblyScript class for every smart contract in the ABI files mentioned in subgraph.yaml, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. It will also generate a class for every contract event to provide easy access to event parameters as well as the block and transaction the event originated from. All of these types are written to <OUTPUT_DIR>/<DATA_SOURCE_NAME>/<ABI_NAME>.ts

   So unless we provide output dir it will be in default dir which is called "generated". In our example before it is not generated folder but types folder and then from there methods used in events are imported. So for our example we want to change those paths so we will change it to below

7. To have more knowledge on how to fill and manipulate data in your entities and mappings check the video from this specifi point https://youtu.be/e5OwjDao3MA?t=1556

   With that we can finally run again yarn codegen and deploy the code to subgraph, we will do this with this line. 4.1 First set the token with graph auth https://api.thegraph.com/deploy/ token is written on top of your dashboard. 4.2 Then you need to run this command to deploy the graph graph deploy -- debug \ - node https://api.thegraph.com/deploy/ \ - ipfs https://api.thegraph.com/ipfs/ \ <github / subgraph_name> which will be like below when proper parametars are added. graph deploy --debug --node https://api.thegraph.com/deploy/ --ipfs https://api.thegraph.com/ipfs/ adriadrop/ren-project If last line passes all the checks subgraph will be created and it will start to index data, if not you will get bunch of errors, probably some mappings will be wrong, maybe event wili miss some parameters or similar. For info how to debug this errors check here https://thegraph.com/docs/assemblyscript-api#logging-and-debugging