Skip to content

major edits #739

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Aug 9, 2024
Merged

major edits #739

merged 4 commits into from
Aug 9, 2024

Conversation

idalithb
Copy link
Contributor

@idalithb idalithb commented Aug 8, 2024

-reflecting changes & prepping for it to be archived

@idalithb idalithb requested a review from a team as a code owner August 8, 2024 23:02
---

> Note: This document is continually updated to ensure the most accurate and helpful information is provided. New questions and answers are added on a regular basis. If you can’t find the information you’re looking for, or if you require immediate assistance, [reach out on Discord](https://discord.gg/graphprotocol). If you are looking for billing information, then please refer to [billing](/billing/).
> Note: The Sunrise of Decentralization ended June 12th, 2024.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
> Note: The Sunrise of Decentralization ended June 12th, 2024.
> Note: The Sunrise of Decentralized Data ended June 12th, 2024.


This plan draws on many previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs, and the ability to integrate new blockchain networks to The Graph.
This plan drew on previous developments from The Graph ecosystem, including an upgraded Indexer to serve queries on newly published subgraphs.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This plan drew on previous developments from The Graph ecosystem, including an upgraded Indexer to serve queries on newly published subgraphs.
This plan drew on previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs.

This comment was marked as off-topic.

**Sunray**: Enable support for hosted service chains, introduce a seamless upgrade flow, offer a free plan on The Graph Network, and provide simple payment options.
**Sunbeam**: The upgrade window that subgraph developers will have to upgrade their hosted service subgraphs to The Graph Network. This window will end at 10 a.m. PT on June 12th 2024.
**Sunrise**: Hosted service endpoints will no longer be available after 10 a.m. PT on June 12th, 2024.
The hosted service query endpoints are no longer available, and developers cannot deploy new subgraph versions on the hosted service.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not just new versions, but new subgraphs too, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Both! So I'll just state it as "subgraphs"


### When will hosted service subgraphs no longer be available?
### Was Subgraph Studio be impacted by this upgrade?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### Was Subgraph Studio be impacted by this upgrade?
### Was Subgraph Studio impacted by this upgrade?


Hosted service query endpoints will remain active until 10 a.m. PT on June 12th. After June 12th at 10 a.m. PT, query endpoints will no longer be available, and developers will no longer be able to deploy new subgraph versions on the hosted service.
No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately available for querying, powered by the Upgraded Indexer, which used the same infrastructure as the hosted service.
Copy link
Contributor

@benface benface Aug 8, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately available for querying, powered by the Upgraded Indexer, which used the same infrastructure as the hosted service.
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.

### How can I get started querying subgraphs on The Graph Network?

You can explore available subgraphs on [Graph Explorer](https://thegraph.com/explorer). [Learn more about querying subgraphs on The Graph](/querying/querying-the-graph).
The Graph Network was initially deployed on the mainnet Ethereum but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, any new subgraphs were published on Arbitrum to The Graph Network so that Indexers could support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The Graph Network was initially deployed on the mainnet Ethereum but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, any new subgraphs were published on Arbitrum to The Graph Network so that Indexers could support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)
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, any 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 [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)

The upgrade Indexer is designed to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and to support new versions of existing subgraphs that have not yet been indexed.

The upgrade Indexer aims to bootstrap chains that don't have indexing rewards yet on The Graph Network and to serve as a fallback for new subgraph versions. The goal is to ensure that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
> The upgrade Indexer is currently active
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
> The upgrade Indexer is currently active
> The upgrade Indexer is currently active.


### What chains does the upgrade Indexer support?
The upgrade Indexer improved the experience of upgrading subgraphs from the hosted service to The Graph Network and supported new versions of existing subgraphs that had not yet been indexed.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The upgrade Indexer improved the experience of upgrading subgraphs from the hosted service to The Graph Network and supported new versions of existing subgraphs that had not yet been indexed.
The upgrade Indexer was deployed 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.

(not 100% sure about the term "deployed" here, I just don't think "improve" or "support" should be in the past tense)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"implemented"


### Should I host my own indexing infrastructure?
The upgrade Indexer offers a powerful opportunity for Delegators. As more subgraphs were upgraded from the hosted service to The Graph Network, Delegators benefited from the increased network activity.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The upgrade Indexer offers a powerful opportunity for Delegators. As more subgraphs were upgraded from the hosted service to The Graph Network, Delegators benefited from the increased network activity.
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.


Running infrastructure for your own project is [significantly more resource intensive](/network/benefits/) when compared to using The Graph Network.
### Did the Upgrade Indexer compete with existing Indexers for rewards?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### Did the Upgrade Indexer compete with existing Indexers for rewards?
### Did the upgrade Indexer compete with existing Indexers for rewards?

Comment on lines 61 to 63
### How does this affect subgraph developers?

If you are building in web3, the moment you use a centralized indexing provider, you are giving them control of your dapp and data. The Graph’s decentralized network offers [superior quality of service](https://thegraph.com/blog/qos-the-graph-network/), reliability with unbeatable uptime thanks to node redundancy, significantly [lower costs](/network/benefits/), and keeps you from being hostage at the data layer.
Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or publishing from Subgraph Studio, as no lead time was required for indexing.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure this question/answer is useful as is. Maybe it would be better to explain the differences in deploying/publishing new subgraph versions between hosted service and Subgraph Studio? And also highlight what didn't change: how to develop subgraphs itself (e.g. subgraph manifest, schema, mappings, etc.) should be exactly the same, as far as I know.


Additionally, Subgraph Studio provides 100,000 free monthly queries on the Free Plan, before payment is needed for additional usage.
The upgraded Indexer enabled chains on the network that were previously only supported on the hosted service. Therefore, it widened the scope and availability of data that could be queried on the network.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The upgraded Indexer enabled chains on the network that were previously only supported on the hosted service. Therefore, it widened the scope and availability of data that could be queried on the network.
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.


With The Graph Network, your subgraph is public and anyone can query it openly, which increases the usage and network effects of your dapp.
### How did this benefit data consumers?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### How did this benefit data consumers?
### How did Sunrise benefit data consumers?

(just to justify keeping it in the past tense, but if "this" is the upgrade Indexer, I think it should be in the present)


Here's a detailed breakdown of the benefits of The Graph over centralized hosting:
### How did the upgrade Indexer price queries?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### How did the upgrade Indexer price queries?
### How does the upgrade Indexer price queries?


- **Resilience and Redundancy**: Decentralized systems are inherently more robust and resilient due to their distributed nature. Data isn't stored on a single server or location. Instead, it's served by hundreds of independent Indexers around the globe. This reduces the risk of data loss or service interruptions if one node fails, leading to exceptional uptime (99.99%).
The Indexer upgraded its pricing model to align with market rates in order to avoid influencing the query fee market.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The Indexer upgraded its pricing model to align with market rates in order to avoid influencing the query fee market.
The upgrade Indexer prices queries at the market rate to avoid influencing the query fee market.


Just as you've chosen your blockchain network for its decentralized nature, security, and transparency, opting for The Graph Network is an extension of those same principles. By aligning your data infrastructure with these values, you ensure a cohesive, resilient, and trust-driven development environment.
Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer trended towards zero, as it has a small allocation size, and other Indexers were chosen for queries ahead of it.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer trended towards zero, as it has a small allocation size, and other Indexers were chosen for queries ahead of it.
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.

### How can I get started querying subgraphs on The Graph Network?

You can explore available subgraphs on [Graph Explorer](https://thegraph.com/explorer). [Learn more about querying subgraphs on The Graph](/querying/querying-the-graph).
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, any 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 [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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, any 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 [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)
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, any 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 [supported networks](/developing/supported-networks/)


No, the upgrade Indexer will only allocate the minimum amount per subgraph and will not collect indexing rewards.
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 were enabled for a chain.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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 were enabled for a chain.
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.


If you are building in web3, the moment you use a centralized indexing provider, you are giving them control of your dapp and data. The Graph’s decentralized network offers [superior quality of service](https://thegraph.com/blog/qos-the-graph-network/), reliability with unbeatable uptime thanks to node redundancy, significantly [lower costs](/network/benefits/), and keeps you from being hostage at the data layer.
Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](https://thegraph.com/docs/en/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](https://thegraph.com/docs/en/developing/creating-a-subgraph) was not impacted by this upgrade.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](https://thegraph.com/docs/en/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](https://thegraph.com/docs/en/developing/creating-a-subgraph) was not impacted by this upgrade.
Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](https://thegraph.com/docs/en/publishing/publishing-a-subgraph/). Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade.

Relative URLs are better, otherwise translations link to English content. 🙏


Additionally, Subgraph Studio provides 100,000 free monthly queries on the Free Plan, before payment is needed for additional usage.
The upgraded 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The upgraded 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 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.


- **Censorship Resistance**: Centralized systems are targets for censorship, either through regulatory pressures or network attacks. In contrast, the dispersed architecture of decentralized systems makes them much harder to censor, which ensures continuous data availability.
The upgrade Indexer serves a subgraph until it is sufficiently and successfully served with consistent queries served by at least 3 other Indexers.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, repeating the word "served" sounds like a potential mistake?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe this is what we mean?

Suggested change
The upgrade Indexer serves a subgraph until it is sufficiently and successfully served with consistent queries served by at least 3 other Indexers.
The upgrade Indexer supports a subgraph until at least 3 other Indexers successfully and consistently serve queries made to it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would be fair to state "The upgrade Indexer serves a subgraph until it is sufficiently and successfully supported with consistent queries by at least 3 other Indexers"

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, not sure what "successfully supported" means. IMO, the "success" aspect refers to query success rate.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also feel like "supports a subgraph" is more correct than "serves a subgraph". An Indexer serves queries made to a subgraph, not a subgraph itself, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

correct!

Copy link
Contributor

@benface benface left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🙌

@idalithb idalithb merged commit 0fef8c1 into main Aug 9, 2024
6 checks passed
@idalithb idalithb deleted the post-sunrise-edit branch August 9, 2024 20:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants