Goldsky provides a one-step migration for your subgraphs on The Graph’s hosted service / decentralized network, or other subgraph host (including your own graph-node). This is a drop-in replacement with the following benefits:

  • The same subgraph API that your apps already use, allowing for seamless, zero-downtime migration
  • A load-balanced network of third-party and on-prem RPC nodes to improve performance and reliability
  • Tagging and versioning to hotswap subgraphs, allowing for seamless updates on your frontend
  • Alerts and auto-recovery in case of subgraph data consistency issues due to corruption from re-orgs or other issues
  • A world-class team who monitors your subgraphs 24/7, with on-call engineering support to help troubleshoot any issues

​
Migrate subgraphs to Goldsky

If you have subgraphs deployed to The Graph’s hosted service, the following command seamlessly migrates your subgraph to Goldsky:

goldsky subgraph deploy your-subgraph-name/your-version --from-url <your-subgraph-query-url>

If you have subgraphs deployed to The Graph’s decentralized network, use the IPFS hash instead (visible on The Graph’s Explorer page for the specified subgraph):

goldsky subgraph deploy your-subgraph-name/your-version --from-ipfs-hash <your-subgraph-ipfs-hash>

You can get this IPFS deployment hash by querying any subgraph GraphQL endpoint with the following query:

query {
  _meta {
    deployment
  }
}

​
Monitor indexing progress

Once you started the migration with the above command, you can monitor your subgraph’s indexing status with:

goldsky subgraph list

Alternatively, navigate to app.goldsky.com to see your subgraphs, their indexing progress, and more.