A method returning calldata has prepared a plan. FxAeon adds the execution boundary in service planners (opens in a new tab), policy validation (opens in a new tab), and the transaction runner (opens in a new tab).
- Bind the review. Validate wallet, chain, contract, action, token, amounts, recipients, approvals, economic limits, and conversion-route fingerprints against the user's request.
- Simulate in order. Require a successful result for every planned call. Missing, truncated, failed, or unavailable simulation fails closed.
- Ask for each signature. Send only the reviewed step to the wallet. Exact token or position approval is distinct from the protocol action.
- Wait for each receipt. Verify the mined transaction matches the reviewed data and remains canonical through the required confirmations before continuing. Rejection, revert, timeout, or nonce drift stops the route.
- Read again. Refresh authoritative SDK/chain state after the action receipt. If this read fails, show the confirmed transaction and unavailable fresh state separately. A bridge also needs destination-delivery verification.
Simulation reduces avoidable failures; it does not guarantee execution or remove protocol, market, bridge, or smart-contract risk. See the scope and fee-review contract (opens in a new tab).