Skip to content

Conversation

@LookingForOwls
Copy link

The existing strategy was failing to find our subgraph when querying from the subgrapher.snapshot.org api endpoint.

Updated to directly use the subgraph url and accept and api key.

If there is a better way to handle this please let me know.

Tests pass when apiKey is provided.

@ChaituVR ChaituVR changed the title [wagdie] fix the subgraph url and handle api key [wagdie-subgraph] fix the subgraph url and handle api key Oct 8, 2025
import { subgraphRequest } from '../../utils';

const SUBGRAPH_URL = {
'1': 'https://subgrapher.snapshot.org/subgraph/arbitrum/CiuchCqNbcNs88KkbQqs7PwuaD2DrPqHqxuDVKrJ5ESM'
Copy link
Member

Choose a reason for hiding this comment

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

Hi @LookingForOwls it should work with this URL, i think the real problem is that this subgraph doesn't support historical queries, if you are are the owner of the subgraph, you'd need to redeploy with prune: never

Copy link
Author

Choose a reason for hiding this comment

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

Ok will test this out. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants