Wallet Address Formats | Wallets, Custody & Security

WALLETS, CUSTODY & SECURITY · KEYS AND ADDRESSES

Security first: Sending to the wrong address or network can be irreversible. Always verify both the destination address and the network. A string that looks valid is not proof that it belongs to the intended recipient.

QUICK NAVIGATION

CORE CONCEPT

What is a wallet address format?

A wallet address is a user-facing identifier used to receive assets or interact with accounts on a blockchain. Different networks use different encoding rules, lengths, prefixes and checksum methods.

Examples include Bitcoin address families that may begin with 1, 3 or bc1, and Ethereum-style addresses represented as hexadecimal strings beginning with 0x.

Format is network-specific: two addresses can look similar yet belong to different networks, and some networks deliberately share address formats.

HOW IT WORKS

Encoding, prefixes and checksums

An address usually represents encoded information derived from a public key, script, account or other identifier. The network may add:

a prefix or human-readable part that signals address type or network;
an encoding scheme such as Base58 or Bech32;
a checksum that helps detect some typing errors;
case conventions or mixed-case checksums;
additional destination fields such as memos or tags on certain networks.

A checksum can detect some mistakes, but it does not confirm that the recipient is trustworthy or that the network selection is correct.

PRACTICAL USE

Address verification before sending

Use the receiving wallet or exchange to generate the destination details, then verify them independently.

Safe pattern: select the asset and network on the receiving platform → copy the displayed address → verify the network on the sending platform → compare the first and last characters → where practical, send a small test transaction before the full amount.

Be careful with clipboard malware and address-poisoning attacks. Recent-transaction history can contain lookalike addresses designed to exploit partial checking.

COMPARISON

How the concepts differ

Concept	What it does	Security / practical point
Address prefix	May indicate network or address type.	Helpful clue, not sufficient proof of correctness.
Checksum	Detects certain formatting or typing errors.	Does not validate recipient identity or network choice.
Memo / tag	Additional routing identifier used by some custodial services or networks.	Omitting it can delay or prevent account crediting even if the base address is correct.

PRACTICAL WORKFLOW

A safer operating sequence

1. Generate the receiving address from the destination wallet or platform

2. Confirm the intended blockchain network on both sides

3. Copy the full address using a trusted method

4. Compare more than a few characters and beware of lookalikes

5. Use a small test transfer where the value and network fees justify it

The exact steps vary by wallet and network, but the control principle is consistent: verify what you are signing or sharing before you act.

COMMON MISTAKES

Errors to avoid

Assuming all 0x addresses belong to the same network.
Checking only the first four and last four characters when copying from transaction history.
Ignoring a required memo, destination tag or account identifier.
Trusting an address solely because the wallet accepts its syntax.
Reusing an old deposit address without checking whether the exchange still supports it.

CHECKPOINT

Can you explain it?

Why can two networks use addresses that look the same?
What does a checksum help detect, and what does it not prove?
Why can a memo or tag matter even when the base address is correct?
How does a test transaction reduce operational risk?

THOUGHT EXERCISE

Apply the idea

You are withdrawing a token from an exchange to your own wallet. Write the exact verification sequence you would follow.
Compare the risks of copying an address from a fresh receive screen versus from an old transaction history.
Explain why “the platform accepted the address” does not mean the transfer will necessarily reach the intended destination.

The aim is not to memorise jargon. It is to build a security model you can use before transferring, storing or authorising crypto.

FAQ

Frequently asked questions

❓ Why do Bitcoin addresses have different prefixes?

Different Bitcoin address types and script constructions use different encodings and prefixes. Wallet compatibility and transaction features can vary by type.

❓ Are all Ethereum-style 0x addresses compatible across EVM networks?

The same address format may exist on multiple EVM-compatible networks, but assets and transaction state are network-specific. You must still choose the correct network.

❓ What is an address checksum?

It is validation information intended to catch certain accidental errors in an address representation. It does not verify who controls the address.

❓ Should I always send a test transaction?

A test can reduce operational risk, especially for large or unfamiliar transfers, but it adds fees and does not eliminate all risks. The decision should reflect value, network cost and confidence in the workflow.

SUMMARY

Key takeaways

Address formats differ by network, encoding and address type.
A syntactically valid address can still be the wrong destination or wrong network.
Checksums help catch some errors but do not prove ownership.
Network, address and any required memo/tag should be verified as one complete destination.