Entries → comparison tables
Address Formats: A Reference Table
How to identify which network an address belongs to, and which formats are shared between chains.
| Entry type | reference |
|---|---|
| Section | comparison tables |
| Last verified | |
| Compiled by | Reference Desk |
Entry last verified May 2026.
Identifying a format
| Pattern | Networks |
|---|---|
| Begins with a hexadecimal prefix, 42 characters total | Ethereum and every compatible chain |
| Begins with 1 or 3, base58 | Bitcoin legacy and script addresses |
| Begins with bc1, bech32 | Bitcoin native segwit |
| Begins with ltc1 or L or M | Litecoin |
| Base58, 34 characters, begins with T | Tron |
| Base32, no checksum prefix visible | Several newer chains, format varies |
The critical case is the first row. Ethereum-format addresses are identical across dozens of networks, which means the address alone cannot tell you which chain it belongs to.
The consequence
Sending an asset to the right address on the wrong network is the most common expensive error in crypto, because the address gives no warning.
The network is chosen in a dropdown, usually positioned away from the address field, and it is the field that determines whether the funds arrive.
The checksum
Most formats include a check within the string. A mistyped character produces an invalid address and the wallet refuses to send.
That protects against the majority of typos. It does not protect against a typo producing a different valid address, which is rare and permanent.
What is recoverable
| Situation | Recoverable |
|---|---|
| Same address, different compatible network, you control the key | Yes, add the network in your wallet |
| Sent to a venue on an unsupported network | Sometimes, via support, slowly |
| Sent to a non-compatible chain | Generally no |
| Sent to a contract that cannot forward it | Usually no |
| Valid address you do not control | No |
The prevention
Check the network before the address.
Confirm the destination supports that network for that asset. Support is per asset, not just per venue.
Send a test transaction. Small amount, confirm arrival, then send the rest. This catches every row in the table above while the amount at risk is trivial.
Where to check network support
Venues publish which networks they support for deposit and withdrawal, per asset. Platforms listing this alongside fees, such as venues where the asset is listed for retail purchase, make the check a single page.
Wallets publish the same for what they can display. Checking both ends before sending is the whole procedure.
Figures in this entry were correct on the date shown. Spotted something out of date?Send a correction and the entry gets updated.