Return syncing status (latest block synced) in header of subgraph query responses #494
Labels
Comments
gusinacio
added
type:feature
Linear
gusinacio
changed the title
|
The requirements can be limited to the block hash, number, and timestamp for the latest indexed block for the subgraph deployment being queried. It's unnecessary for any client to get block info for any block that cannot be queried yet. |
Theodus
added a commit
to graphprotocol/graph-node
that referenced
this issue
Nov 25, 2024
This adds a `graph-indexed` header to query responses. The header value contains the block hash, number, and timestamp for the most recently processed block in the subgraph. This avoids the need to rewrite all queries to include `_meta { block { hash number timestamp } }` in either the indexer-service or gateway.
Related: edgeandnode/gateway#900, graphprotocol/indexer-rs#494
Theodus
pushed a commit
that referenced
this issue
Dec 4, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem statement
Currently the Gateway uses query rewrites to keep track of block numbers on each chain.
Expectation proposal
Include header with
latestSyncedBlockNumberand chainHeadBlock information:chainHeadBlocknumber,chainheadBlockHash, andchainHeadBlocktimestamp.The text was updated successfully, but these errors were encountered: