Skip to main content

​
Submit a preconf request

To submit a preconf request fill in the following curl template for eth_sendRawTransaction with the params containing your raw transaction. The endpoint to send the request to is listed in Networks and the query parameters to constrain your request are listed below.
ParameterTypeDescription
deadlineuint64Number of seconds to attempt to gain a preconf commitment
fallbackbooleanUpon failure to gain a commitment, or any other failure, should the preconf request be forwarded as a standard/non-preconf request
preconfbooleanWhether the request is a standard request or a preconf request
An example request to the holesky network: 
curl -X POST \
  'https://preconf.holesky.spire.dev/v0/?deadline=3&fallback=true&preconf=true' \
  -H "Content-Type: application/json" \
  --data '{
    "jsonrpc":"2.0",
    "method":"eth_sendRawTransaction",
    "params":["0xRAW_TX_HERE"],
    "id":1
  }'
The router will respond with the hash of your transaction but that transaction may not appear in any block explorer until a preconfer has submitted it to the mempool or the router failed to get a commitment and forwarded the request to a standard RPC provider. The hash is used as a parameter to query so save it for the next step. 
{
  "id":1,
  "jsonrpc":"2.0",
  "result":"0x..."
}

​
Submit a standard request

To submit a non-preconf request i.e. use the router to forward your request to a RPC provider either change the method (and the rest of the body) to not be eth_sendRawTransaction or in the url specify the preconf=false parameter.