Review a token swap from a dApp

How to do it

1. Choose the input asset, output asset, amount and network in the dApp. Request its quote.
2. When Oath opens, confirm the dApp origin, selected wallet/account and network.
3. Read the input and output assets using their full identities. Check whether an amount is exact, a maximum input or a minimum output.
4. Review the recipient, native-coin value, network fee and deadline when shown. A token approval or Permit2 signature may arrive as a separate request before the swap.
5. Open Transaction data for readable operations and the original technical data. If an unfamiliar call cannot be explained, reject it until you can verify its purpose.
6. Confirm and authenticate only the request you intended. Return to the dApp for any remaining step, then verify the actual transaction outcome.

For recognized router methods Oath displays readable swap bounds and routing operations. Native wrapping/unwrapping is only summarized when the route supports that interpretation.

A quote or simulation is not a guaranteed settlement price. Slippage, price movement, expiry and contract conditions can cause a swap to fail.

Unknown routers, commands or metadata remain explicitly unknown or technical. A safe review must not invent an output token or interpret every arbitrary contract call as a swap.