You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: website/pages/en/developing/developer-faqs.mdx
+74-60
Original file line number
Diff line number
Diff line change
@@ -2,68 +2,93 @@
2
2
title: Developer FAQs
3
3
---
4
4
5
-
## 1. What is a subgraph?
5
+
This page summarizes some of the most common questions for developers building on The Graph.
6
6
7
-
A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using the Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available to be queried by subgraph consumers.
7
+
## Subgraph Related
8
8
9
-
##2. Can I delete my subgraph?
9
+
### 1. What is a subgraph?
10
10
11
-
It is not possible to delete subgraphs once they are created.
11
+
A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using The Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available for subgraph consumers to query.
12
12
13
-
##3. Can I change my subgraph name?
13
+
### 2. What is the first step to create a subgraph?
14
14
15
-
No. Once a subgraph is created, the name cannot be changed. Make sure to think of this carefully before you create your subgraph so it is easily searchable and identifiable by other dapps.
15
+
To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/).
16
16
17
-
##4. Can I change the GitHub account associated with my subgraph?
17
+
### 3. Can I still create a subgraph if my smart contracts don't have events?
18
18
19
-
No. Once a subgraph is created, the associated GitHub account cannot be changed. Make sure to think of this carefully before you create your subgraph.
19
+
It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are the fastest way to retrieve useful data.
20
20
21
-
## 5. Am I still able to create a subgraph if my smart contracts don't have events?
21
+
If the contracts you work with do not contain events, your subgraph can use call and block handlers to trigger indexing. However, this is not recommended, as performance will be significantly slower.
22
22
23
-
It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are by far the fastest way to retrieve useful data.
23
+
### 4. Can I change the GitHub account associated with my subgraph?
24
24
25
-
If the contracts you are working with do not contain events, your subgraph can use call and block handlers to trigger indexing. Although this is not recommended, as performance will be significantly slower.
25
+
No. Once a subgraph is created, the associated GitHub account cannot be changed. Please make sure to carefully consider this before creating your subgraph.
26
26
27
-
##6. How are templates different from data sources?
27
+
### 5. How do I update a subgraph on mainnet?
28
28
29
-
Templates allow you to create data sources on the fly, while your subgraph is indexing. It might be the case that your contract will spawn new contracts as people interact with it, and since you know the shape of those contracts (ABI, events, etc) upfront you can define how you want to index them in a template and when they are spawned your subgraph will create a dynamic data source by supplying the contract address.
29
+
You can deploy a new version of your subgraph to Subgraph Studio using the CLI. This action maintains your subgraph private, but once you’re happy with it, you can publish to Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
30
+
31
+
### 6. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
32
+
33
+
You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't change, it won't have to sync from the beginning.
34
+
35
+
### 7. How do I call a contract function or access a public state variable from my subgraph mappings?
36
+
37
+
Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
38
+
39
+
### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings?
40
+
41
+
Not currently, as mappings are written in AssemblyScript.
42
+
43
+
One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
44
+
45
+
### 9. When listening to multiple contracts, is it possible to select the contract order to listen to events?
46
+
47
+
Within a subgraph, the events are always processed in the order they appear in the blocks, regardless of whether that is across multiple contracts or not.
48
+
49
+
### 10. How are templates different from data sources?
50
+
51
+
Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address.
30
52
31
53
Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates).
32
54
33
-
##7. How do I make sure I'm using the latest version of graph-node for my local deployments?
55
+
### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`?
34
56
35
-
You can run the following command:
57
+
Yes. On `graph init` command itself you can add multiple dataSources by entering contracts one after the other.
36
58
37
-
```sh
38
-
docker pull graphprotocol/graph-node:latest
39
-
```
59
+
You can also use `graph add` command to add a new dataSource.
40
60
41
-
**NOTE:** docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so it is important to do this to make sure you are up to date with the latest version of graph-node.
61
+
### 12. In what order are the event, block, and call handlers triggered for a data source?
42
62
43
-
## 8. How do I call a contract function or access a public state variable from my subgraph mappings?
63
+
Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
44
64
45
-
Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
65
+
When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
46
66
47
-
##9. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another datasource in `subgraph.yaml` after running `graph init`?
67
+
### 13. How do I make sure I'm using the latest version of graph-node for my local deployments?
48
68
49
-
Yes. On `graph init` command itself you can add multiple datasources by entering contracts one after the other. You can also use `graph add`command to add new datasource.
69
+
You can run the following command:
50
70
51
-
## 10. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
> Note: docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so make sure you're up to date with the latest version of graph-node.
57
76
58
-
##11. What is the recommended way to build "autogenerated" ids for an entity when handling events?
77
+
### 14. What is the recommended way to build "autogenerated" ids for an entity when handling events?
59
78
60
79
If only one entity is created during the event and if there's nothing better available, then the transaction hash + log index would be unique. You can obfuscate these by converting that to Bytes and then piping it through `crypto.keccak256` but this won't make it more unique.
61
80
62
-
##12. When listening to multiple contracts, is it possible to select the contract order to listen to events?
81
+
### 15. Can I delete my subgraph?
63
82
64
-
Within a subgraph, the events are always processed in the order they appear in the blocks, regardless of whether that is across multiple contracts or not.
83
+
It is not possible to delete subgraphs once they are created. However, you can [transfer and deprecate your subgraph](/managing/transfer-and-deprecate-a-subgraph/).
84
+
85
+
## Network Related
65
86
66
-
## 13. Is it possible to differentiate between networks (mainnet, Sepolia, local) from within event handlers?
87
+
### 16. What networks are supported by The Graph?
88
+
89
+
You can find the list of the supported networks [here](/developing/supported-networks).
90
+
91
+
### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers?
67
92
68
93
Yes. You can do this by importing `graph-ts` as per the example below:
69
94
@@ -74,60 +99,49 @@ dataSource.network()
74
99
dataSource.address()
75
100
```
76
101
77
-
##14. Do you support block and call handlers on Sepolia?
102
+
### 18. Do you support block and call handlers on Sepolia?
78
103
79
104
Yes. Sepolia supports block handlers, call handlers and event handlers. It should be noted that event handlers are far more performant than the other two handlers, and they are supported on every EVM-compatible network.
80
105
81
-
## 15. Can I import ethers.js or other JS libraries into my subgraph mappings?
106
+
## Indexing & Querying Related
82
107
83
-
Not currently, as mappings are written in AssemblyScript. One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
108
+
### 19. Is it possible to specify what block to start indexing on?
84
109
85
-
## 16. Is it possible to specify what block to start indexing on?
110
+
Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
86
111
87
-
Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
112
+
### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
88
113
89
-
## 17. Are there some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
114
+
Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
90
115
91
-
Yes, you should take a look at the optional start block feature to start indexing from the block that the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
92
-
93
-
## 18. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
116
+
### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
94
117
95
118
Yes! Try the following command, substituting "organization/subgraphName" with the organization under it is published and the name of your subgraph:
96
119
97
120
```sh
98
121
curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"organization/subgraphName\") { chains { latestBlock { hash number }}}}"}' https://api.thegraph.com/index-node/graphql
99
122
```
100
123
101
-
## 19. What networks are supported by The Graph?
102
-
103
-
You can find the list of the supported networks [here](/developing/supported-networks).
104
-
105
-
## 20. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
106
-
107
-
You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't change, it won't have to sync from the beginning.
108
-
109
-
## 21. Is this possible to use Apollo Federation on top of graph-node?
110
-
111
-
Federation is not supported yet, although we do want to support it in the future. At the moment, something you can do is use schema stitching, either on the client or via a proxy service.
112
-
113
-
## 22. Is there a limit to how many objects The Graph can return per query?
124
+
### 22. Is there a limit to how many objects The Graph can return per query?
114
125
115
126
By default, query responses are limited to 100 items per collection. If you want to receive more, you can go up to 1000 items per collection and beyond that, you can paginate with:
## 23. If my dapp frontend uses The Graph for querying, do I need to write my query key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
132
+
###23. If my dapp frontend uses The Graph for querying, do I need to write my query key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
122
133
123
134
Currently, the recommended approach for a dapp is to add the key to the frontend and expose it to end users. That said, you can limit that key to a hostname, like _yourdapp.io_ and subgraph. The gateway is currently being run by Edge & Node. Part of the responsibility of a gateway is to monitor for abusive behavior and block traffic from malicious clients.
124
135
125
-
## 24. How do I update a subgraph on mainnet?
136
+
## Miscellaneous
126
137
127
-
If you’re a subgraph developer, you can deploy a new version of your subgraph to Subgraph Studio using the CLI. It’ll be private at that point, but if you’re happy with it, you can publish to the decentralized Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
138
+
### 24. Is it possible to use Apollo Federation on top of graph-node?
128
139
129
-
## 25. In what order are the event, block, and call handlers triggered for a data source?
140
+
Federation is not supported yet. At the moment, you can use schema stitching, either on the client or via a proxy service.
130
141
131
-
Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
142
+
### 25. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
132
143
133
-
When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
0 commit comments