Bitcoin, Ethereum and Solana address formats
A wallet address has a network-specific encoding. Ethereum normally uses 0x plus 40 hexadecimal characters; Bitcoin has several address families; Solana encodes 32-byte account addresses in base58.
Worked example
| System | Illustrative shape | Meaning |
|---|---|---|
| Ethereum / EVM | 0x + 40 hex characters | 20-byte address; chain still needed |
| Bitcoin mainnet | 1…, 3…, bc1q…, bc1p… | Different output/address families |
| Solana | Base58 text, usually 32–44 characters | 32-byte account address; role needs lookup |
How to compare a receive screen
Read the asset and network labels before inspecting characters. A shared prefix is weaker evidence than the network selected by the receiver. Bitcoin address families describe how an output can be spent; EVM 0x does not encode a network; Solana account text does not identify the account role.
Worked comparison
If a service offers USDC on Ethereum and Solana, the ticker alone cannot select a destination. Open the recipient’s deposit instructions for the exact network and asset. Treat the shapes in this table as annotations, not complete destinations.
Common pitfalls
- Truncated shapes containing … are placeholders, not valid addresses.
- An address accepted by a format checker may still be the wrong recipient or network.
Related references
Primary sources
Examples explain identifiers. They are not investment recommendations.