Settlement Status
Settlement status is an operator-only service endpoint. There is no public Edge route for querying a settlement batch, and user access tokens do not authorize this service.
Operator Status Endpoint
GET /v1/status
GET /v1/status?from={height}&to={height}
Send the bearer token configured as GDX_SETTLEMENT_AUTH_TOKEN directly to the settlement service:
curl "$GDX_SETTLEMENT_OPS_URL/v1/status?from=1200&to=1250" \
-H "Authorization: Bearer $GDX_SETTLEMENT_AUTH_TOKEN"
The service is intended for private operations networking. Do not expose it through api.godarkdex.com/api/v1.
Response
{
"sealed_height": 1250,
"finalized_heights": [1200, 1201, 1202]
}
| Field | Description |
|---|---|
sealed_height | Latest sealed internal ledger height known to the settlement database |
finalized_heights | Finalized checkpoint heights in the requested inclusive from / to range; omitted range parameters produce an empty array |
This endpoint does not return fictional batch ids, trade counts, or a transaction signature per user-visible batch.
Checkpoint State
Internally, checkpoint records use:
| State | Meaning |
|---|---|
pending | The sealed height exists locally and still needs an L1 submit attempt |
anchored | Checkpoint commitment fields were verified on L1, but the local record has no submit signature and slot |
confirmed | The checkpoint transaction landed and the record includes its Solana signature and slot |
Both anchored and confirmed mean the height is present on L1. confirmed describes how the local service observed submission; it is not a separate public batch API state.
For account-agnostic public information, see Transparency.