How to Send Crypto Safely: Addresses, Networks, and Mistakes to Avoid – Genghis

Last updated: May 8, 2026

Sending crypto safely means three things: picking the right network for the token, double-checking the destination address, and confirming the transaction reached its target on-chain. Most "lost crypto" cases come from rushed sends. Genghis uses a one-time payment address per order to remove guesswork at checkout.

How to send crypto safely — addresses, networks, and common mistakes on Genghis

What Does It Mean to "Send Crypto Safely"?

A safe crypto send is one where the funds reach exactly the intended recipient on exactly the intended network, are confirmed by the network's validators, and arrive in a usable state.

The reason this matters more in crypto than in traditional banking is irreversibility. A bank wire sent to the wrong account can usually be reversed by calling the bank within a window. A blockchain transaction is final once confirmed: there is no central authority that can claw it back. If the funds went to the wrong place, recovery depends on whether the receiving address is controlled by anyone able and willing to return them.

Crypto has two distinct failure modes that the safety habits below are designed to prevent:

Wrong address. The recipient address contains a typo, a clipboard hijacker swapped it during paste, or the user pasted an address from a different transaction. Funds go to a wallet the sender does not control. Recovery depends on who controls that wallet, and is rarely possible.
Wrong network. The token name is correct (USDT, USDC, ETH) but the network is wrong (sent on Ethereum to an address that only exists on Tron). Recovery is sometimes possible — particularly across EVM-compatible chains — but requires technical intervention and is not guaranteed.

A safe send is essentially a small set of habits applied consistently. The sections below walk through each one.

How to Read a Crypto Address

A crypto address is the destination identifier for a transaction. Every blockchain uses its own format, and learning to recognize the format on sight is the first line of defense against wrong-chain mistakes.

Bitcoin addresses start with 1, 3, or bc1. Examples:

Legacy: 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa
P2SH: 3J98t1WpEZ73CNmQviecrnyiWrnqRhWNLy
SegWit (bech32): bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq

A Bitcoin address is 26–62 characters long.

Ethereum and EVM addresses start with 0x followed by 40 hexadecimal characters (0–9, a–f). Example: 0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb6. The same format is used on all EVM chains: Ethereum, BNB Smart Chain, Polygon, Avalanche, Arbitrum, Optimism, Base. This is convenient for wallets but is the single biggest source of cross-chain confusion (an Ethereum address looks identical to a BNB Smart Chain address).

Tron addresses start with T and are 34 characters long. Example: TQrZ5xXkQqV9F8sV8qZkXCYy1jJpL5HdEX. Tron uses base58 encoding similar to Bitcoin's legacy format.

Solana addresses are 32–44 characters in base58 encoding, no consistent prefix. Example: 7xKXtg2CW87d97TXJSDpbD5jBkheTqA83TZRuJosgAsU.

XRP addresses start with r and are 25–35 characters. XRP transactions also require a destination tag (covered below).

Cardano addresses start with addr1 and are long (about 100 characters).

A useful safety habit: when a wallet displays an address for the first time, look at the first 4–6 characters and the last 4–6 characters. These are what the wallet typically shows in transaction history, and they are the parts most easily verified at a glance.

What Is a Network or Chain When Sending Crypto?

A network — or chain — is the specific blockchain on which a transaction is broadcast. The same-named token can exist on multiple networks: USDT exists on Ethereum (ERC-20), Tron (TRC-20), Solana, BNB Smart Chain (BEP-20), and several others. Each version of USDT lives on its own network with its own address format and its own gas dynamics.

The critical concept: USDT-on-Ethereum and USDT-on-Tron are not the same thing at the protocol level. They are two different tokens that happen to share a name and a price peg. Sending USDT-on-Ethereum to a USDT-on-Tron address fails — the receiving address does not exist on the Ethereum network, and the funds are stuck in the void of the wrong chain.

The same applies for many ecosystem tokens: USDC, BUSD, wrapped BTC (WBTC), DAI, and others all exist on multiple chains. The address format alone is not enough to know which chain a transaction targets:

An Ethereum address (0x…) and a BNB Smart Chain address (also 0x…) are visually identical
The wallet may store funds on multiple EVM chains under the same address
The transaction always specifies which network, but the user-facing UX often hides this until it is too late

For paying on Genghis, the network selector at checkout is the explicit step that prevents this confusion. The buyer picks the token first, then picks the network — and Genghis displays the correct address for that network combination. The deeper context is in USDT across networks on Genghis, which shows the per-network options for the most-traded stablecoin. The recovery process if a wrong-network send happens is documented in the USDT wrong-network recovery guide.

The 5 Most Common Mistakes That Lose Funds

Across thousands of support tickets analyzed industry-wide, five mistakes account for the majority of lost-crypto incidents.

1. Wrong network. Already covered above. The single most common error. Sending USDT on Ethereum to a Tron-only address, or sending ERC-20 to an address that only accepts BEP-20. Frequency: high. Recoverability: variable.

2. Wrong address. Three sub-causes:

Typo on manual entry. Anyone typing 42 hex characters by hand will eventually fat-finger one. Always copy-paste, never type.
Clipboard hijacker malware. A class of malware monitors the clipboard for crypto addresses and silently replaces them with the attacker's address. The user pastes what looks correct but is actually the attacker's wallet. Mitigation: always verify the first and last 4–6 characters after pasting, before signing.
Wrong recent-recipient pick. Wallets that auto-suggest recent recipients can serve up the wrong one if multiple addresses are similar.

3. Missing memo or destination tag. Some networks require a secondary identifier alongside the address. XRP uses a destination tag. XLM and EOS use memos. Many exchanges (Binance, Kraken, OKX) require this when crediting deposits to user accounts. Sending XRP to an exchange without the destination tag means the funds reach the exchange's main wallet but cannot be credited to your account automatically — recovery requires support contact and is sometimes refused.

4. Sending below the dust threshold. Bitcoin and a few other chains have a minimum transaction amount called the "dust limit" (around 546 satoshis on Bitcoin). Transactions below this are rejected by the network. Less common today but worth knowing about.

5. Underpayment to a payment processor. Genghis and most crypto-checkout systems use a one-time payment address per order, expecting the exact amount specified at checkout. Sending less than the order amount leaves the order pending until the user tops up. Sending more triggers a refund of the excess to the source wallet. Sending nothing for too long leads to the order timing out and the address being released. The recovery flow for partial-amount sends is in the wrong-amount recovery guide.

How to Send Crypto Safely — A 6-Step Pre-Send Checklist

These six steps, applied every time, prevent the vast majority of send errors.

Step 1 — Verify the address (first 4 + last 4). After pasting the destination, look at the first 4 characters and the last 4 characters. Compare them to the address shown on the source page (the merchant's checkout, the recipient's wallet QR code, the exchange deposit screen). If even one character differs, stop. This single habit catches both clipboard hijackers and copy-paste mistakes.

Step 2 — Verify the network matches. Confirm that the network selected in the wallet matches the network the recipient expects. For Genghis: the network selected at checkout must equal the network the wallet sends from. For an exchange deposit: the network shown on the exchange's deposit screen must equal the network the wallet sends from.

Step 3 — Verify the memo or destination tag if required. XRP, XLM, EOS, BNB Beacon Chain, and most exchange deposits need this. If the recipient explicitly says "no memo required," that is fine. If the field is blank when the recipient required one, the send will not be credited correctly.

Step 4 — Send a small test amount first (for new addresses). When sending to a new address for the first time — especially for high-value transactions — send a $1–5 test first. Wait for confirmation, verify the recipient acknowledges receipt, then send the rest. Test sends are not common practice for $50 gift card orders, but they are smart practice for new wallets, new exchanges, and any transfer where the cost of an error is high.

Step 5 — Check the gas or fee estimate. Before signing, look at the network fee the wallet estimates. If it seems unusually high (10× the typical for that network), the wallet may have set fast-priority by default. If it seems unusually low, the transaction may stall in the mempool. Adjust to a reasonable level for the urgency.

Step 6 — Confirm and broadcast. Sign the transaction. The wallet broadcasts it to the network. Note the transaction hash (TXID) for later reference — this is how the transaction can be verified on the network.

For Genghis purchases specifically, the master hub at buy gift cards with crypto is the canonical landing page that walks through token and network selection. For broader spending context, the how do you spend cryptocurrency guide covers the daily-life framing.

How Do I Confirm My Transaction Went Through?

Once a transaction is broadcast, it lives on the blockchain. Anyone with the transaction hash (TXID) can look it up on a public block explorer and see its status.

The major block explorers:

Bitcoin: mempool.space — the most usable visual explorer for BTC mempool state and fee analysis
Ethereum and EVM chains: etherscan.io — the standard for ETH, also has variants for BNB (bscscan.com), Polygon (polygonscan.com), and Arbitrum
Tron: tronscan.org
Solana: solscan.io or explorer.solana.com

A transaction passes through several states:

Pending in mempool. Broadcast but not yet included in a block. Waiting for a validator to pick it up.
Confirmed. Included in a block. The first confirmation means the transaction is on-chain. Each subsequent block adds another confirmation.
Finalized. After enough confirmations, the transaction is considered immutable. The threshold varies by chain: 1 confirmation on Solana is final; 6 confirmations is the standard for Bitcoin (about 60 minutes).

For Genghis orders, the system tracks the same on-chain data automatically. Once the network confirms the payment, the order completes and the digital code is delivered. The expected wait times per network are documented in Genghis delivery times. If a transaction is stuck in pending for longer than expected, the stuck-in-pending recovery guide covers the troubleshooting steps.

What If I Send to the Wrong Address or Wrong Network?

The recovery options depend on what kind of mistake was made.

Sent to the wrong address (controlled by an unknown party). The funds are at the destination address. If the address is controlled by another person, you can ask, but you have no leverage — they may keep the funds. If the address is a burn address or invalid, the funds are gone. There is no central authority that can reverse a confirmed transaction.

Sent to the wrong address but on the right network (controlled by a service). If the destination address belongs to an exchange or a service like Genghis, the recovery may be possible. Contact the service's support, provide the transaction hash, and explain what was intended. Recovery depends on the service's policy and the operational complexity of the recovery.

Sent on the wrong network (correct token, wrong chain). This is the most common case and often recoverable. Two scenarios:

EVM-to-EVM mistake. Sent USDT-ERC20 (Ethereum) to a USDC-BEP20 deposit address (BNB Smart Chain). Both addresses look identical (0x…). The funds are at the receiving address but on the wrong chain. Most exchanges and many wallets can recover this by importing the receiving wallet's private key into the alternate chain — a manual but achievable process. Genghis support handles this for orders, documented in the EVM-to-EVM recovery process.
Cross-architecture mistake. Sent USDT-ERC20 to a TRC20 address. Tron addresses cannot be derived from Ethereum private keys, so the standard recovery does not apply. Recovery here is much harder and often impossible without specific support arrangements.

Sent the wrong amount (under or over). For Genghis orders, undersending leaves the order pending until topped up; oversending triggers an automatic refund to the source wallet. The full wrong-amount recovery process documents what to do.

In all recovery cases, the transaction hash (TXID) and the wallet that sent the funds are the only proofs that matter. Save both immediately after sending. Anyone in support troubleshooting the case will need them.

How to Pay Genghis Safely

The Genghis payment flow is designed around the safety habits above, with one important convenience: every order generates its own one-time payment address.

One-time payment address per order. When the buyer completes checkout, Genghis generates a fresh payment address specifically for that order. The address is not reused. This eliminates two common errors: copying an address from a previous order (which would not credit the new one), and clipboard-hijacker malware swapping a stored address (because there is no stored address to swap).

Exact amount required. Genghis displays the precise amount of crypto needed for the order, calculated at the prevailing spot rate at checkout. Send the exact amount. Sending more triggers a refund of the excess to the source wallet. Sending less leaves the order pending until topped up.

Network selection at checkout. Before generating the payment address, Genghis asks the buyer to pick the network. With 300+ supported cryptocurrencies, USDT alone can be paid on Ethereum, Tron, Solana, BNB Smart Chain, or Polygon — and the address shown is specific to the network selected. This forces the explicit step that prevents wrong-network errors.

Refund to source wallet. Any refund — overpayment, expired order, support intervention — routes back to the wallet address that sent the funds. Genghis does not maintain a customer account balance; refunds always return to the original payer.

Privacy by default. Genghis collects only the email address used to deliver the digital code. No identity verification. No banking link. No KYC at digital-goods checkout. Zero platform fees beyond the network gas paid by the buyer. The full security model is detailed in is Genghis safe?, which covers the trust architecture in depth.

If something does go wrong with a Genghis order — unreceived code, wrong amount, wrong network, stuck in pending — the troubleshooting category of this Help Centre covers each scenario. The fastest path to resolution is always: save the transaction hash, then check the relevant troubleshooting article. If the issue is not covered, contact support with the TXID and the order number.

Frequently Asked Questions

How do I send crypto safely?

Six habits prevent most send errors: verify the first and last four characters of the destination address after pasting; confirm the network matches what the recipient expects; include any required memo or destination tag; send a small test first for new high-value addresses; check the gas estimate is reasonable; and save the transaction hash after broadcasting. For Genghis orders, the one-time payment address per order removes most of the variables.

What is a crypto address and why does it matter?

A crypto address is the destination identifier for a transaction. It is essentially the recipient's account number on a specific blockchain. Every chain uses its own address format — Bitcoin starts with 1, 3, or bc1; Ethereum and EVM addresses start with 0x; Tron starts with T; Solana uses 32–44 base58 characters. The address tells the network where to deliver the funds. A single character wrong means a different destination.

What is a network or chain when sending crypto?

A network is the specific blockchain on which a transaction is broadcast. The same-named token can exist on multiple networks: USDT on Ethereum (ERC-20), Tron (TRC-20), Solana, BNB Smart Chain (BEP-20), and others. These are technically different tokens that share a name and price peg. Sending USDT on the wrong network for the recipient's address is the most common cause of stuck or lost crypto.

What happens if I send crypto to the wrong address?

The funds go to whoever controls that address. If the address belongs to a service (an exchange, Genghis), recovery may be possible by contacting their support with the transaction hash. If the address is a typo with no controller (like a burn address) or belongs to an unknown party, the funds are typically unrecoverable. There is no central authority that can reverse a confirmed blockchain transaction.

What is a memo or destination tag?

A memo or destination tag is a secondary identifier required alongside the address on certain networks. XRP uses a destination tag; XLM and EOS use memos; many exchange deposits require one to credit funds to the correct user account. Sending without the required memo means the funds reach the recipient's main wallet but cannot be auto-credited. Recovery requires manual support intervention and is not always possible.

How do I confirm a transaction went through?

Look up the transaction hash (TXID) on the network's block explorer: mempool.space for Bitcoin, etherscan.io for Ethereum and EVM chains, tronscan.org for Tron, solscan.io for Solana. The status will show pending (in mempool, waiting for inclusion), confirmed (in a block), or finalized (enough confirmations to be considered immutable). Genghis tracks the same data automatically and delivers the digital code once the network confirms.

What's the safest way to pay Genghis with crypto?

Pay using stablecoins (USDT or USDC) on a low-fee high-throughput network — Solana, Tron (TRC-20), or Polygon. The combination has the cheapest gas, the fastest confirmation, and the most predictable price. Use the network selector at Genghis checkout to confirm the network before signing. Save the transaction hash. The full Genghis checkout flow is documented in how it works.

About the author: this guide was written by Claudio Cuccovillo, founder of Genghis Ltd.