Responses and retries

The relay reports transaction broadcast, not transaction execution.

BROADCAST

{
  "requestId": "018f5ef2-88a1-7b41-a826-4b679010f87f",
  "status": "BROADCAST",
  "txHash": "0x...",
  "sponsorAddress": "0x...",
  "sponsorNonce": "42",
  "transactionType": "DYNAMIC_FEE"
}

At least one configured RPC accepted the signed transaction. Store the response, fetch the receipt, require receipt success, and verify the action-specific event or state transition.

REJECTED

{
  "requestId": "018f5ef2-88a1-7b41-a826-4b679010f87f",
  "status": "REJECTED",
  "code": "INVALID_WALLET_SIGNATURE",
  "message": "wallet signature is invalid",
  "retryable": false,
  "retryAfterMs": null,
  "candidateTxHash": null,
  "sponsorAddress": null,
  "sponsorNonce": null
}

The request or transaction candidate was definitely declined under the returned classification. Correct the request. Retry unchanged only when retryable is true, and respect retryAfterMs when provided.

UNKNOWN

BROADCAST_RESULT_UNKNOWN means the relay cannot prove whether the RPC accepted the candidate. Do not blindly create another request. First query candidateTxHash when present and reconcile the wallet's nonce, AccountCore authorization state, and expected contract events.

Safe retry policy

Situation	Action
HTTP connection failed before any response	Treat the result as ambiguous; reconcile before re-signing.
retryable: true	Retry after the indicated delay, using your bounded retry policy.
retryable: false	Do not retry unchanged. Correct or regenerate the request.
BROADCAST	Never resubmit merely because inclusion is slow. Track txHash.
BROADCAST_RESULT_UNKNOWN	Query the candidate and on-chain state before deciding.
Receipt reverted	Inspect the revert and current nonces/state; regenerate stale signed fields before retrying.

requestId is a tracing and best-effort duplicate-detection identifier. It does not guarantee durable idempotency across processes or restarts.

The OpenAPI YAML lists every stable error code and exact response schema.