<aside> ❗ This page has been shared publicly

</aside>

Motivated by forum post: https://forum.thegraph.com/t/n-1-to-n-solution-staging-version/3735

When developers deploys a new version of subgraph deployment, they can give indexers a heads up that there will soon be an upgrade of the subgraph. This allows indexers to start indexing the new subgraph deployment before there is query demand.

For the developer, they gain a better control and support for when they can utilize the new version.

For the indexers, they can seamlessly transition into the upgraded deployment.

statusEndpointMessage identifier as subgraph deployment hash, content includes the indexer’s public status API endpoint. This should already be public and verifiable

stagingVersionMessage identifier must be old version subgraph deployment hash as it is known and subscribed by indexers, content includes new subgraph deployment hash and potentially the time they plan to deploy


Github issues