Address formats by network
What each network's addresses start with, how long they are, how they are encoded and whether a checksum catches typos. Every value follows from the format's specification, linked on each validator page.
All formats
| Network | Starts with | Length | Encoding | Checksum | Typo check |
|---|---|---|---|---|---|
| B BitcoinLegacy · P2PKH | 1 | 26–34 | Base58Check | 4 bytes · double SHA-256 | Full |
| B BitcoinScript · P2SH | 3 | 34 | Base58Check | 4 bytes · double SHA-256 | Full |
| B BitcoinSegWit v0 | bc1q | 42 / 62 | Bech32 | 6 characters · BCH code | Full |
| B BitcoinTaproot | bc1p | 62 | Bech32m | 6 characters · BCH code | Full |
| Ł LitecoinL · M · ltc1 | LMltc1 | 34 / 43 / 63 | Base58Check · Bech32 | as Bitcoin | Full |
| D DogecoinLegacy · P2SH | D9A | 34 | Base58Check | 4 bytes · double SHA-256 | Full |
| B Bitcoin CashCashAddr | qp | 42 | CashAddr | 40-bit BCH code | Full |
| D DashLegacy · P2SH | X7 | 34 | Base58Check | 4 bytes · double SHA-256 | Full |
| Z ZcashTransparent · shielded · unified | t1t3zs1u1 | 35 / 78 / 100+ | Base58Check · Bech32 · Bech32m | 4 bytes · BCH code | Full |
| E Ethereum · EVMAccount or contract | 0x | 42 | Hex · 20 bytes | Letter case (EIP-55), optional | Format · case |
| T TRONAccount or contract | T | 34 | Base58Check | 4 bytes · double SHA-256 | Full |
| X XRP LedgerClassic · X-address | rX | 25–35 / 47 | Base58Check · XRP alphabet | 4 bytes · double SHA-256 | Full |
| S SolanaAccount | any Base58 | 32–44 | Base58 · 32 bytes | None | Format only |
| T TONUser-friendly · raw | EQUQ0: | 48 / 66 | Base64url · hex | CRC16 (user-friendly form) | Full |
| A CardanoShelley · Byron | addr1stake1Ae2DdzFF | 58 / 59 / 103 | Bech32 · Base58 + CBOR | 6 characters · BCH code · CRC32 | Full |
| S StellarAccount · muxed | GM | 56 / 69 | Base32 | CRC16 | Full |
| C Cosmos chainscosmos, osmo, … | cosmos1osmo1 | 45+ | Bech32 | 6 characters · BCH code | Full |
| M MoneroStandard, subaddress, integrated | 48 | 95 / 106 | Base58 · Monero blocks | 4 bytes · Keccak-256 | Full |
| P Polkadot · KusamaSS58 | 15C–H | 47–48 | Base58 · SS58 | 2 bytes · BLAKE2b-512 | Full |
| A AlgorandAccount | A–Z, 2–7 | 58 | Base32 | 4 bytes · SHA-512/256 | Full |
| T Tezostz accounts · KT1 contracts | tz1tz2tz3KT1 | 36 | Base58Check | 4 bytes · double SHA-256 | Full |
| K KaspaSchnorr · ECDSA · P2SH | kaspa:qkaspa:p | 61 / 63 + prefix | CashAddr-style | 40-bit BCH code | Full |
| N NEARNamed · implicit | .near | 2–64 | Name or hex | None | Format only |
| S Sui · AptosAccount or object | 0x | 66 | Hex · 32 bytes | None | Format only |
✓ Full: format and checksum are verified in the browser– Format only: no checksum to verify, a typo cannot be detectedFormat · case: EIP-55 checksum only when written in mixed case
FAQ
Which crypto addresses have no checksum?
Solana, Sui, Aptos, NEAR and EVM addresses written in a single case. A typo in them gives another valid-looking address.
Why do several networks share one format?
Networks built on the same technology reuse its address format: every EVM chain uses 0x… addresses, Bitcoin Cash legacy addresses look like Bitcoin's. The format then cannot tell the networks apart.