Wallet address formats show where a transfer can go

Wallet address formats matter because they tell wallets and networks how to identify a destination, but an address alone may not tell you which chain to use. Before sending, check that the destination supports the network and asset you have selected.

What does a wallet address format tell you?

A format reflects how a blockchain represents an account or spending destination. Bitcoin addresses use formats such as legacy addresses beginning with “1” or “3” and SegWit addresses beginning with “bc1”; Ethereum-style addresses start with “0x” and contain 40 hexadecimal characters after it.

These differences help software validate and handle addresses, but they are not a universal label for the network. A checksum can help catch mistyped characters: Ethereum’s mixed-case checksum encoding, for example, uses capitalization to signal some errors. It does not confirm that the address is on the right chain. When a wallet route includes a swap, thor swap explains how to use one from your own wallet.

Why can the same address mean different things across chains?

Several networks that use Ethereum’s address system can show the same address for a wallet, because they can derive it from the same key. That shared appearance does not make the networks interchangeable: a transfer on one chain does not automatically arrive as a usable balance on another.

Other chains use different address encodings. Solana addresses, for example, are commonly shown as base58 strings rather than Ethereum’s hexadecimal form. A wallet may also support only certain address types or networks, and a service accepting a deposit may credit only assets sent over its listed networks. The destination address can look valid while the selected chain is unsupported.

How should you check an address before sending?

Check the network and asset shown by both the sending wallet and the receiving wallet or service. Then compare the full address, not just its first and last characters, and follow any network-specific instructions from the recipient.

• Confirm the selected chain on both sides of the transfer.
• Check that the destination supports the exact asset and network combination.
• Copy the address from the recipient and verify it after pasting.
• For an unfamiliar destination, send a small test amount first if fees and minimums allow.

For most users, the safest check is the receiving service’s deposit instructions: match its named network exactly, even when the address looks familiar. If the recipient does not support the chosen chain, stop and ask it which network to use before sending.