TRANSACTION LIFECYCLE
Read frame receipts
Distinguish inclusion from successful execution. Inspect individual frame results or wait until every returned frame has succeeded.
API
client.waitForFrameReceipt({ hash, ...options })Usage
TYPESCRIPTreceipts.ts
// One read: null means no receipt was returned yet.const current = await client.getFrameReceipt({ hash });// Poll for successful execution; throws if a frame reverts.const receipt = await client.waitForFrameReceipt({ hash, expectedFrameCount: 2, timeoutMs: 120_000, pollingIntervalMs: 2_000,});Examples use the configured client from Create a client.
Parameters
| Name | Type | Description |
|---|---|---|
hash | Hex | The transaction hash to inspect. |
expectedFrameCount | number? | An optional check against the expected number of frames. |
timeoutMs | number? | Maximum wait duration. Defaults to 120,000 milliseconds. |
signal | AbortSignal? | Cancel waiting. This does not cancel the transaction. |
Returns
getFrameReceipt: Promise<FrameReceipt | null>. waitForFrameReceipt: Promise<FrameReceipt>.
Behavior to know
- A reverted frame raises FRAME_REVERTED and identifies failed frame indices.
- A receipt is evidence of observed inclusion, not finality. A timeout is not proof of rejection.