Wallet Address Validator
Validate Ethereum/EVM, Bitcoin, and Solana wallet addresses. Auto-detects network, verifies EIP-55 checksum, address type, and format. Supports batch validation.
Wallet Address
Supported Address Formats
This validator supports the three major blockchain address formats used across the majority of DeFi, NFTs, and Web3 applications. Each network has a distinct encoding scheme, prefix convention, and length requirement that allows reliable auto-detection.
| Network | Prefix | Length | Encoding | Checksum |
|---|---|---|---|---|
| Ethereum / EVM | 0x | 42 chars | Hex | EIP-55 mixed-case |
| Bitcoin Legacy (P2PKH) | 1 | 25–34 chars | Base58 | Base58Check |
| Bitcoin P2SH | 3 | 25–34 chars | Base58 | Base58Check |
| Bitcoin Bech32 (SegWit) | bc1 | 42 or 62 chars | Bech32 | BCH code |
| Solana | none | 32–44 chars | Base58 | none |
Understanding Wallet Address Checksums
A checksum is a mechanism that lets software detect whether an address has been accidentally corrupted — for example by a typo, a copy-paste truncation, or a character substitution. Different blockchains implement checksums differently.
Ethereum EIP-55
Capitalises specific hex letters in the address based on the Keccak-256 hash of the lowercase version. Wallets that support EIP-55 will reject or warn about checksummed addresses with incorrect capitalisation.
Bitcoin Base58Check
Appends a 4-byte SHA-256 checksum to the payload before Base58 encoding. Any single character corruption will almost certainly fail the checksum, making Bitcoin addresses highly resistant to transcription errors.
Bech32 BCH Code
Bitcoin's native SegWit (Bech32) format uses a BCH (Bose–Chaudhuri–Hocquenghem) error-detecting code that can detect any single character error and most multi-character errors, while also being human-friendly (no ambiguous characters).
Common Address Mistakes and How to Avoid Them
Sending funds to a wrong address is usually irreversible. Understanding the most common mistakes helps prevent costly errors in production.
Wrong network
An Ethereum address and a Polygon address look identical — they both start with 0x. Always confirm the network in your wallet before signing. Use a bridge if you sent assets to the wrong chain.
Truncated address
Some UIs display a shortened address (0x1234...abcd). Never send to a truncated address. Always expand and copy the full 42-character form.
Clipboard hijacking
Malware can silently replace copied addresses with an attacker-controlled address. Always verify the first 6 and last 6 characters after pasting before confirming a transaction.
Case sensitivity
Ethereum addresses are case-insensitive at the protocol level but EIP-55 uses mixed case for integrity. Solana Base58 addresses ARE case-sensitive — changing any letter changes the address entirely.
Frequently Asked Questions
What is EIP-55 checksum and why does it matter?
EIP-55 (Ethereum Improvement Proposal 55) defines a mixed-case checksum encoding for Ethereum addresses. An Ethereum address is 20 bytes (40 hex characters prefixed with 0x), and the checksum capitalises certain letters based on a Keccak-256 hash of the lowercase address. This allows applications to detect common typos — if you accidentally change a character, the checksum will no longer match. Unlike Bitcoin's Base58Check, Ethereum does not enforce checksums by default, so many tools display addresses in lowercase. Using checksummed addresses is a best practice for safer copy-paste.
What is the difference between P2PKH, P2SH, and Bech32 Bitcoin addresses?
P2PKH (Pay-to-Public-Key-Hash) addresses start with '1' and are the original Bitcoin address format, sometimes called legacy addresses. P2SH (Pay-to-Script-Hash) addresses start with '3' and support more complex scripts, including multisig and SegWit-wrapped transactions. Bech32 addresses start with 'bc1' and are the native SegWit format introduced by BIP 173. Bech32 addresses have lower fees (because SegWit reduces transaction size), better error detection, and are fully lowercase to avoid confusion. Most modern wallets and exchanges now support all three formats.
How are Solana addresses structured?
Solana addresses are Base58-encoded public keys derived from Ed25519 keypairs. They are typically 32 to 44 characters long and use the standard Base58 character set (no 0, O, I, or l). Unlike Ethereum addresses, Solana addresses do not use a checksum scheme — validity is determined purely by character set and length. Programs (smart contracts) on Solana are also identified by regular addresses, so the same format applies to both user wallets and on-chain programs.
Can this tool verify whether an address actually exists on-chain?
No. This is a purely client-side format validator — it checks the structure, encoding, length, and character set of an address. It cannot query the blockchain to confirm whether an address has been used, holds a balance, or is a contract. For on-chain lookup, use block explorers such as Etherscan (Ethereum), Blockchain.com (Bitcoin), or Solscan (Solana). Format validation is still valuable — it catches typos, pasting errors, and wrong-network addresses before you send funds.
Why does my all-lowercase Ethereum address show as valid but without a checksum?
All-lowercase Ethereum addresses (0x followed by 40 lowercase hex characters) are syntactically valid — they can be used in transactions and smart contract calls. However, they lack the EIP-55 mixed-case checksum that protects against transcription errors. This tool displays the checksum status and recommends using the checksummed form for display purposes. Your wallet software will typically show checksummed addresses automatically. When in doubt, use the checksummed version — it is more copy-paste safe.