LibraryData and agents2021Design paperCorpus record
SQD: a decentralised query network for chain data
SQD. Subsquid.
SQD publishes a network that stores and serves chain data to indexers, so a query does not have to hit a full node for every read.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
SQD publishes a network that stores and serves chain data to indexers, so a query does not have to hit a full node for every read.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 3
- Records linked
- 1
01 Claim ledger
What the paper is allowed to say
Each row is a sentence already in the study. The status is the same on every row: a model claim, not a live measurement.
Claim 01 · Paper model
The defect
A query network is not a source of truth. The chain is. The network is a cache with a trust assumption about who served the bytes.
Claim 02 · Paper model
The proposal
SQD publishes a network that stores and serves chain data to indexers, so a query does not have to hit a full node for every read.
Claim 03 · Paper model
The mechanism
Workers store data. A gateway or scheduler routes queries. An indexer consumes them.
Claim 04 · Paper model
The bound
No query-volume figure is stated here.
02 Three cuts
Observation, model, falsifier
A desk does not stop at the summary. Each claim is cut three ways, using only this study's own assumptions and checks. Nothing here is a new figure.
01 The defect
Observation
What the study says
A query network is not a source of truth. The chain is. The network is a cache with a trust assumption about who served the bytes.
Model
What has to hold
The document is the one at the source URL. A marketing page with the same brand is not this text.
Falsifier
What would retire it
Does a client verify the response against the chain, or trust the worker?
02 The proposal
Observation
What the study says
SQD publishes a network that stores and serves chain data to indexers, so a query does not have to hit a full node for every read.
Model
What has to hold
The document is the one at the source URL. A marketing page with the same brand is not this text.
Falsifier
What would retire it
Does a client verify the response against the chain, or trust the worker?
03 The mechanism
Observation
What the study says
Workers store data. A gateway or scheduler routes queries. An indexer consumes them.
Model
What has to hold
No price, supply, yield, or adoption figure is added by this desk.
Falsifier
What would retire it
Who is paid to store the data?
04 The bound
Observation
What the study says
No query-volume figure is stated here.
Model
What has to hold
No price, supply, yield, or adoption figure is added by this desk.
Falsifier
What would retire it
What block height is a response bound to?
03 Sequence
One action, as an operating tape
- 01Workers store data. A gateway or scheduler routes queries. An indexer consumes them.
- 02A proof of the query response, if the docs include one, is what would let a client stop trusting the worker. If they do not, the client trusts the worker.
- 03Lag behind the chain head is a property of the pipeline. A query result has a block height, and the height is part of the answer.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
SQD publishes a network that stores and serves chain data to indexers, so a query does not have to hit a full node for every read.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
No query-volume figure is stated here.
What actually moves
The cut
A proof of the query response, if the docs include one, is what would let a client stop trusting the worker. If they do not, the client trusts the worker.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
No query-volume figure is stated here.
What a later deployment may change
The cut
Lag behind the chain head is a property of the pipeline. A query result has a block height, and the height is part of the answer.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
No query-volume figure is stated here.
05 Register
What has to be true
Model · Not re-measured
You are reading the SQD docs. The Graph remains a separate study.
Model · Not re-measured
The document is the one at the source URL. A marketing page with the same brand is not this text.
Model · Not re-measured
No price, supply, yield, or adoption figure is added by this desk.
06 Divergence
What happened after the paper
An unproved response can be cheaper and wrong.
A later client, parameter set, or reward formula is a different object. Cite this paper for the mechanism. Cite a primary release for the network. This desk has not re-run the proof.
07 Pre-mortem
What to check before you use the idea
- 0 of 3 marked on this browser. A mark is a reading note, not a pass, a rating, or a recommendation.
08 Anatomy
The paper, in the order a builder needs
The problem it names
A query network is not a source of truth. The chain is. The network is a cache with a trust assumption about who served the bytes.
What the design proposes
- Workers store data. A gateway or scheduler routes queries. An indexer consumes them.
- A proof of the query response, if the docs include one, is what would let a client stop trusting the worker. If they do not, the client trusts the worker.
- Lag behind the chain head is a property of the pipeline. A query result has a block height, and the height is part of the answer.
How the mechanism is specified
- Workers store data. A gateway or scheduler routes queries. An indexer consumes them.
- A proof of the query response, if the docs include one, is what would let a client stop trusting the worker. If they do not, the client trusts the worker.
- Lag behind the chain head is a property of the pipeline. A query result has a block height, and the height is part of the answer.
What this page does not treat as proven
- No query-volume figure is stated here.
- This is not The Graph's document, though both index chains.
- An unproved response can be cheaper and wrong.
Why the desk still reads it
SQD publishes a network that stores and serves chain data to indexers, so a query does not have to hit a full node for every read.
09 Lexicon
Terms, opened into the record
- Query worker
- A party who stores and serves chain data. They are not the chain.
- Indexer
- A consumer who builds a dataset from those responses.
10 Repository
Every linked record on this page
Underlined words open a page that already exists: a concept, a protocol profile, a failure record, or another paper. If a word is not underlined, this desk does not have a record for it.
Papers
This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.
Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.