Skip to main content
A non-preconf request is not stored therefore an error / no data is returned if queried.

​
Query request status

Once a preconf request has been submitted you may use the hash to query its status to see if it has finished processing and if it has succeeded or failed. Here’s an example request querying against the holesky network and using the transaction hash from the Submit Request results: 
curl -X POST 'https://preconf.holesky.spire.dev/v0/' \
  -H "Content-Type: application/json" \
  --data '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "transaction",
    "params": { "tx_hash": "0xYOUR_TX_HASH" }
  }'
A valid request that successfully received a preconf commitment will respond with something like: 
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "tx_hash": "0x...",
    "query": {"deadline":3,"fallback":true,"preconf":true},
    "status": "Success",
    "timestamp_unix_seconds": "1749219302",
    "request_id": 1
  }
}
The request result status has four possible values:
  • Submitted - Initial value when the router stores the request
  • Pending - Awaiting a response from preconf providers
  • Success - a pre-confirmation commitment was received within the deadline or in the case that the request had the fallback parameter set to true the request was forwarded as a standard request
  • Failure - Any other scenario

​
Query commitment

If in the previous stage the status contained Success then we may attempt to query the commitment.
A request may have a Success status if it failed to gain a commitment but successfully forwarded the request to an RPC provider. In this case querying for a commitment will result in an error response.
 
curl -X POST 'https://preconf.holesky.spire.dev/v0/' \
  -H "Content-Type: application/json" \
  --data '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "commitment",
    "params": { "tx_hash": "0xYOUR_TX_HASH" }
  }'
If a commitment has been acquired then a valid request will respond with something like 
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "tx_hash": "0x...",
    "signature": "0x...",
    "slot": 42,
    "preconfer": "uuid",
    "timestamp_unix_seconds": "1749219302"
  }
}