Skip to main content
Goldsky provides a one-step migration for your subgraphs on TheGraph’s decentralized network. 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

  1. Install the Goldsky CLI: For macOS/Linux: 
    curl https://goldsky.com | sh
    For Windows: 
    npm install -g @goldskycom/cli
    Windows users need to have Node.js and npm installed first. Download from nodejs.org if not already installed.
  2. Go to your Project Settings page and create an API key.
  3. Back in your Goldsky CLI, log into your Project by running the command goldsky login and paste your API key.
  4. Now that you are logged in, run goldsky to get started: 
    goldsky
Use the following command to seamlessly migrate your subgraph to Goldsky via IPFS hash(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 alo 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.
⌘I