Why does my Bitcoin-related receive address start with 0x?

What does 0x tell you—and what still needs checking?

Ethereum’s account documentation describes the 0x-prefixed account format. Other EVM networks use that format too. MetaMask’s address guidance explains that the same account address can be used across EVM networks.

The prefix helps identify an address family. It does not confirm that the intended service accepts your particular token on the network you selected. For native Bitcoin address types, Bitcoin Design’s address glossary explains the Bitcoin receive formats. Use the whole receive screen and full address rather than validating a transfer from a prefix alone.

Read a fictional receive screen

This is a label-only example, not a live Coinbase screen or a usable destination. No full wallet address or QR code is supplied.

Scroll across the table to see all columns.

Which situation are you in?

Scroll across the table to see all columns.

Why might a service show BTC with an alternative network?

Coinbase’s wrapped-assets help, checked November 12, describes eligible customers receiving supported cbBTC deposits into an underlying BTC balance. The asset selection, network selection and account policy work together. Its region and product restrictions still apply.

That example concerns a hosted service account. Holding a token in a self-custody wallet follows a separate process. The cbBTC-versus-WBTC comparison helps identify the correct product; the wrapped-token to native-BTC guide follows the conversion and withdrawal stages.

Check these five things before sending

1. Open the receiving service through its official app or website. Choose the intended account, asset and network.
2. Match that choice with the sender’s actual token and network. Clarify any mismatch before approving.
3. Read the full receiving address from that screen. Compare it with the final sender preview, including any required additional instructions.
4. Check deposit minimums, supported token identifiers, network costs and any later conversion or withdrawal conditions.
5. If a test transfer is appropriate, confirm support and minimums first and account for both transfers’ costs. Keep the original records.

Already sent to a 0x address and cannot see the funds?

Record the actual asset, source network, full destination, amount, transaction ID and time. Check the transaction on the explorer for that network. A Bitcoin explorer and an EVM explorer read different network records.

For a hosted destination, ask the receiving service about that exact asset/network deposit through verified support. For self-custody, follow the wallet’s official documentation. MetaMask’s wrong-network guidance explains why the destination and network affect available options. Recovery depends on the actual case; keep private keys and recovery phrases out of messages and recovery sites.

A useful support message is: “I sent [asset] on [network], transaction [ID], to [full destination] at [time]. My account shows [status]. Can this account accept or investigate that exact deposit, and which step remains?” Use the service’s secure channel for your real records.

What should you read next?

Use the wallet-address guide to find the intended receive screen, then the transaction-ID guide to match a transfer record. For a native Bitcoin transfer awaiting confirmations, use the transfer-time guide.

Check your account for current purchase options; the provider’s offer and eligibility checks apply. If you are planning a future purchase, the buy Bitcoin guide explains how the delivery asset and network fit the quote.