The Graph nodes provided by Highbury is only a sandbox. The Graph admin endpoint is made public to allow anyone to be able to use it for testing. Projects should run their own Graph instances in production and avoid exposing the admin endpoint.
A hosted The Graph node is available to use on Fury EVM.
- JSON-RPC Admin (Deploy subgraphs): https://the-graph-admin.furya.io
- GraphQL HTTP Server (Query subgraphs): https://the-graph.furya.io
- Query Metrics: https://the-graph-metrics.furya.io/graphql
An example deployed subgraph is available for V2 Uniswap on Highbury EVM Testnet.
Write your subgraph
You can also use an example project like v2-uniswap.
Upgrade the manifest
network properties in the
subgraph.yaml manifest file.
The network name for Highbury EVM is
Create your subgraph
graph create <subgraph-name> --node https://the-graph-admin.furya.io
Deploy your subgraph
graph deploy <subgraph-name> --debug --ipfs https://api.thegraph.com/ipfs/ --node https://the-graph-admin.furya.io
Note that you can either use your own ipfs node here or
Once deployed, your graph should now be deployed and accessible via the GraphQL Server. It can be access at
A hosted The Graph node is available on Highbury EVM Testnet.
- JSON-RPC Admin (Deploy subgraphs): https://the-graph-admin.testnet.furya.io
- GraphQL HTTP Server (Query subgraphs): https://the-graph.testnet.furya.io
- Metrics GraphQL (Subgraph indexing status): https://the-graph-metrics.testnet.furya.io
network name for Highbury EVM Testnet is