Confirming Actions#

The confirm tap is the only thing standing between a proposal and an on-chain transaction. Here's exactly what it does.

What "Confirm" actually does#

When you tap ✅ Confirm:

1. Ava re-simulates the action against the latest on-chain state (gas prices, balances, prices).
2. If anything changed materially (e.g. HF moved, your balance moved, gas spiked), Ava re-presents with the new numbers instead of executing. You confirm the new numbers, or you don't.
3. The transaction is built and submitted through your authorized smart wallet / permission, never bypassing the on-chain spend caps you set.
4. Ava streams status: pending → confirmed → result.

What gets checked before sending#

• Caps. The transaction must fit inside the on-chain spend permission. If the proposal would exceed your cap, Ava refuses and tells you why.
• Allowlisted contracts. The transaction must target an allowlisted protocol contract for this Guardian job. Off-allowlist destinations are refused on-chain by the permission, not just by Ava.
• Slippage / price guard. For any action involving a swap or quoted price, Ava enforces a slippage bound. If the bound is breached, the transaction reverts safely — funds don't move.
• Sanity check on result. Ava compares the simulated outcome to the actual on-chain result. If they differ materially (e.g. a frontrun), Ava warns you in the post-action message.

After confirmation#

A short result lands in chat:

✅ Done. Supplied 300 USDC → health factor now 1.9. Gas: $0.38. I'll keep watching and ping you before it gets risky again.

You can:

• Ask for the on-chain transaction hash — Ava replies with an explorer link.
• Ask Ava to redo something (it'll re-propose, fresh simulation).
• Tell Ava to stop watching that position (/pause or revoke).

What if the transaction fails?#

• Reverted (safety guard triggered). Funds didn't move. Ava explains why — slippage, price drift, cap hit — and either re-proposes with tighter parameters or asks for your input.
• Stuck (gas too low / mempool congestion). Ava bumps gas inside reasonable bounds or asks you whether to bump further. Nothing happens behind your back.
• Network outage. Ava queues a retry and warns you. You can cancel the queued retry anytime.

What confirmation isn't#

• Not signing a seed phrase. Confirm in chat does not move keys around. The one-time signing happened earlier (the Guardian setup); the chat confirm is a permission-bounded action call into your smart wallet.
• Not "auto-approve everything in the future." Each action is its own confirm gate. The only thing one signature does is set up the cap-bounded permission.
• Not financial advice. Confirming is your decision. Ava can be wrong; you have the final word.