Skip to content

Commit 23f190e

Browse files
Initial edits
1 parent 4a4c3ae commit 23f190e

File tree

1 file changed

+13
-18
lines changed

1 file changed

+13
-18
lines changed

website/src/pages/en/about.mdx

Lines changed: 13 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -7,13 +7,24 @@ description: This page summarizes the core concepts and basics of The Graph Netw
77

88
### What is The Graph?
99

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:
17+
18+
- [Graph Explorer](/subgraphs/explorer/)
19+
- [Subgraph Studio](/subgraphs/developing/deploying/using-subgraph-studio/)
1120

1221
The Graph supports [90+ blockchains](/supported-networks/), enhancing dapp development and data retrieval.
1322

1423
### Why is Blockchain Data Hard to Query?
1524

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.
1728

1829
## Solution
1930

@@ -34,22 +45,6 @@ Each Subgraph defines:
3445
3. An [Indexer](/indexing/overview/) picks it up and starts indexing Ethereum blocks.
3546
4. Data becomes queryable via a [GraphQL endpoint](/subgraphs/querying/graphql-api/).
3647

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-
![A graphic explaining how The Graph uses Graph Node to serve queries to data consumers](/img/graph-dataflow.png)
52-
5348
## Next Steps
5449

5550
Explore [Graph Explorer](https://thegraph.com/explorer) to view and query existing Subgraphs.

0 commit comments

Comments
 (0)