You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
gusinacio
changed the title
[Feat.Req] - Return syncing status (latest block synced) in header of subgraph query responses
Return syncing status (latest block synced) in header of subgraph query responses
Nov 18, 2024
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.
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
Problem statement
Currently the Gateway uses query rewrites to keep track of block numbers on each chain.
Expectation proposal
Include header with
latestSyncedBlockNumber
and chainHeadBlock information:chainHeadBlocknumber
,chainheadBlockHash
, andchainHeadBlocktimestamp
.The text was updated successfully, but these errors were encountered: