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
Is your feature request related to a problem? Please describe.
Sometimes we need to know what's the latest available block number/hash. We can use the JSON-RPC provider to do that, but there is always the possibility that the Apibara DNA node and the provider node are not exactly at the same block.
Describe the solution you'd like
We should add a Status method to the rpc that returns the block syncing status, together with the cursors of the current finalized and accepted blocks.
serviceStream {
rpcStatus(StatusRequest) returns (StatusResponse);
}
messageStatusRequest {
}
messageStatusResponse {
// Optional because the chain may be so new that no block has been finalized. For example, devnets.optionalCursorfinalized=1;
Cursorlatest=2;
IngestionStatusstatus=3;
}
enumIngestionStatus {
INGESTION_STATUS_UNKNOWN=0;
INGESTION_STATUS_SYNCING=1;
INGESTION_STATUS_SYNCED=2;
}
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Sometimes we need to know what's the latest available block number/hash. We can use the JSON-RPC provider to do that, but there is always the possibility that the Apibara DNA node and the provider node are not exactly at the same block.
Describe the solution you'd like
We should add a
Status
method to the rpc that returns the block syncing status, together with the cursors of the current finalized and accepted blocks.The text was updated successfully, but these errors were encountered: