An AI agent submits a swap. The RPC call times out.
What should it retry?
“No response” does not mean “no transaction.” The swap may have been broadcast, included, or still be pending. Blindly sending it again could create an unintended second trade.
My recovery checklist:
1. Observe the original attempt. Check any known transaction hash, the sender’s nonce, and chain state. Keep pending, reverted, reorged, and unknown outcomes distinct.
2. Recover the evidence. Resume receipt and verification work from the saved checkpoint. Do not sign or broadcast during this step.
3. Consider a new trade only after assessing the duplicate-execution risk. Prepare the exact call again, refresh the oracle and route review, and obtain fresh authorization. A confirmed or reverted transaction correlated to a single-use authorization consumes it.
Insight helps assess whether the evidence still supports the proposed trade. PriorSeal connects the authorized call to the execution actually observed.
The dangerous assumption is: “I didn’t get a response, so nothing happened.”
How does your agent handle an uncertain broadcast?
#AIAgents #Web3Security