Subgraph Manifest: Data Indexing in The Graph
Subgraph Manifest is the file that defines how a particular image is mapped from the Ethereum network to The Graph. The Subgraph application contains information about Subgraph data sources, patterns, and more.
What is a Subgraph Manifest?
The Subgraph manifest is a file that defines how a particular image is mapped from the Ethereum network to The Graph.
It is written in YAML and contains the following fields: Name: The name of the subgraph; Description: A brief description of what the subgraph represents. It will appear as an image in the explorer user interface to help users get an idea of what they are looking at; Data Sources: An array of data source identifiers pointing to specific Ethereum networks or smart contract addresses. Here we define which smartcontracts will contribute data to this subgraph, what specific events they produce, and how those events map to the GraphQL schema defined elsewhere in this manifest.
The subgraph manifest is a structure that allows you to specify the entities, relationships, and indexes needed for the graph. The Graph CLI is used by dApp developers to deploy the subgraph, and by dApp developers on The Graph during queries.
It is used as a protocol to create DappS more quickly using GraphQL. These DappS are mostly built on Ethereum and IPFC.
Typically, the subgraphs are open-source data schemas to define how the application should store data in a centralized Graph Node information base. Manifest text is written in the GraphL SDl language and is used by nodes to create indexes of the entire blockchain and its smart contract.
The Graph consists of subgraphs that describe the data requirements for the application. To create more complex applications, the subgraphs can be composed together. The subgraphs have a single manifest that describes the data requirements of the subgraphs along with other subject metadata.