QUICKTXN / DOCUMENTATION

Your first submission

This example uses Robinhood Chain mainnet, chain ID 4663. Prepare a signed transaction in your own wallet; QuickTxn never needs your signing key.

1. Get access

Complete managed onboarding to receive an endpoint, credential, approved chains, rate limit, and fee agreement. Load QUICKTXN_ENDPOINT and QUICKTXN_API_KEY from your application configuration and secret manager. Keep the key out of browser bundles, URLs, and logs.

2. Verify the chain

curl --connect-timeout 3 --max-time 10 "$QUICKTXN_ENDPOINT" \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'

The response must contain "result":"0x1237". Stop on a different chain ID. This public method also keeps your HTTP connection active; it does not submit a transaction.

3. Build and sign

Use your chain RPC to obtain nonce, gas estimate, and current gas fees. Build an EIP-1559 transaction with chainId: 4663, your intended recipient and calldata, and the fee arrangement assigned to your account. Sign it locally with your existing wallet integration. A plain untipped transfer is accepted only if your account and deployment explicitly permit untipped submissions.

Save the following as submission.json, replacing the placeholder with the full signed transaction hex, including its 0x prefix. The placeholder is deliberately not a spendable transaction.

{"jsonrpc":"2.0","id":2,"method":"eth_sendRawTransaction","params":["0xSIGNED_TRANSACTION_HEX"]}

4. Submit

# Use the endpoint assigned during onboarding.
# QUICKTXN_API_KEY is loaded from your secret manager.
curl --connect-timeout 3 --max-time 10 \
  "$QUICKTXN_ENDPOINT" \
  -H 'Content-Type: application/json' \
  -H "X-Api-Key: $QUICKTXN_API_KEY" \
  --data @submission.json

Check the HTTP status and parse the response body. A successful JSON-RPC result is the transaction hash. An HTTP 200 response can still contain a JSON-RPC error. Do not treat it as success.

5. Verify the receipt

curl --connect-timeout 3 --max-time 10 \
  'https://rpc.mainnet.chain.robinhood.com' \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":3,"method":"eth_getTransactionReceipt","params":["0xTRANSACTION_HASH"]}'

A null receipt means the RPC has no receipt yet. Poll with bounded backoff. A receipt with status: "0x1" indicates successful execution; "0x0" indicates a revert. Check block inclusion and your required confirmation/finality policy before treating a payment or trade as final.

Timeouts and retries

The example uses a 3-second connect limit and a 10-second total limit as client starting values, not a service SLA. A timeout leaves submission uncertain. Check the receipt for the hash computed by your wallet before deciding whether to resubmit the exact same signed bytes. See endpoint failover.