Transaction Checks

Do not rely only on the first and last few characters or trust the clipboard blindly. For an unfamiliar recipient or larger amount, verify through a trusted channel and consider a small test.

A repeatable order of checks is more reliable than memory. Review source, network, account, target and expected outcome each time so the same safety logic carries across wallets and DApps.

Similar address formats do not make networks interchangeable. Sender and recipient should agree on the target network and any additional contract or memo/tag requirements.

When a task involves a third-party contract, bridge, validator or web service, separate that external risk from the wallet itself. A wallet can display and sign a request, but it cannot guarantee the safety of outside code or services.

Assets with the same name may exist on different networks or contracts. Verify asset identity, amount and expected gas to avoid mistakes involving decimals, units or token contracts.

Put this concept back into the current network, account and request type before acting. Identify what the interface is asking for, then decide whether a signature, gas payment or ongoing permission is actually required.

Blockchain transactions generally cannot be unilaterally reversed. Keep the transaction hash and determine whether the transaction is pending, successful or failed before taking another action.

Do not rely on a button label or a familiar-looking page as the reason to continue. Compare the request with the on-chain target, network state and expected result, and stop when those pieces do not line up.