To receive CRO, share the address that matches the network the sender uses: a cro address for Cronos POS, a 0x address for Cronos EVM, or your exchange's deposit address with any memo. To send, paste and verify the address, pick the matching network, keep some CRO for gas, confirm, and check the explorer before you trust it.
The reason the address alone is not enough is that CRO lives on more than one chain. Native CRO sits on the Cronos POS chain and uses addresses that start with cro, the Cronos EVM chain uses 0x addresses like Ethereum, and an older version trades as an ERC20 token on Ethereum itself. Same coin, same value, but three different destinations, so the coin you picked up after following how to buy CRO decides which network you send and receive on.
Get the network right on both ends and this is routine. Get it wrong and the coins can be gone for good, which is why every step below comes back to matching the network.
First, match the network on both ends
Before you copy an address, decide which chain the CRO is moving on, because the address type and the network you pick must agree on both ends. A cro address means Cronos POS, a 0x address means Cronos EVM or Ethereum, and an exchange deposit address means whatever network it supports. Match them, and the rest is easy.
| Where the CRO is going | Address form | Network to choose | Memo or tag? |
|---|---|---|---|
| Your own Cronos EVM wallet (apps, DeFi) | starts with 0x | Cronos EVM | No |
| Your own Cronos POS wallet (holding, staking) | starts with cro | Cronos POS | No |
| An exchange deposit address | 0x or cro, as the exchange shows | the one network that exchange lists for CRO | Often yes for native CRO |
| An Ethereum wallet or ERC20-only service | starts with 0x, on Ethereum | Ethereum | No |
The value of CRO is the same whichever chain it sits on, so this is never about the amount, only the route (source: Ledger). Native CRO on the Cronos POS chain uses cro addresses, the Cronos EVM version uses 0x addresses, and the Ethereum ERC20 version also uses a 0x address but on a different network. The habit that protects you is to confirm which chain an address is on before you move anything, because the coin's name alone will not tell you.
If that split still feels fuzzy, the overview of how the Cronos chains work shows what each chain does. And if you have moved coins before, the general shape here matches sending and receiving any crypto, just with CRO's extra wrinkle that one coin spans several chains.
How to receive CRO on the right network
To receive CRO, get your address from the wallet or exchange that will hold it, confirm which chain that address belongs to, and tell the sender to use that network. If it starts with cro, that is Cronos POS; if it starts with 0x, that is Cronos EVM or Ethereum. Name the chain, not just the coin.
- Open the wallet or exchange account that will receive the CRO and find its receive or deposit screen.
- Copy the address and note the chain it is labeled with. In Keplr or a Cronos POS wallet, that is a cro address ready to receive native CRO (source: Cronos POS Chain Docs); in MetaMask on Cronos, it is a 0x address.
- On an exchange, pick the CRO network first, then copy the deposit address it shows for that network, since the same account can list more than one.
- If you are depositing native CRO to an exchange, check whether it also asks for a memo or tag, and copy that too. It is part of the destination, not an optional note.
- Give the sender the address and any memo, or show the QR code, and confirm the network. The CRO appears once that network confirms the transfer.
A memo, sometimes called a tag, is a short code that a shared deposit address uses to route your CRO to the right account, so it matters most when you receive native CRO into a centralized exchange. A personal wallet like Keplr or MetaMask does not need one. Treat a required memo as part of the destination and hand it over with the address.
One case trips up beginners more than any other on the receive side: the exchange that only supports one network. Some centralized exchanges let you withdraw or deposit only the Ethereum ERC20 version of CRO, so you would need a 0x address on Ethereum rather than a Cronos one (source: Cronos Bridge Docs). Read the network list on the screen before you share an address. If you have received Solana before, this is the same shape as sending and receiving Solana, with the network choice carrying the risk.
How to send CRO safely, step by step
To send CRO, paste the recipient's address, verify it character by character, choose the network that matches that address, and make sure you hold a little CRO for the network fee. Then confirm the amount and network on the review screen, send, and check the transaction on the explorer before you assume it arrived.
- Copy the recipient's address straight from their wallet or the exchange deposit screen. Never retype it by hand, and treat any address pasted into a chat or email as suspect.
- Verify the address by its first and last characters after you paste it, because malware can quietly swap a copied address for an attacker's. Scanning a QR code lowers that risk.
- Pick the network that matches the address: Cronos EVM for a 0x on Cronos, Cronos POS for a cro address, or Ethereum for a 0x you were told is on Ethereum.
- Keep some CRO in the sending wallet for gas. On Cronos EVM the fee is paid in CRO, so a wallet holding other tokens but zero CRO cannot send anything until you top it up.
- Add the memo or tag if the receiving service asked for one, then open the review screen and check the amount, the network, and the address one more time.
- Confirm the transfer, then find it and check it on the block explorer, and wait for the status to read confirmed before you consider it done.
Before you approve a first-time destination, keep the recipient's receive screen open and compare it with the transfer review screen. First, check that the full address is identical, including the first and last characters. Next, check that the network label names the same chain in both places, not merely the same coin. Finally, if the receiving service asks for a memo or tag, make sure it is displayed with that same address and network, not copied from an earlier deposit. This two-screen check catches an address from the wrong account, a deposit screen left on a different network, or an out-of-date saved recipient. If a recipient uses more than one wallet or exchange account, make them confirm which account owns the address before you send. A copied address is useful only when it stays paired with that network and destination. If anything differs, cancel the draft, ask the recipient for a newly generated deposit address, and repeat the comparison before you send.
If the network you need is not in your wallet yet, add it before you send, not in a rush at the last second. A wallet that shows only Ethereum, for example, cannot send on Cronos EVM until that network is set up, and forcing the transfer anyway is how coins end up on the wrong chain.
The review screen is your last cheap chance to catch a mistake, so read it rather than tapping through. A transfer that has left your wallet is final, while a mismatched network caught at review costs nothing to fix. If you are sending a large amount, do the whole sequence once with a small amount first, and let it land before you send the rest.
The number-one mistake: wrong network or wrong address type
The single most expensive mistake is sending CRO on the wrong network or to the wrong address type, and it happens so often because the address types look alike. A 0x address on Cronos EVM has the same shape as one on Ethereum, yet they are different destinations on different chains. Matching the coin name is not enough.
This is the trap the CRO forms create. Native CRO on Cronos POS, CRC20 CRO on Cronos EVM, and ERC20 CRO on Ethereum are separate assets on separate chains, even where two of the addresses look identical (source: Cronos POS, EVM & zkEVM FAQ). So before you confirm, ask which chain the address is really on, and pick that network by name rather than trusting how the address looks.
There is one more network to avoid entirely. The Cronos zkEVM is being retired, with a permanent shutdown set for 2027, so do not send CRO to it, since anything stranded there after the deadline may be unrecoverable (source: Cronos Labs). When you add or select a network, choose the main Cronos EVM chain, not the zkEVM that is winding down.
From BloFin's operational view, make the network and address a single check, not two separate ones. Confirm the chain named on the recipient's deposit or receive screen, then make sure that exact chain is selected in your send screen before you approve the transfer.
If CRO does land on the wrong chain or a wrong address, there is usually no undo button, and the Cronos Labs team cannot reverse a transaction or recover funds sent in error (source: Cronos EVM Docs). That is the whole case for the small test transfer: a test costs a fraction of a cent, while a wrong-network send can cost the entire balance.
What to do if a transfer doesn't arrive
If CRO does not show up, do not resend it right away. Find the transaction on the block explorer using its hash, read whether it is pending or confirmed, and check which chain it actually reached. Most missing transfers are still confirming or sitting on a different network, not truly lost, so diagnose before you act.
Keep the transaction hash and a screenshot of the send, because any support team will ask for them first. Where it landed decides what you can do next. If the CRO went to an address you control on the wrong chain, you may be able to recover it by importing that wallet's recovery phrase into a wallet that supports the chain the coins actually reached, then moving them from there. If it went to an exchange, on an unsupported network or without a required memo, you cannot fix it yourself; contact that exchange's official support with your transaction hash and let them trace it. Recovery is not guaranteed either way, which is exactly why the checks come first.
Keeping a wallet safe across several chains is its own skill, and the wider habits, from verifying addresses to spotting fake approval prompts, live in the guide to multi-chain wallet security. Build those in early, and sending and receiving CRO becomes a routine you can trust rather than a gamble each time.
Frequently asked questions
Can I send CRO from Cronos EVM straight to a Cronos POS address?
No. Cronos EVM (0x) and Cronos POS (cro) are separate blockchains, so a plain transfer between them fails or sends your CRO to an address that cannot receive it. To move CRO from one Cronos chain to the other, you bridge or convert it through a service that supports both, rather than pasting a cro address into an EVM send. If a wallet even lets you attempt it, stop and use a bridge instead, because a direct cross-chain send is one of the ways people lose coins.
Do the sender and I need to use the same wallet app?
No. Wallets are interoperable, so someone on the Crypto.com Onchain Wallet can send to your MetaMask, and Keplr can send to a Ledger, as long as both sides use the same network and address format. What matters is the chain and the address type, never the brand of app. Do not assume you must install whatever wallet the sender uses; give them your address and the network, and any compatible wallet will reach it. The network agreement is the real requirement.
Is it safe to share my CRO receive address, and can I reuse it?
Yes on both counts. A receive address is public by design: it lets people send you CRO but gives no one the power to take it, so you can post it, message it, or reuse the same one for every deposit. The secret that must never leave your control is your recovery phrase, not your address. The one habit worth keeping is verifying the address each time you paste it, because malware can swap what sits on your clipboard, even for an address you have used many times before.
What should I do if my wallet says the CRO address is invalid?
Do not try to edit the address to make it fit. Ask the recipient to open the receive screen again, select the intended network, and send you a newly copied address or QR code from that screen. An invalid cro or 0x address can mean the wrong network is selected, the address was copied incompletely, or the sender has a stale recipient record. Resolve that mismatch before submitting anything, rather than guessing which chain the recipient intended.
Does my wallet need to be open to receive CRO?
No. CRO is sent to an address on the selected chain, not to a wallet app that must be running, so the recipient's wallet can be closed or their hardware device disconnected. The sender still needs the correct address, network, and any required memo. When the recipient opens their wallet later, they should select the same network and use the transaction hash or explorer if the balance does not appear immediately.
What is a transaction hash, and how is it different from an address?
An address is where CRO goes and can be reused for many transfers; a transaction hash is the unique receipt for one specific transfer. After you send, your wallet gives you that hash, a long string of characters, which you paste into the matching block explorer to watch the transfer confirm and to prove it happened. Think of the address as the mailbox and the hash as the tracking number for a single package sent to it.
Why is my CRO transfer confirmed but not in my exchange balance?
Yes. A confirmation shows the transfer reached the blockchain, but an exchange may still need time to process and assign the deposit to your account. Confirm that the address, network, and memo match the active deposit screen, then wait for the exchange's stated processing period. If it remains uncredited after that, give the transaction hash to official support. Do not send another deposit just to test whether the first one will be credited.
Researched and written by the BloFin Academy editorial team with AI-assisted drafting. Updated July 2026. Primary sources: the Cronos documentation, the Cronos POS Chain documentation, Ledger support, the Cronos Labs blog, the crypto-org-chain project on GitHub, and the BloFin market API.
This article is educational and general in nature, not financial or investment advice. Cryptocurrencies like CRO carry real risks, including price volatility, smart-contract bugs, custody mistakes, and the chance of losing funds sent on the wrong network or to the wrong address. Self-custody means you alone are responsible for your keys and recovery phrase. Nothing here is a recommendation to buy, sell, hold, or trade any asset. Do your own research, and consider a licensed professional before making financial decisions. BloFin does not provide investment advice.