-
Notifications
You must be signed in to change notification settings - Fork 13
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
Subgraph endpoint update required #52
Comments
@alex-pakalniskis does this mean I have to create my own endpoint to query with allocation optimizer, or will a new endpoint be provided eventually? If I need to create my own endpoint I would appreciate a guide specific for allocation-optimizer, so I can continue reallocating. |
I think I have it figured out, I set The subgraph I used is |
Yes that looks good to me. Glad it worked (I expected it to be plug-and-play replace old url with new one including API key). Let us know if you run into any issues (we'll update the docs for this repo). |
@alex-pakalniskis actually I ran into additional issues trying to reallocate. I have the following settings for the indexer-agent: arbitrumNetwork: arbitrum-one
arbitrumGateway: "https://gateway-arbitrum.network.thegraph.com"
arbitrumSubgraphEndpoint: "https://api.thegraph.com/subgraphs/name/graphprotocol/graph-network-arbitrum"
arbitrumEpochEndpoint: "https://api.thegraph.com/subgraphs/name/graphprotocol/arbitrum-epoch-block-oracle" Do any of these need to be also updated? When trying to close allocations today I ran into https://github.com/graphprotocol/indexer/blob/main/docs/errors.md#ie069 for all of them |
Hey team,
We've noticed that you're referencing a subgraph deployed on The Graph's hosted service in this repository. Just a heads-up: after June 12th, hosted service subgraph endpoints will no longer be available as the offering is being deprecated.
If you are the subgraph owner or maintainer, it's time to upgrade your subgraph to the network. This ensures everything keeps running smoothly and you get access to all the latest features and improvements. Here is a quick guide with all the upgrade steps.
If you're not the subgraph owner or maintainer, check Graph Explorer to see if the subgraph development team has already upgraded to the network. If you don’t find an upgraded subgraph, a friendly nudge to the subgraph development team would be greatly appreciated—it's a quick process that benefits everyone. Here's the upgrade guide with all the necessary steps for the subgraph development team.
Once the subgraph is upgraded to the network, you can create an API key and updated query URL in Subgraph Studio then update this repository to query from the new endpoint,
https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
Need more support or have more questions? Feel free to reach out to [email protected]. We're here to help!
Cheers,
Paka
The text was updated successfully, but these errors were encountered: