Lesson Objective
The asset and the network are separate choices
A crypto asset is the unit being transferred. The network is the blockchain that records the transfer. Some assets exist only on one blockchain, while others have native, issued, bridged or wrapped versions on several networks.
Selecting USDC, ETH or another familiar ticker does not finish the decision. The sender must also select the exact network supported by the destination. Both sides need to agree on the asset version and blockchain route.
The Four-Part Match
Why the same asset appears on several networks
An issuer may create a native version of its token on several supported blockchains.
A bridge may lock or burn an asset on one network and create a representation on another.
An exchange may support deposits and withdrawals for the same ticker over several networks.
A blockchain may use a token standard that gives the asset a network-specific contract or mint address.
Wallet interfaces may combine several network balances under one asset name, making the distinction less visible.
Common network families
| Network | Address / token characteristic | Typical fee asset |
|---|---|---|
| Bitcoin | Bitcoin addresses and UTXO-based transactions; not an EVM token network. | BTC |
| Ethereum | Native ETH plus tokens identified by Ethereum contract addresses. | ETH |
| EVM-compatible networks | Often use 0x-style addresses, but each network has separate state and token contracts. | Network-specific native asset |
| Solana | Base58-style addresses; tokens are identified by a unique mint address. | SOL |
| XRP Ledger | XRP addresses; some hosted destinations require a destination tag. | XRP |
| Stellar | Stellar accounts; exchanges may require a memo for correct customer crediting. | XLM |
Address Appearance Is Not Proof
Sender support and recipient support
A successful blockchain transaction and a successful account deposit are not always the same outcome. The network may record the transfer correctly while an exchange or custodian does not credit it because the chosen network or token version is unsupported.
| Sender must confirm | Recipient must confirm |
|---|---|
| The asset and network are available for withdrawal. | The same asset and network are available for deposit. |
| The displayed fee and minimum are acceptable. | The deposit meets any minimum and confirmation requirements. |
| The destination address and any memo or tag are entered correctly. | The address, memo or tag was generated for this account and network. |
| The token version is native or bridged as expected. | The receiving service accepts that exact contract or mint. |
| The destination is not a contract or unsupported account type. | The receiving platform can process the incoming transaction type. |
Network labels can be confusing
ERC-20: Usually indicates an Ethereum token standard, but similar token interfaces also exist on other EVM networks. Always read the named network.
BEP-20: Generally refers to tokens on BNB Smart Chain and should not be treated as an Ethereum deposit route.
Polygon: A separate network from Ethereum, despite address-format compatibility and links to the Ethereum ecosystem.
Arbitrum or Optimism: Ethereum Layer 2 networks with their own balances and deposit routes.
SPL: A Solana token standard; the token is identified by a Solana mint address.
Native, bridged and wrapped versions
An asset name may refer to economically related but technically different tokens. Native issuer-created USDC, bridged USDC and another wrapper representing USDC can have different contracts, redemption routes and acceptance.
| Version | How it arises | Verification need |
|---|---|---|
| Native blockchain asset | Built into the blockchain protocol, such as ETH on Ethereum. | Confirm the correct blockchain and destination. |
| Issuer-native token | The issuer creates an official token contract or mint on a supported chain. | Verify the issuer's supported-chain list and token identifier. |
| Bridged token | A bridge creates a destination-chain representation of an asset from another chain. | Identify the bridge, backing, contract and recipient support. |
| Wrapped token | A contract or custodian issues a representation in another format or environment. | Confirm the wrapper and redemption mechanism. |
Contract and mint addresses identify tokens
Names and symbols are not unique. Anyone may create a token with a familiar name. On smart-contract networks, the contract or mint address is the reliable technical identifier for a specific token on that network.
Obtain the identifier from the issuer, network documentation or another authoritative source.
Confirm the blockchain before comparing the identifier.
Do not rely only on a logo, ticker, wallet search result or unsolicited link.
Be cautious when a wallet displays an unexpected token; spam tokens may appear without being requested.
The safe transfer sequence
Ask the destination. Open the receiving wallet or platform and select Deposit or Receive for the intended asset.
Select the network there. Record the exact supported network name, address and any required memo or tag.
Match the sender. On the sending platform, select the identical asset and network — not merely the lowest fee.
Verify the token version. When relevant, compare the contract or mint address with an authoritative source.
Confirm the address. Copy and paste or scan the QR code, then compare the first and last characters on a trusted screen.
Review fees and minimums. Ensure the received amount will meet platform requirements after applicable charges.
Send a small test. Use a modest amount first when the address, asset, network or service is new.
Verify receipt. Wait for required confirmations and confirm that the destination credits the asset before sending more.
Recipient Information Governs
Memos, tags and account identifiers
Some custodial platforms use one blockchain address for many customers and rely on a memo, destination tag or similar identifier to assign each deposit. The transaction can reach the platform's address but remain uncredited if the identifier is missing or wrong.
Copy the memo or tag exactly when the deposit page requires it.
Do not reuse old instructions without confirming they remain valid.
A self-custodial wallet may not require a memo even when an exchange deposit does.
If a memo is omitted, contact the receiving platform only through its official support channel.
A test transaction reduces — but does not remove — risk
A test verifies that the current asset, network, address and deposit process work for a small amount. It cannot prove that every later transaction will succeed, and it adds another fee, but it is often sensible when sending a material amount or using a destination for the first time.
After the Test
What happens on the wrong network?
| Situation | Possible outcome |
|---|---|
| Self-custodial recipient controls keys on a compatible EVM network | The asset may be accessible by configuring a wallet for that network, but token support and gas are still needed. |
| Exchange or custodian does not support the selected network | The blockchain transfer may succeed but the platform may not credit or recover it. |
| Asset sent to an incompatible address format | The wallet may block the transaction, or the transfer may be unrecoverable depending on the network. |
| Correct network but wrong or missing memo/tag | The platform may hold the asset without knowing which customer to credit; recovery may require support and fees. |
| Wrong token contract on the correct network | A similarly named or bridged token may arrive but remain unsupported or have different value and redemption rights. |
If a mistake occurs
Do not send another transaction in an attempt to reverse the first.
Record the transaction hash, network, asset, amount, destination and time.
Use the correct blockchain explorer to confirm whether the transaction succeeded.
Determine who controls the destination address and whether the asset is visible there.
Contact the receiving service through its official website or application — not through unsolicited direct messages.
Never give a recovery phrase or private key to someone offering recovery assistance.
Understand that recovery may be impossible, delayed or subject to fees and identity verification.
Recovery Scams
Common network mistakes
Choosing the cheapest withdrawal network without checking recipient support.
Assuming all 0x addresses refer to Ethereum.
Treating native and bridged versions as interchangeable.
Using a token ticker instead of verifying its contract or mint address.
Forgetting a required memo or destination tag.
Sending the full amount without first testing a new route.
Using deposit instructions found in an old email or screenshot.
Believing blockchain success guarantees that a custodial account will be credited.
Network controls for organizations
Maintain an approved list of assets, networks, token contracts, custodians and destination addresses.
Require independent verification of new addresses, memos and network selections.
Use test transactions and transaction limits for new routes.
Separate preparation, approval and post-transfer reconciliation where practical.
Document bridge use and distinguish native, bridged and wrapped balances.
Monitor changes to exchange deposit support and issuer-supported chains.
Retain transaction hashes, screenshots of approved instructions and accounting records.
Accounting Perspective
Final pre-send checklist
Exact asset confirmed
Exact receiving network confirmed
Sender network matches recipient network
Token contract or mint verified when applicable
Destination address checked on a trusted screen
Memo or tag included when required
Fees, minimum deposit and received amount reviewed
Small test completed for a new or material transfer
Native fee asset retained for future activity
Key takeaways
The asset and the blockchain network are separate parts of a transfer.
Sender and recipient must support the same asset version on the same network.
Similar-looking addresses do not prove network compatibility.
Contract or mint addresses distinguish genuine token versions from look-alikes.
A successful blockchain transaction may still be uncredited by an unsupported custodian.
A test transfer and a disciplined checklist can reduce preventable errors.
Quick knowledge check
Why is selecting the correct asset ticker not enough to make a safe transfer?
Why can one 0x address appear valid on several networks?
What distinguishes two tokens with the same name on one blockchain?
Why can an exchange fail to credit a transaction that succeeded on-chain?
What information should be recorded before contacting support about a mistaken transfer?
Glossary
- Blockchain network
- The distributed system whose rules and ledger process a transaction.
- Contract address
- The unique blockchain address identifying a specific smart-contract token on a network.
- Destination tag / memo
- Additional information used by some custodial platforms to assign a deposit to a customer.
- Mint address
- On Solana, the unique identifier defining a particular token.
- Native asset
- An asset built into a blockchain protocol and commonly used to pay network fees.
- Test transaction
- A small preliminary transfer used to verify a route before sending more.
- Transaction hash
- A unique identifier used to locate a blockchain transaction.
Sources and further reading
Editorial note: This lesson was independently written for Fichtner Digital and synthesizes the cited sources in original language. It does not reproduce substantial passages from them. Facts and links last reviewed 22 July 2026.
Educational purposes only. Not financial advice. Asset and network support can change. Blockchain transactions may be irreversible, and recovery of an incorrect transfer is not guaranteed. This material does not constitute financial, legal, accounting, tax or investment advice.