Skip to main content

Migrating from GoldSky Subgraphs to Bitquery

Subgraphs require you to define a schema, write mappings, and deploy an indexer per protocol. Bitquery gives you prebuilt, decoded cross-chain cubes you query directly — no subgraph to author or operate.

note

Verify chain/cube coverage in the coverage matrix.

Concept mapping​

GoldSky / subgraphBitquery
Define GraphQL schema + mappingsPrebuilt cubes — no schema authoring
Deploy & sync a subgraphNothing to deploy; query immediately
Entity queriesCube queries (EVM { ... }, Solana { ... }, Trading { ... })
Subgraph webhooks / streamsWebSocket / Kafka / gRPC
Custom protocol decodingAsk support to index a protocol's ABIs/IDL

Example: pair-creation events (a common subgraph use case)​

{
  EVM(network: eth, dataset: combined) {
    Events(
      where: { Log: { Signature: { Name: { is: "PairCreated" } } } }
      orderBy: { descending: Block_Time }
      limit: { count: 100 }
    ) {
      Block { Time }
      Log { Signature { Name } SmartContract }
      Transaction { Hash }
    }
  }
}

What differs​

  • No indexer to run. You skip subgraph authoring, deployment, and re-syncs.
  • Cross-chain in one place. The same query shapes span supported chains.
  • Rate limits & cost are point-based rather than per-subgraph — see How Billing Works.
  • Custom protocols. If a protocol isn't decoded yet, ask support to index its ABIs/IDL.

Frequently Asked Questions

Do I need to deploy a subgraph with Bitquery?

No. Bitquery provides prebuilt decoded cubes you query directly — there's no subgraph schema, mapping, or indexer to deploy or sync.

How do I track pair-creation or custom events?

Use the Events cube filtered by event signature. For a protocol that isn't decoded yet, ask support to index its ABIs/IDL.

How is pricing different from subgraphs?

Bitquery bills by API points rather than per-subgraph hosting. See How Billing Works.

Next steps​