confirmGaslessRequest

Follow one accepted relay request through to on-chain reality — the opinionated layer above waitForGaslessRequest.

import { confirmGaslessRequest } from "@symmio/trading-core";
 
const accepted = await relayGrantDelegation(config, { account, delegatedSigner, selectors, expiryTimestamp });
const { request, txHash, receipt } = await confirmGaslessRequest(config, {
  requestId: accepted.requestId,
  until: "receipt",
});

Where the driver reports facts — it resolves with whatever terminal it reaches — this asserts the outcome a caller is waiting for: it resolves only on succeeded, and throws for reverted / failed / rejected with the record attached to the error’s responseData.

With until: "receipt" it then waits for the receipt on this config’s own client. That is not belt-and-braces: the relayer’s succeeded is the relayer’s node’s view, and invalidating cached reads against a node that has not yet seen the block re-reads pre-state — which looks exactly like the stalled UI this whole mechanism exists to prevent.

Transient read failures — a 429, a 503, a dropped connection — are absorbed by the status wait underneath rather than reported as failures. Subscribe to onTransportIssue to show “status unavailable” while they last; the relay is unaffected. This never re-submits: a 202 is the point of no return.

React consumers rarely call this directly: every relay hook in @symmio/trading-react confirms by default and invalidates the reads its action changed. See the React gasless guide.

Parameters

Returns

Errors

The first three carry the terminal record on responseData, so the real cause is readable without parsing a message.