Post-Sunrise + Upgrading to The Graph Network FAQ
Reading time: 4 min
Note: The Sunrise of Decentralized Data ended June 12th, 2024.
The Sunrise of Decentralized Data was an initiative spearheaded by Edge & Node. This initiative enabled subgraph developers to upgrade to The Graph’s decentralized network seamlessly.
This plan drew on previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs.
The hosted service query endpoints are no longer available, and developers cannot deploy new subgraphs on the hosted service.
During the upgrade process, owners of hosted service subgraphs could upgrade their subgraphs to The Graph Network. Additionally, developers were able to claim auto-upgraded subgraphs.
No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service.
The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the
The upgrade Indexer is currently active.
The upgrade Indexer was implemented to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and support new versions of existing subgraphs that had not yet been indexed.
- It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains .
- Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them.
Edge & Node historically maintained the hosted service and, as a result, already have synced data for hosted service subgraphs.
Chains previously only supported on the hosted service were made available to developers on The Graph Network without indexing rewards at first.
However, this action unlocked query fees for any interested Indexer and increased the number of subgraphs published on The Graph Network. As a result, Indexers have more opportunities to index and serve these subgraphs in exchange for query fees, even before indexing rewards are enabled for a chain.
The upgrade Indexer also provides the Indexer community with information about the potential demand for subgraphs and new chains on The Graph Network.
The upgrade Indexer offers a powerful opportunity for Delegators. As it allowed more subgraphs to be upgraded from the hosted service to The Graph Network, Delegators benefit from the increased network activity.
No, the upgrade Indexer only allocates the minimum amount per subgraph and does not collect indexing rewards.
It operates on an “as needed” basis, serving as a fallback until sufficient service quality is achieved by at least three other Indexers in the network for respective chains and subgraphs.
Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or , as no lead time was required for indexing. Please note that was not impacted by this upgrade.
The upgrade Indexer enables chains on the network that were previously only supported on the hosted service. Therefore, it widens the scope and availability of data that can be queried on the network.
The upgrade Indexer prices queries at the market rate to avoid influencing the query fee market.
The upgrade Indexer supports a subgraph until at least 3 other Indexers successfully and consistently serve queries made to it.
Furthermore, the upgrade Indexer stops supporting a subgraph if it has not been queried in the last 30 days.
Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it has a small allocation size, and other Indexers should be chosen for queries ahead of it.