A same-chain swap uses one wallet-broadcast router transaction. It does not create a cross-chain escrow order or require solver reimbursement. Approval transactions, when required, are separate transactions. Infinity Hub supports swap reporting on configured EVM and Solana chains. Confirm that the selected gateway forwards these endpoints before enabling reporting.

Report a transaction

POST /v1/swaps Report the swap transaction, not the token approval. Do not substitute the wallet’s pending nonce for the actual transaction nonce. Retry a lost report with the same quote and transaction identity. Infinity Hub validates quote ownership and execution binding before accepting the watch. A replacement must match the original sender, nonce, and issued call. A different call or cancellation is not a successful swap.

Read tracking

GET /v1/swaps lists the subject’s reports. GET /v1/swaps/{chainDomain}/{txHash} reads one report. The list defaults to 100 entries and caps a page at 500 entries. An absent or empty cursor starts from the newest row. Pass each returned nextCursor unchanged to the next request. Stop when nextCursor is absent. A full final page can return a cursor followed by an empty page. These pagination rules differ from order history. Tracking depends on RPC evidence and configured confirmation requirements. Infinity Hub does not infer success solely from a wallet-reported hash. For Solana, the returned quote binds the fee payer, blockhash, and ordered instructions. Do not modify the returned transaction before signing. If its lifetime expires before broadcast, obtain a new quote. After broadcast, reconcile the original transaction before requesting replacement execution.