Cowrie Research

goldsky-primary-sources-2026-04-23

3 min read

Goldsky primary-source snapshot

Fetched: 2026-04-23 UTC

1) Official site overview

Source: https://goldsky.com/

Selected excerpts from the official site:

The modern back-end for crypto-enabled products

Stream blockchain data directly into your sink of choice in real time.

One RPC endpoint for live and archive access to EVM chains.

Additional signals from the homepage:

  • Goldsky is presented as an infrastructure backend, not as an app or token-centric protocol
  • The product stack spans streaming pipelines, subgraphs, and RPC rather than a single indexing primitive
  • The homepage emphasizes production readiness, chain breadth, and enterprise-like reliability more than community/governance narratives

2) Docs introduction

Source: https://docs.goldsky.com/introduction.md

Selected excerpts from the docs introduction:

Goldsky is the modern back-end for crypto-enabled products.

Subgraphs — Instant GraphQL APIs with zero maintenance.

Mirror — Stream realtime data directly into your database.

Additional signals from this page:

  • The docs introduce Goldsky as a multi-product platform: Subgraphs, Mirror, Turbo, Edge RPC, and Compose
  • The product framing is useful for categorizing Goldsky under data/backend infra rather than only indexing
  • The docs structure is mature enough to serve as a primary source of truth even without a whitepaper

3) Mirror

Source: https://docs.goldsky.com/mirror/introduction

Selected excerpts from the Mirror docs:

Mirror streams onchain data directly to your database, with <1s latency.

Behind the scenes, Mirror automatically creates and runs data pipelines for you off a .yaml config file.

Pipelines are reorg-aware and update your datastores with the latest information.

Additional signals from this page:

  • Mirror is designed for teams that want blockchain data in their own operational database rather than only through hosted query endpoints
  • The docs stress backfills, reorg handling, and pipeline automation, which are central operational details for serious indexing infrastructure
  • Mirror’s chain-support claims are product-specific and should be read in that narrower context

4) Edge RPC

Source: https://docs.goldsky.com/edge-rpc/introduction

Selected excerpts from the Edge RPC docs:

High-performance RPC endpoints for EVM networks

Edge RPC provides reliable, high-performance RPC access with low latency via multi-region CDN, intelligent caching, automatic failover, and built-in observability.

Edge RPC is built on top of eRPC, an open source RPC proxy.

Additional signals from this page:

  • Goldsky is not only an indexing company; it also sells operational RPC access as part of the same backend stack
  • The docs emphasize failover, cross-validation, archive access, and indexer/front-end performance tuning
  • Partner logos on the page suggest usage among recognizable crypto applications, but those should still be treated as vendor-presented references

5) Docs index / llms.txt

Source: https://docs.goldsky.com/llms.txt

Selected excerpts from the docs index:

AI Skills

Supported networks

Overview

Additional signals from this page:

  • Goldsky exposes a rich llms.txt index that makes the documentation especially discoverable and machine-readable
  • The breadth of chain pages and API references reinforces that the docs are a primary research surface in their own right
  • This makes Goldsky a strong example of the “docs-first” crypto infra companies worth cataloging even without a canonical whitepaper

Notes

  • This pass did not locate a classic whitepaper or litepaper from official Goldsky sources.
  • The strongest primary materials were the official site, product docs, and machine-readable docs index.
  • Goldsky is worth cataloging because it occupies an important but sometimes under-cataloged layer of the ecosystem: data pipelines, indexing, and RPC infrastructure used by crypto apps and analytics systems.
  • Scale metrics, latency claims, chain counts, and customer references should still be treated as vendor claims unless independently verified.

Graph View