Receiving Crypto Safely

Receiving crypto is the easiest thing you will do in a wallet, right up until a sender picks the wrong network from a dropdown. The wallet doesn't prevent that. Your job as the receiver is to hand over three things the sender cannot guess: the correct address, the matching network, and (for some chains) a memo. Get those right and funds land in Zelcore in seconds. Miss one and there is usually no undo.

This guide walks through how to receive crypto safely using Zelcore — what to check before you share an address, how to spot chain-specific prefixes, the exact six-step receive flow, and how to recover (or at least diagnose) the four failures that catch every beginner.

Before You Start

You should already have Zelcore installed, your wallet set up, your seed backup verified, and the coin you want to receive enabled in your asset list. If any of that is missing, fix it first — receiving to a wallet you cannot recover is worse than not receiving at all.

Receiving is free from your side. The sender always pays the network fee. But "free" doesn't mean "safe": picking the wrong address format makes the coins unrecoverable on many chains, not just expensive.

Before you share any address, answer three questions:

1. Which coin am I receiving? USDT is not USDC. WBTC is not BTC.
2. On which chain? USDC exists on Ethereum, Solana, Polygon, Base, Arbitrum, Tron, and more — each is a different ledger.
3. Does this chain require a memo or destination tag? XRP, XLM, TON, HBAR, Cosmos, and BNB Beacon Chain deposits to exchanges all do.

A useful mental model: the address proves who receives, the network proves on which ledger, the memo proves which sub-account. A crypto address is a public-key derivative and is safe to share — but only into the right context.

The Address-Format Zoo

You don't need to memorise every format, but you should recognise the prefix of whatever you're receiving. A wrong prefix is the cheapest error to catch.

• Bitcoin legacy (P2PKH) — starts with 1 (e.g. 1A1zP1…). Still valid, costs the sender more in fees.
• Bitcoin SegWit-wrapped (P2SH) — starts with 3. Backwards-compatible, modest fee savings.
• Bitcoin native SegWit / Taproot (bech32, bech32m) — starts with bc1. bc1q… is SegWit v0, bc1p… is Taproot. Defined in BIP-173, lowercase only, with a BCH-code checksum that guarantees detection of any error affecting up to four characters. This is what Zelcore hands you by default.
• Ethereum and every EVM chain (Polygon, BNB Smart Chain, Arbitrum, Optimism, Base, Avalanche C-Chain) — all use the same 0x-prefixed 42-character hex address. The address is identical across chains. The chain is chosen by the sender's "network" dropdown, not by the address.
• Solana — base58, 32–44 characters, no fixed prefix, case-sensitive. SPL USDC on Solana and ERC-20 USDC on Ethereum are different tokens on different ledgers.
• Tron — starts with T. Cosmos/Osmosis — cosmos1… / osmo1…. Cardano — addr1…. Litecoin — L, M, or ltc1…. Dogecoin — D.
• Memo-field chains — XRP starts with r, XLM with G, TON and HBAR have their own formats. When depositing to a centralised exchange on any of these, the exchange gives you a shared address plus a unique memo. The address alone routes to the exchange's pooled wallet; the memo tells them which customer to credit.

Receiving in Zelcore: The Six-Step Flow

1. Open Zelcore and unlock. Confirm you're on the main wallet and not a secondary profile.
2. Tap the asset you want to receive from your asset list. If it isn't there, open Manage Assets and enable it first.
3. Tap Receive. Zelcore displays the current deposit address plus a QR code. For Bitcoin and other UTXO chains, Zelcore rotates to a fresh address each time for privacy — this is expected, and old addresses still work.
4. Show the QR, or tap Copy. Prefer the QR: a scan is atomic and has no clipboard in the middle. If the sender must type, read the first four and last four characters aloud.
5. Verify the prefix matches the sending chain. If you asked for USDC on Solana, the address must be base58 without a 0x. If the sender's dropdown reads "Ethereum (ERC-20)" but you gave them a Solana address — stop, pick one or the other, and start over.
6. Include the memo or destination tag for XRP, XLM, TON, HBAR, Cosmos deposits to exchanges, or any memo-requiring token. For any first-time send over a few hundred dollars, run a minimum-amount test transaction first.

You'll Know It Worked When…

The pending balance appears in Zelcore within seconds to a few minutes. It will sit under "pending" or "unconfirmed" until the network has reached its required confirmation depth, then shift into your confirmed balance.

If you want independent confirmation that doesn't depend on a single wallet's view of the world, paste your address into the relevant block explorer: mempool.space for BTC, etherscan.io for Ethereum and ERC-20, solscan.io for Solana, bscscan.com for BSC, tronscan.org for Tron. The incoming transaction and its confirmation count appear immediately.

Rough confirmation targets: 1–3 blocks for small Bitcoin amounts and 6 for large; 12–20 blocks on Ethereum; near-instant on Solana. Centralised exchanges may wait 20–200 blocks before they credit your account — that's their policy, not your wallet's problem.

If the explorer shows success but Zelcore hasn't updated, pull down to refresh the asset screen or restart the app. Zelcore reads from public nodes and occasionally lags 30–60 seconds.

If Something Goes Wrong

Wrong-network send. The single biggest beginner disaster. When withdrawing from Binance, Coinbase, Kraken, or OKX, the dropdown labelled "Network" offers Ethereum (ERC-20), BNB Smart Chain (BEP-20), Polygon, Arbitrum, Tron (TRC-20), Solana, and more. Picking BNB Smart Chain because it's cheaper, then sending to an Ethereum-only address, puts funds on a chain your wallet doesn't watch. Recovery is sometimes possible when the two chains share a key format — all EVM chains share the same 0x address and private key, so ETH accidentally sent as BEP-20 can usually be recovered by importing your Zelcore seed into a wallet that watches BSC. Recovery is not possible when chains are fundamentally different, like SPL USDC sent to an ERC-20 USDC address. Rule: the sender's "Network" dropdown must match the chain of the address you shared.

Missing memo or destination tag. The XRP, XLM, TON, and HBAR trap. Most centralised exchanges pool all customer deposits into a single shared wallet; the memo is the only thing that tells them which customer the incoming tokens belong to. Exchanges enforce the tag on withdrawals, not always on deposits. If you send without the memo, open a support ticket with the transaction hash — some exchanges recover these for a fee, many don't.

Stuck at 0 confirmations. Almost always a fee problem on the sender's side, not yours. On Bitcoin during mempool congestion, a low-fee transaction can sit for hours or days. Ask the sender to use Replace-by-Fee (RBF) to bump the fee, or wait — unconfirmed Bitcoin transactions eventually drop from the mempool after roughly two weeks, and the coins return to the sender untouched.

Address poisoning. This one targets your habits, not Zelcore. An attacker sends a zero-value or dust transaction from a wallet whose first four and last four characters visually match one of your real counterparties. The next time you copy an address from your transaction history, you grab the lookalike. Chainalysis documented a single 2024 campaign that seeded 82,031 lookalike addresses from 8 attacker-controlled seeder wallets; 2,774 victims sent funds, totaling roughly $69.7M in initial losses — one victim lost $68M in wrapped bitcoin before the attacker returned it, leaving the scammer a net ~$3M (3,727x the 2024 median scam profit). Academic research found more than 252 million poisoning transfers on BNB Smart Chain alone, targeting about 16 million victim addresses. Three defences: never copy addresses from your transaction history (copy from the Receive screen or a saved address book entry), verify the middle characters and not just the ends, and run a minimum-amount test transaction for any send over about $500. This is part of a broader pattern covered in our attack-surface guide, and fits into the general safe-habits checklist every self-custodian should internalise.

A 30-Second Pre-Send Checklist You Can Paste to the Sender

• Coin matches — same ticker you asked for (USDT is not USDC; WBTC is not BTC).
• Network matches — their "Network" dropdown matches your address prefix.
• Address matches character-by-character — first four, middle four, last four.
• Memo included if required — XRP, XLM, TON, HBAR, and any exchange deposit.
• Test transaction first for any amount you'd regret losing.

Key Takeaways

• The address answers who; the network answers which ledger; the memo answers which sub-account. All three must be right.
• EVM addresses are identical across Ethereum, Polygon, BSC, Arbitrum, Optimism, Base, and Avalanche C-Chain — the sender's network dropdown decides where the funds land.
• Memo-field chains (XRP, XLM, TON, HBAR) pool deposits at exchanges. No memo, no automatic credit.
• Never copy an address from your transaction history. Always copy from the Receive screen or a verified address-book entry.
• Run a test transaction for any amount you couldn't afford to lose.

Receiving is the defensive half of moving crypto — the half where mistakes are made by the other person. Part 4 flips that: sending crypto, picking the right fee for the chain and the moment, and signing without giving away more permission than you intended.