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/src/pages/en/about.mdx
+13-18Lines changed: 13 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,13 +7,24 @@ description: This page summarizes the core concepts and basics of The Graph Netw
7
7
8
8
### What is The Graph?
9
9
10
-
The Graph is a decentralized protocol for indexing and querying blockchain data. Its suite includes [Subgraphs](/subgraphs/developing/subgraphs/), [Substreams](/substreams/introduction/), [Token API BETA](/token-api/quick-start/), and tools like [Graph Explorer](/subgraphs/explorer/) and [Subgraph Studio](/subgraphs/developing/deploying/using-subgraph-studio/).
10
+
The Graph is a decentralized protocol for indexing and querying blockchain data. Its data services include:
11
+
12
+
-[Subgraphs](/subgraphs/developing/subgraphs/)
13
+
-[Substreams](/substreams/introduction/)
14
+
-[Token API Beta](/token-api/quick-start/)
15
+
16
+
The ecosystem maintains additional tooling that includes:
The Graph supports [90+ blockchains](/supported-networks/), enhancing dapp development and data retrieval.
13
22
14
23
### Why is Blockchain Data Hard to Query?
15
24
16
-
Reading onchain data from the blockchain (e.g., ownership history, metadata, relationships between assets) typically requires processing smart contract events, parsing metadata from IPFS, and aggregating data manually. This is very slow, complex, and resource-intensive.
25
+
Reading data from blockchains (e.g., ownership history, metadata, relationships between assets) often requires processing smart contract events, parsing metadata from IPFS, and manually aggregating data.
26
+
27
+
This is slow, complex, and resource-intensive.
17
28
18
29
## Solution
19
30
@@ -34,22 +45,6 @@ Each Subgraph defines:
34
45
3. An [Indexer](/indexing/overview/) picks it up and starts indexing Ethereum blocks.
35
46
4. Data becomes queryable via a [GraphQL endpoint](/subgraphs/querying/graphql-api/).
36
47
37
-
### Data Flow Overview
38
-
39
-
1. A dapp triggers a transaction on Ethereum by interacting with a smart contract.
40
-
41
-
2. As the transaction is processed, the smart contract emits one or more events.
42
-
43
-
3.[Graph Node](/indexing/tooling/graph-node/) continuously scans the Ethereum blockchain for new blocks and filters for events relevant to a deployed Subgraph.
44
-
45
-
4. When a matching event is identified, Graph Node executes the Subgraph’s mapping logic, which is a WASM module that transforms event data into structured entities. These entities are subsequently stored and indexed.
46
-
47
-
5. The dapp queries the Graph Node via a [GraphQL API](https://graphql.org/learn/), retrieving indexed data to render in the UI. Users can then take actions that generate new transactions, continuing the cycle.
48
-
49
-
The diagram below provides more detailed information about the flow of data after a Subgraph manifest has been deployed with Ethereum transactions.
50
-
51
-

52
-
53
48
## Next Steps
54
49
55
50
Explore [Graph Explorer](https://thegraph.com/explorer) to view and query existing Subgraphs.
0 commit comments