Subsquid

About Subsquid (SQD)

What Is Subsquid (SQD)?

Subsquid, branded by the project as SQD, is a decentralized data lake and query engine for blockchain data. It ingests, verifies and stores historical and real-time onchain data from a large set of networks, then streams it to applications over HTTP so teams need not run archive nodes. Storage and serving are spread across independently operated worker nodes, positioning it against centralized RPC and indexing providers. SQD is an ERC-20 token on Arbitrum One, Base and BNB Chain.

Official resources:

• Website: https://sqd.dev
• Documentation: https://docs.sqd.dev
• Network docs: https://docs.sqd.dev/en/network/overview
• GitHub: https://github.com/subsquid
• Arbitrum One contract: https://arbiscan.io/token/0x1337420dED5ADb9980CFc35f8f2B054ea86f8aB1

Who Founded Subsquid? (History)

Subsquid was founded by Dmitry Zhelezov and Marcel Fohrmann in 2021, with Subsquid Labs GmbH as the operating company. Zhelezov, a mathematics PhD and former Substrate core developer, has described the idea as growing out of a hackathon prototype. Project and press records show a seed round in late 2021 led by Hypersphere Ventures and the token launch in May 2024. In June 2026 it announced a repositioning toward institutional clients, naming Wanja S. Oberhof chief executive.

How Subsquid Works

Data from each chain is ingested, normalized and written as columnar Parquet chunks, which a scheduler distributes across many worker nodes with heavy replication. A Portal then accepts a query over an arbitrary block range, pulls chunks from many workers in parallel, and streams results back, handling pagination, finality tracking and reorg compensation. The documentation describes correctness as enforced at ingestion by cryptographic checks such as multi-RPC cross-verification and state root comparison.

Key Ecosystem Components

• SQD Network: worker nodes holding Parquet chunks and answering queries in parallel.
• Portal: the gateway that fans requests out to workers and handles finality and reorgs.
• SDK: TypeScript libraries, historically Squid SDK and now Pipes SDK, for decoding and persisting data into your own database.
• SQD Cloud: managed hosting for indexers.

SQD Token Utility

SQD meters and secures participation rather than billing end users per query. Rewards are paid onchain for uptime, data served and validation work. Running a worker requires bonding SQD, published as 100,000 SQD, with slashing for provable violations, and holders can delegate to specific workers to share those rewards. Portal operators lock SQD against an onchain identity, with query bandwidth allocated in proportion to the lock.

What Makes Subsquid Unique?

The distinguishing choice is architectural: instead of each indexer re-reading a chain through an RPC endpoint, SQD ingests each chain once into a compressed columnar dataset that many consumers read slices of in parallel. Columnar storage suits the filtered scans indexing workloads perform, and throughput scales with network size rather than one provider.

How Subsquid Differs from Similar Projects

The Graph is the closest comparison. Its model centers on subgraphs that indexers run and consumers query in GraphQL, whereas SQD streams raw verified data and leaves transformation to the developer, suiting teams that want data in their own database. Oracle networks such as Chainlink and Pyth push a few attested values onchain rather than serving bulk history, and storage networks such as Filecoin are general file stores.

Use Cases of Subsquid

• Building indexers and app backends without operating archive nodes.
• Powering dashboards, trackers and explorers needing deep historical scans.
• Feeding trading, risk and compliance systems needing reproducible history.
• Supplying structured onchain context to AI agents and research pipelines.

How Subsquid Is Secured

Integrity is addressed at ingestion by the checks above, so a worker cannot silently serve altered history. Accountability comes from bonding, since workers place SQD at risk and can be slashed. Availability comes from replication, since each chunk sits with many independent workers and the Portal routes around unresponsive ones.

Risks and Considerations

Worker economics depend on demand for data; if query volume does not grow, operator rewards come mainly from emissions, a common sustainability question for this category. Bonding and delegation lock tokens and carry slashing and operator-performance risk. The 2026 institutional repositioning is a real strategy change worth tracking in current project communications.

Why Subsquid Matters

Nearly every crypto application showing a balance, chart or history reads indexed data rather than the chain directly, and that layer sits with a few centralized providers. A network storing verified history redundantly across independent operators addresses a concrete concentration risk.

Where Can You Buy Subsquid (SQD)?

SQD trades on several centralized exchanges and on decentralized exchanges across its three chains, with availability varying by venue and jurisdiction. Before any decentralized trade, verify the contract address against the official sources above, since symbols are not unique.

Storage Options After Purchase

SQD sits in any wallet supporting the relevant chain: MetaMask, Rabby or Trust Wallet for everyday use, with Ledger or Trezor for offline key storage. Delegating requires a self-custodied wallet that can sign on the chain hosting the network's contracts.

Related Coins

• The Graph (GRT)
• Space and Time (SXT)
• Pyth Network (PYTH)
• DIA (DIA)
• Filecoin (FIL)