State what you intend to do
Before interacting with a wallet prompt, say the action plainly: “Send this asset to this destination on this network,” or “Approve this contract to spend no more than this amount.” Compare that sentence with the final signing screen. If the screen describes a different contract, asset, spender, amount, or network, stop.
Match the network on both sides
The same asset name can exist on several networks, and an address format may look valid across more than one. Confirm that the sending service and receiving service both support the exact network. Do not rely on ticker symbols alone. Bridging is a separate transaction with separate contract and finality risks.
Verify every destination requirement
- Obtain the address from the intended recipient through a trusted route.
- Use the CoinPork address comparison tool for a character-for-character check.
- Confirm whether the destination requires a memo, tag, or payment ID.
- Do not select a look-alike address from transaction history.
- For saved addresses, confirm that the saved entry has not changed.
Understand every reduction
Separate the network fee, service fee, spread, destination minimum, and any withdrawal fee. Ask whether the fee is paid in the transferred asset or another network asset. A low displayed service fee can coexist with a large spread. Use the fee-impact calculator as a planning aid, then use the provider’s final quote.
Use a test transfer when appropriate
A small test can confirm routing and account crediting, but it does not prove every later transaction will succeed. Some services impose minimum deposits, and some destination tags must be present even on tests. Verify that the test amount is large enough to be credited but small enough to limit loss.
Keep enough evidence to investigate
Record the transaction hash, network, asset, destination, amount, provider reference, and time. Do not store seed phrases or private keys with the record. If the status is unclear, do not immediately repeat the transfer; check the network explorer and provider status first to avoid a duplicate payment.