Choose the right network before sending crypto

Start from the receiving account's deposit instructions. Match the exact asset and network on both sides, include any required memo or destination tag, and check a small transfer before sending the remainder. Choose among compatible networks only after those checks.

This is a source-researched workflow prepared on 21 September 2026. It does not report a transfer performed by Wayne. It applies to ordinary on-chain transfers; exchange-internal payments, bridges and payment invoices can use different procedures.

Treat a destination as several fields

A coin ticker does not provide enough information to select a transfer route. The receiving service must accept the asset on the network you use. A shared-looking address or a matching ticker is not proof of support. Coinbase's multi-network instructions require checking network compatibility and warn that an incorrect network can cause loss. Coinbase network guidance

Use this table as a transfer record. Obtain the details from the recipient or the authenticated receiving application, not from a transaction-history suggestion or an unsolicited message.

A token contract address identifies a token; it is not automatically your deposit address. If the receiving instructions distinguish native and bridged versions, preserve that distinction. Do not select a cheaper option solely because its name contains the same asset symbol.

Read memo and tag requirements literally

Some receiving services use a shared blockchain address and a memo or tag to identify a customer's deposit. The correct address alone may therefore be insufficient. Requirements come from the receiving service, and a missing or incorrect value can prevent crediting. Coinbase memo and tag explanation

Copy the value exactly into the dedicated field. Do not substitute a message to the recipient or invent a value to satisfy a form. When the recipient says no memo is needed but the sending application insists on one, stop and consult the services' official instructions. A small test does not make conflicting instructions safe.

Make a small transfer that can actually be credited

1. Open the destination's receive page and select the asset and network. Keep those instructions available while filling in the sending form.
2. Check the full destination address after pasting it. For a hardware wallet, compare against the receiving address shown by the device using its official procedure.
3. Enter the memo or tag if required. Confirm the final preview shows the same network and recipient details.
4. Choose a small amount whose net arrival exceeds the receiving minimum and which also satisfies the sender's withdrawal minimum. Allow for the quoted deduction. Kraken's documentation illustrates why withdrawal minimums and fees need separate attention. Withdrawal conditions
5. Send the test and retain the transaction hash, network, amount and time. Wait for the receiving account to show a usable credit; a sender's “completed” label alone is insufficient evidence of account credit.
6. Reopen and recheck the destination instructions before sending the remainder. A successful test applies to the details tested, not to a changed address, token or network.

Testing costs an additional transaction fee. For a very small transfer, fees or minimums may make a separate test impractical. That is a reason to reconsider the transfer amount or route, not to ignore incompatible details.

Plan for the next movement

Receiving tokens in a self-custody wallet does not guarantee you can immediately send them onward. For a conventional Ethereum transaction, gas is paid in ETH. Check the actual destination network's fee asset and wallet requirements before deciding where to receive funds. Ethereum gas documentation

Changing a network selector does not, by itself, bridge an asset from one chain to another. If the two services have no compatible route, stop and research a separate route. A bridge introduces additional transactions and risks and is outside this checklist.

When a transfer does not arrive

Do not repeat it immediately. Check the recorded network and hash with the relevant network explorer and compare the transaction with the receiving instructions. Then use the receiving service's official support channel, supplying public transaction details as requested. Never provide a recovery phrase. Recovery depends on the asset, network and service; it is not assured.

The practical conclusion is simple: verify compatibility first, then compare price and speed. A test transfer reduces uncertainty about one route, but it cannot guarantee the safety of later transfers or the reliability of either service.