Network status

Check how Guveno's chain workers are tracking each network (the same data behind the dashboard status page) and nudge a wallet or address to re-scan.

Chain sync status

Returns one row per chain/network the server tracks, with how far it has synced and its connection health.

curl https://api.guveno.com/v1/sync/status \
  -H "Authorization: Bearer gv_live_your_key_here"

{
  "items": [
    {
      "chain": "ethereum",
      "network": "mainnet",
      "cursor": "20461123",                  // last processed block/ledger height
      "lastSyncedAt": "2026-06-14T11:59:50.000Z",
      "connectionStatus": "connected",
      "activeEndpoint": "esplora",            // id of the upstream provider in use, may be null
      "lastError": null,
      "lastHealthyAt": "2026-06-14T11:59:50.000Z"
    }
  ]
}

Status values

• connected: the worker is tracking the chain normally.
• degraded: syncing, but a provider is erroring or falling behind.
• disconnected: no healthy provider; the chain isn't advancing.
• disabled: this chain's worker isn't enabled on the server.

A connected status with a recent lastSyncedAt means deposits and confirmations are flowing. If you see degraded or disconnected, events may be delayed until it recovers.

Forcing a re-scan

Reads one address's native balance from the chain now and hints the worker to re-scan for deposits, instead of waiting for the next poll. Useful right after you expect a deposit. Returns { "accepted": true } with status 202.

Each address can be refreshed once every 5 minutes. A repeat inside that window returns 429 with a Retry-After header; wait that long rather than retrying.

Refreshing a whole wallet is a dashboard action (the wallet's Settings, under Advanced). It runs in the background and can be started once an hour per wallet. You shouldn't need it from an integration: balances already update as deposits and withdrawals confirm.