Skip to content
Menu
Finabase Learn

Crypto · Wallets, exchanges and custody

How to send and receive crypto without losing it

A step-by-step guide to crypto transfers: matching the asset and network, reading address formats, test transactions, memos, fees in dollars and confirmations.

On this page
  1. What a transfer is
  2. Before you send: five checks
  3. What an address looks like
  4. Fees: what a transfer costs
  5. After you send: confirmations
  6. Receiving
  7. Common mistakes
  8. How Finabase does it
  9. Frequently asked questions
  10. Summary
  11. Check your understanding

A bank transfer that goes to the wrong account can often be traced, disputed and returned. A crypto transfer cannot. Once a transaction is confirmed on a blockchain, no company, developer or regulator can pull it back; bitcoin.org's own FAQ says a payment can be refunded only by the person who received it. If the address belongs to nobody, or the coins went out on a network the recipient does not use, they are usually gone.

Almost all such losses come from a short list of avoidable mistakes: the wrong asset, the wrong network, a wrong or tampered address, a missing memo. This guide walks through one transfer from start to finish, shows what a correct address looks like, works out what the fee costs in dollars, and explains how long "confirmed" takes. It describes the mechanics; it does not suggest that anyone should move coins.

What a transfer is

Coins do not sit in a wallet. They are entries on a shared ledger, and a transfer is a signed message that says "move this amount from my address to that address". Your wallet builds the message, signs it with your private key and broadcasts it. Validators or miners include it in a block, and from then on the ledger says the coins belong to the receiving address.

Two details explain most of what follows. First, the network checks only that the signature is valid. It has no idea whether the destination is the one you meant. Second, an address is just a number derived from a key. An address nobody holds the key for is still a valid destination, and coins sent to it stay there.

Before you send: five checks

Five checks before a transfer that cannot be reversed 1. Asset Which coin or token, exactly? 2. Network Same network on both sides 3. Address Copied, then read back in full 4. Test Small amount first; wait 5. Send The rest, to the same address A memo or destination tag, where the receiving exchange asks for one, belongs with step 3.
Five checks before an irreversible transfer. Where the recipient asks for a memo or destination tag, it is part of the address check.

1. The asset

Be exact about what is being sent. Tickers repeat, and many coins have near-namesakes. Bitcoin (BTC) and Bitcoin Cash (BCH) are different coins on different chains. A dollar stablecoin such as USDC is issued separately on many networks, and some networks carry both an issuer's own version and a "bridged" version of the same name. The recipient must support the exact asset, not something with a similar label.

2. The network

This is the check most often skipped. Tokens live on a particular network: Ethereum, a layer 2 built on it, or another chain entirely. An exchange's withdrawal screen will often offer several networks for one coin, with very different fees.

The sender and the recipient must pick the same one. If an exchange credits deposits of a token only on Ethereum and the token arrives on another network, the coins exist at that address on the other network, and the exchange's system does not see them. Whether they can be recovered depends on whether the recipient controls the key and is willing to do the work. Some exchanges will, for a fee. Many will not.

3. The address

Copy the address, paste it, and then read it back against the source: the first six characters, the last six, and ideally all of it. Two reasons:

  • Clipboard malware replaces a copied address with the attacker's at the moment of pasting.
  • Address poisoning plants look-alike addresses in your transaction history, with the same first and last characters as one you use, in the hope that you will copy the wrong line next time.

A QR code avoids typing errors. It does not prove whose address it encodes. For a hardware wallet, the address shown on the device's own screen is the one to trust, as Hot wallets vs cold wallets explains.

Some recipients need a second identifier. Exchanges that receive a given coin for all their customers at one shared address tell deposits apart with a memo or destination tag that must be entered alongside the address. A transfer that arrives without it reaches the exchange but is not credited to any account until support sorts it out, if they do.

4. The test

Send a small amount first, wait until the recipient sees it, then send the rest to the same address by the same route. The test costs one extra network fee. It checks the asset, the network, the address and the memo together, and it is the only check that does.

5. The send

Review the confirmation screen once more: asset, network, address, amount, fee. Then send, and keep the transaction ID (a long hexadecimal string, also called the hash). Anyone can look it up on a public block explorer to see whether it has been confirmed.

What an address looks like

Address formats differ by network, and the format is a quick sanity check.

What an address looks like on bitcoin and on Ethereum-style networks Address type Starts with What to know Bitcoin legacy (P2PKH) 1 Oldest format; case-sensitive Bitcoin script (P2SH) 3 Often multisignature or wrapped SegWit Bitcoin SegWit (bech32) bc1q Lower-case; built-in error detection Bitcoin Taproot (bech32m) bc1p Newest format, in use since 2021 Ethereum and EVM networks 0x Then 40 hex characters; one address on every EVM chain
Common address formats on bitcoin and on Ethereum-style networks. Source: BIPs 13, 173 and 350; ethereum.org.

Bitcoin has four formats in use. The oldest begin with 1. Addresses beginning with 3 pay to a script, defined in BIP 13, and are often multisignature wallets. Native SegWit addresses, defined in BIP 173, begin with bc1q and are written in lower case; their "bech32" encoding includes a checksum that catches mistyped characters. Taproot addresses begin with bc1p and use the revised encoding of BIP 350; Taproot has been active on bitcoin since November 2021. All four are bitcoin addresses, and a modern wallet can pay any of them.

Ethereum addresses are 0x followed by 40 hexadecimal characters. According to ethereum.org, the address is the last 20 bytes of a hash of the account's public key. The same format, and the same derivation, is used by every network built on the Ethereum Virtual Machine (EVM): Ethereum itself, its layer 2 networks and several independent chains.

That shared format is convenient and dangerous. If you control an address through your own wallet, you control it on every EVM network, so a token sent to you on the "wrong" EVM network is usually reachable by adding that network to the wallet. If the address is an exchange deposit address, only the exchange has the key, and it may not support that network at all.

One more trap on smart-contract networks: every token has a contract address, the address of the program that keeps its ledger. It appears on explorers and looks like any other address. Tokens sent to it are generally stuck for good.

Fees: what a transfer costs

Network fees pay for space in a block. They depend on how busy the network is and how much data the transaction takes up. They do not depend on the value moved.

A worked example

Prices are the Finabase closes of November 17, 2026: bitcoin $64,873.18 and ether $1,802.30. A typical bitcoin payment with one input and two outputs, in the SegWit format, is about 141 virtual bytes. A token transfer on Ethereum uses more gas than a plain ether transfer; 65,000 is used below as a round illustration, since the real figure varies by token.

Network and feerate Fee in coin Fee in dollars
Bitcoin at 1 satoshi per vB 141 sats $0.09
Bitcoin at 5 satoshis per vB 705 sats $0.46
Bitcoin at 20 satoshis per vB 2,820 sats $1.83
Bitcoin at 100 satoshis per vB 14,100 sats $9.15
Ether transfer at 0.5 gwei 0.000010 ETH $0.02
Ether transfer at 10 gwei 0.000210 ETH $0.38
Ether transfer at 50 gwei 0.001050 ETH $1.89
Token transfer at 10 gwei 0.000650 ETH $1.17
Token transfer at 50 gwei 0.003250 ETH $5.86

The feerates are chosen to show the range, not to describe today's market: fees have been far below and far above these levels at different times. Two things stand out. A $2.00 fee is 4% of a $50 transfer and 0.04% of a $5,000 one, so small transfers are the expensive ones. And a test transaction on a busy day is not free, which is a cost worth knowing before choosing a network.

Three practical notes:

  • Exchanges charge their own withdrawal fee, which may be a flat amount per coin and higher than the network fee. It is shown before you confirm.
  • Token transfers need the network's own coin for gas. Moving a stablecoin on Ethereum requires some ether in the same wallet. A wallet holding only tokens cannot send them.
  • A low fee can leave a bitcoin transaction waiting. If the feerate is below what miners are accepting, the transaction sits unconfirmed. Many wallets can replace it with a higher-fee version under the replace-by-fee rules of BIP 125. Since Bitcoin Core 30.0 (October 2025), nodes by default relay transactions paying as little as 0.1 satoshi per virtual byte, but relayed is not the same as mined.

Gas fees and their mechanics are covered in Ethereum and smart contracts.

After you send: confirmations

A broadcast transaction is first unconfirmed: seen by the network but not yet in a block. Each block that includes it or follows it adds one confirmation, and each confirmation makes it harder to undo.

Network New block about every What recipients commonly wait for
Bitcoin 10 minutes Up to 6 confirmations, about an hour
Ethereum 12 seconds Finality, about 15 minutes according to ethereum.org
Layer 2 → Ethereum exit Varies About 7 days on optimistic rollups' own bridges

Bitcoin's developer guide says software handling high-value payments should wait for at least six confirmations, and calls the number somewhat arbitrary. Each exchange sets its own requirement per coin, so a deposit can show as "pending" long after the explorer shows it in a block. That delay is the exchange's policy, not a problem with the transfer.

The seven-day figure in the last row surprises people. Withdrawing from an optimistic rollup to Ethereum through the rollup's standard bridge includes a challenge period, which Optimism's documentation puts at 7 days on its main network. Transfers within a layer 2, or through an exchange that supports the layer 2 directly, do not wait for it.

Receiving

Receiving is the same list read from the other side.

  1. Tell the sender the asset and the network, not only the address.
  2. Generate the address in your own wallet or on your exchange's deposit screen for that exact asset and network. Send it as text or QR, and ask the sender to read back the first and last characters.
  3. Include the memo or tag if the deposit screen shows one.
  4. Ask for a small test first if the amount matters.

Sharing an address is safe: it lets people pay you and look at that address's history, and nothing else. Sharing a seed phrase or private key is never part of receiving. Anyone who asks for one "to release your funds" is stealing.

Unexpected arrivals deserve suspicion too. Tokens that appear unrequested, often with a website in their name, are a common lure toward pages that ask for a signature. Ignoring them costs nothing.

Common mistakes

Mistake What happens Recoverable?
Wrong network, to your own wallet Coins sit at your address on the other network Usually, by adding the network
Wrong network, to an exchange Exchange does not see the deposit Only if the exchange agrees to recover it
Missing memo or tag Deposit arrives uncredited Often, through support, slowly
Mistyped or poisoned address Coins go to a stranger or to no one No
Token sent to its contract address Tokens locked in the contract Almost never
Fee set too low (bitcoin) Transaction waits unconfirmed Yes: replace it or wait
No gas coin in the wallet Tokens cannot be moved until gas is added Yes
Sent to a scammer who asked for it Valid, confirmed transfer No

The last row is the largest in money terms. A transfer you signed is valid, whatever you were told to make you sign it. Be especially wary of anyone who offers to recover lost crypto for an upfront fee: that is a second scam aimed at people who have already lost money once.

How Finabase does it

Finabase does not send, receive or hold crypto. It has no wallet, no deposit addresses and no withdrawal screen, and it never asks for an address or a signature. What it provides is the price side of a transfer: BTC.X, ETH.X and the rest of the crypto list show current dollar prices, which is what turns a fee quoted in satoshis or gwei into money, as in the table above. That table uses the closes Finabase recorded for November 17, 2026.

Finabase does not show network fee levels, mempool congestion or transaction status. Those come from the wallet or exchange making the transfer and from public block explorers.

Frequently asked questions

Can a crypto transaction be reversed or canceled?

Not once it is confirmed. Only the recipient can send the coins back. An unconfirmed bitcoin transaction can sometimes be replaced by its sender with a different one paying a higher fee, but that is a narrow technical window, not a refund mechanism.

What happens if I send crypto to the wrong network?

The coins arrive at the same address on the network you used. If you hold the key to that address, you can usually reach them by adding the network to your wallet. If the address belongs to an exchange, recovery depends entirely on whether the exchange supports that network or is willing to retrieve the funds manually.

Why does my deposit show as pending when the explorer says it is confirmed?

Exchanges wait for a set number of confirmations before crediting a deposit, and the number differs by coin and by exchange. One confirmation on the explorer is often not enough.

Is it safe to share my wallet address?

Yes. An address only lets others send to it and view its public history. It does reveal that history and balance to whoever you share it with, which is a privacy consideration, not a security one.

Do I pay a fee to receive crypto?

Not to the network: the sender pays the network fee. An exchange may charge its own fees on deposits or conversions, and moving the coins onward later will cost a fee of its own.

Summary

A crypto transfer is a signed, public instruction that cannot be undone once confirmed, so all the safety is in the minutes before sending. The asset, the network and the address must match on both sides, with a memo or tag where the recipient needs one, and the address should be read back against its source because malware and look-alike addresses target exactly that step. Address formats give a quick check: bitcoin addresses begin with 1, 3, bc1q or bc1p, and Ethereum-style addresses are 0x plus 40 hexadecimal characters shared across every EVM network. Fees depend on congestion and data size, not on value, so they weigh most on small transfers. A small test transaction is the one check that covers everything at once.

Check your understanding

5 questions on this lesson. Each answer comes with the reason, and nothing is scored.

  1. You withdraw a stablecoin from an exchange and choose a cheaper network than the one the receiving exchange supports. The address is correct. What is the likely result?

    1. The receiving exchange converts it automatically
    2. The coins exist at that address on the other network, where the receiving exchange does not see them
    3. The transaction is rejected and refunded
    Show the answer

    B. The coins exist at that address on the other network, where the receiving exchange does not see them An EVM address is valid on every EVM network, so the transfer succeeds. The recipient only credits deposits on networks it watches, and it holds the key, so recovery is up to the exchange.

  2. Which single step checks the asset, the network, the address and the memo all at once?

    1. Reading the first six characters of the address
    2. Scanning a QR code
    3. Sending a small test amount and waiting for the recipient to see it
    Show the answer

    C. Sending a small test amount and waiting for the recipient to see it Only an actual transfer exercises the whole route. Reading the address checks one item; a QR code prevents typos but not a wrong network or a missing memo.

  3. A bitcoin payment of about 141 virtual bytes is sent at 20 satoshis per virtual byte. Roughly how does its fee change if the amount sent is ten times larger?

    1. It is ten times larger
    2. It does not change: the fee depends on transaction size and feerate, not on value
    3. It is ten times smaller
    Show the answer

    B. It does not change: the fee depends on transaction size and feerate, not on value Fee = feerate × size: 20 × 141 = 2,820 satoshis either way. That is why fees weigh heavily on small transfers and hardly at all on large ones.

  4. Your wallet history shows an address with the same first and last four characters as one you often pay. Why should you not copy it from the history?

    1. It may be a look-alike planted by an attacker (address poisoning)
    2. Addresses expire after one use
    3. Copying from history costs a higher fee
    Show the answer

    A. It may be a look-alike planted by an attacker (address poisoning) Attackers send tiny transfers from addresses crafted to resemble yours or your contacts’. Checking only the ends of an address is exactly what the attack relies on.

  5. An exchange deposit screen shows an address and a destination tag. You send with the address only. What usually happens?

    1. The coins reach the exchange but are not credited to your account until support intervenes
    2. The coins bounce back to your wallet
    3. The network adds the tag for you
    Show the answer

    A. The coins reach the exchange but are not credited to your account until support intervenes The shared address belongs to the exchange, so the transfer is valid. The tag is how the exchange knows which customer to credit, and without it the deposit is unassigned.

Sources and further reading

  1. Bitcoin.org — Frequently asked questions (transactions cannot be reversed; confirmations)
  2. Bitcoin developer guide — Payment processing (confirmations and double-spend risk)
  3. BIP 13 — Address format for pay-to-script-hash (addresses beginning with 3)
  4. BIP 173 — Base32 address format for native SegWit outputs (bech32, “bc1”)
  5. BIP 350 — Bech32m format for version 1 and later witness addresses (Taproot)
  6. BIP 141 — Segregated Witness (virtual transaction size)
  7. BIP 125 — Opt-in full replace-by-fee signaling
  8. Bitcoin Core 30.0 release notes (default minimum relay feerate 0.1 satoshis per vB, October 2025)
  9. ethereum.org — Ethereum accounts (how an address is derived)
  10. ethereum.org — Gas and fees (21,000 gas for a transfer; base fee and priority fee)
  11. Optimism docs — Standard Bridge and withdrawal flow (7-day challenge period)
  12. Finabase chart data — BTC.X and ETH.X closes of November 17, 2026, used to convert example fees to dollars