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
Reading data from blockchains requires processing smart contract events, parsing metadata from IPFS, and manually aggregating data.
20
19
21
-
The Graph supports [90+ blockchains](/supported-networks/), enhancing dapp development and data retrieval.
20
+
The result is slow performance, complex infrastructure, and scalability issues.
22
21
23
-
### Why is Blockchain Data Hard to Query?
22
+
##How The Graph Solves This
24
23
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.
24
+
The Graph uses a combination of cutting-edge research, core dev expertise, and independent Indexers to make blockchain data accessible for developers.
26
25
27
-
This is slow, complex, and resource-intensive.
26
+
Find the perfect data service for you:
28
27
29
-
## Solution
28
+
### 1. Custom Real-Time Data Streams
29
+
**Use Case:** High-frequency trading, live analytics
30
+
→ [Build Substreams](/substreams/introduction/)
31
+
→ [Browse Community Modules](https://substreams.dev/)
30
32
31
-
### How The Graph Solves This
33
+
### 2. Instant Token Data
34
+
**Use Case:** Wallet balances, liquidity pools, transfer events
35
+
→ [Start with Token API](/token-api/quick-start/)
32
36
33
-
The Graph simplifies the complex process of retrieving blockchain data through a global, decentralized network of Indexers that index Subgraphs. This infrastructure facilitates efficient, censorship-resistant query handling, allowing developers to build applications using blockchain data without the hassle of managing servers or custom indexing.
34
-
35
-
Each Subgraph defines:
36
-
37
-
- Which smart contracts to watch
38
-
- Which events to extract
39
-
- How to map event data into a queryable format using [GraphQL](https://graphql.org/learn/)
40
-
41
-
### [Building a Subgraph](/subgraphs/developing/creating/starting-your-subgraph/)
42
-
43
-
1. Define a [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) with data sources and mappings.
44
-
2. Use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) to deploy the manifest to IPFS.
45
-
3. An [Indexer](/indexing/overview/) picks it up and starts indexing Ethereum blocks.
46
-
4. Data becomes queryable via a [GraphQL endpoint](/subgraphs/querying/graphql-api/).
47
-
48
-
## Next Steps
49
-
50
-
Explore [Graph Explorer](https://thegraph.com/explorer) to view and query existing Subgraphs.
0 commit comments