A short review can keep different kinds of evidence from being mixed up.
LET’S PICTURE IT
Before dispatching a parcel, check the city, destination, contents, price and any standing permissions on the order.
SEE IT FOR YOURSELF
Illustration · no network calls
Prepare
→
Sign
→
Share
→
Include
→
Finalize
Maya prepares an instruction: send 0.01 pretend ETH to Leo.
A local simulation. Nothing is signed or sent to a network.
Identify the action
Name what you intend: send native ETH, move a token, set an allowance or sign a message. If you cannot explain the requested operation, a familiar-looking confirmation is not enough information.
Identify the context
Check network, authorizing account, destination contract and any asset identity. For token calls, distinguish the transaction destination from the recipient or spender encoded inside the arguments.
Review quantities and permissions
Keep raw units, decimals, value and execution fee separate. For approvals or signatures, inspect scope, amount, relevant domain and expiry information when applicable. A small visible payment does not imply a small permission.
Check the result with the right record
After authorized activity, distinguish submission, receipt outcome and finality. Do not repeat payments merely because one interface has not updated. Use the appropriate evidence for the stage you are trying to confirm.
QUICK CHECK · NO PRESSURE
Which item is not a substitute for reviewing the actual request?
Branding is presentation. Review the fields and capabilities being authorized.