This validator needs JavaScript (runs locally in your browser).
Examples:
Note: only formal validity (format + checksum) is checked — not existence or balance. No blockchain query happens; nothing leaves your browser.
What is actually checked here
| Type | Detection | Checksum |
|---|---|---|
EVM 0x… | 0x + 40 hex | EIP-55 (Keccak, encoded in letter casing) |
SegWit bc1q… | Version 0 | bech32 (BIP173) |
Taproot bc1p… | Version 1 | bech32m (BIP350, new constant) |
Legacy 1…/3… | Version byte 0x00/0x05 | Base58Check (double SHA-256) |
Solana Base58 | 32-byte public key | no separate checksum (Base58 itself has none) |
Go deeper: Wallet Generator (where addresses come from) and AI agents & payments (where wrong addresses cost money).
Frequently asked questions
bc1q or bc1p — what is the difference?
bc1q… = SegWit v0 (bech32), bc1p… = Taproot v1 (bech32m). Different checksum constants — a v0 address with a bech32m checksum is invalid and vice versa.My 0x address is all lowercase — a problem?
Format ok, but no checksum. Typos go unnoticed. Use the EIP-55 spelling (mixed upper/lower case) — the validator shows it to you.
Why no balance lookup?
On purpose: every query reveals your address to a server. Formal validation catches ~99 % of copy-paste errors — without costing privacy.
Planning a custody concept or payment flow?
Address handling, checksum validation and custody processes belong in every Web3 project — I help with reviews and setup.