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.
On the /extended/v1/status endpoint, the status is 'ready' even if a hundred blocks still need to be synced { "server_version": "stacks-blockchain-api v2.0.0 (master:8b95f1d9)", "status": "ready" }
Describe the solution you'd like
When more than X blocks (5, for example) still need to be synced, we would have the 'syncing' status { "server_version": "stacks-blockchain-api v2.0.0 (master:8b95f1d9)", "status": "syncing" }
The text was updated successfully, but these errors were encountered:
mardi00
changed the title
Update /extended/v1/status to "syncing" if more than 5 blocks are missing
Update /extended/v1/status to "syncing" if more than X blocks are missing
Feb 10, 2022
The API does not have the information required for this feature. Once PR stacks-network/stacks-core#2768 exposes sync status / block percentage, then the API could potentially expose that info as well. Although, if an RPC endpoint already exposes it, there's no real reason for the API to duplicate that in another endpoint.
Is your feature request related to a problem? Please describe.
On the /extended/v1/status endpoint, the status is 'ready' even if a hundred blocks still need to be synced
{ "server_version": "stacks-blockchain-api v2.0.0 (master:8b95f1d9)", "status": "ready" }
Describe the solution you'd like
When more than X blocks (5, for example) still need to be synced, we would have the 'syncing' status
{ "server_version": "stacks-blockchain-api v2.0.0 (master:8b95f1d9)", "status": "syncing" }
The text was updated successfully, but these errors were encountered: