Ethereum Address Validator

Ethereum addresses: the universal handle of the EVM ecosystem

An Ethereum address is a 20-byte (160-bit) identifier displayed as a 42-character string: the prefix 0x plus 40 hexadecimal characters. The same format is used by every EVM-compatible chain — Polygon, BNB Chain, Avalanche C-Chain, Base, Arbitrum, Optimism, ZkSync Era and dozens of others — which makes it the closest thing to a universal Web3 handle.

Unlike Bitcoin's UTXO model, Ethereum is account-based: every address has a balance and a nonce. There are two kinds of accounts: EOA (Externally Owned Account), controlled by a private key, and Smart Contract account, controlled by deployed bytecode. Both share the exact same address format — there is no way to tell them apart by inspecting the string alone; the network must be queried to know whether code lives at that address.

From private key to address: the cryptographic pipeline

For an EOA, the derivation is deterministic:

• Generate a 256-bit private key (random on the secp256k1 curve, the same curve Bitcoin uses).
• Compute the corresponding public key (64 bytes, uncompressed, without the 04 prefix).
• Apply Keccak-256 over the 64-byte public key.
• Take the last 20 bytes of the hash. Prepend 0x. That is the address.

Note that Ethereum uses Keccak-256 (the original Keccak submission), not the final SHA-3 NIST standard, which differs in the padding bits. This is a frequent source of confusion when porting code from other languages — never use SHA-3 when the spec asks for Keccak.

EIP-55 checksum: case as integrity bit

Hex characters are case-insensitive by nature, so a plain Ethereum address is the same whether written in upper or lower case. EIP-55 (proposed by Vitalik Buterin in 2016) repurposes the case of each letter to encode a checksum: take keccak256 of the lowercase address, look at each nibble; if the nibble is greater than or equal to 8, the corresponding letter is uppercase. The result still validates on every node, but typos in case become detectable with ~99.986% probability.

A robust validator must therefore:

• Match ^0x[a-fA-F0-9]{40}$ as a format check.
• If the input is all lowercase or all uppercase, accept it (legacy, pre-EIP-55).
• If it has mixed case, verify the EIP-55 checksum and reject the address if it fails.

Plain:  0x52908400098527886e0f7030069857d2e4169ee7
EIP-55: 0x52908400098527886E0F7030069857D2E4169EE7
Wrong:  0x52908400098527886E0F7030069857D2E4169Ee7  (mixed case but bad checksum)

ENS: human-readable names backed by smart contracts

The Ethereum Name Service (ENS) maps human names like vitalik.eth to addresses through a set of registry and resolver contracts. Names are NFTs registered for 1 year or more, with annual fees ranging from US$ 5 to US$ 640 depending on the length (3-character names are the priciest). ENS supports reverse resolution, multi-coin records, content hashes (for IPFS sites) and avatars, turning the address into a portable identity across wallets, DEXs and social apps.

ENS names also resolve on Layer 2 networks through CCIP Read (EIP-3668), which lets a name registered on mainnet point to addresses on Optimism, Base or Arbitrum — useful for cross-chain workflows.

EVM chains, Layer 2 and the same address everywhere

Because address derivation depends only on the private key and the Keccak-256 hash, the same EOA controls the same address on every EVM chain: Ethereum mainnet, Polygon, BNB Chain, Avalanche, Fantom, Gnosis Chain, and Layer 2 rollups like Arbitrum One, Optimism, Base, ZkSync Era, Linea, Scroll and Polygon zkEVM. This is convenient — one seed phrase, all the ecosystems — but introduces a critical pitfall: sending the wrong asset to the right address on the wrong chain still loses funds unless the recipient happens to own the address on the destination chain and bridges the asset.

Smart-contract addresses are deterministic per chain (the address is keccak256(rlp(deployer, nonce))[12:]). The same deployer with the same nonce on two chains produces the same contract address — the foundation of CREATE2 and counterfactual deployments used by smart-wallet projects like Safe and account-abstraction (ERC-4337) wallets.

Gas, EIP-1559 and Layer 2 fee economics

Gas is the unit of computation in the EVM, priced in gwei (10^-9 ETH). EIP-1559 (London hard fork, 2021) split the fee into a base fee that is algorithmically determined and burned, plus a priority fee that goes to the validator. Net of issuance, ETH became deflationary in many periods after the merge to proof-of-stake.

Layer 2 rollups inherit Ethereum security while cutting fees by 10-100x. Optimistic rollups (Arbitrum, Optimism, Base) post call data on L1 and rely on a 7-day challenge window. ZK rollups (ZkSync Era, Polygon zkEVM, Scroll, StarkNet) post validity proofs, enabling near-instant finality.

Common scams: address poisoning, MEV and clipboard hijack

Address poisoning: the attacker generates an address whose first and last characters match the victim's recent counterparty, then sends a zero-value transfer to taint the history. Wallets that auto-complete by recent counterparties become a vector — the user pastes the lookalike and loses the funds.

Clipboard hijack malware: a process running on the machine watches for anything that looks like a crypto address in the clipboard and swaps it for the attacker's address. Always double-check the first and last 6 characters before signing.

MEV (Maximum Extractable Value): searchers reorder, insert or front-run transactions in the mempool to extract value — particularly common in DEX swaps. Mitigations include private mempools (Flashbots Protect, MEV-Blocker) and CoW Swap-style batch auctions.

Brazilian DeFi and the regulatory map

Brazilian users access Ethereum through wallets like MetaMask, Rainbow, Trust Wallet and hardware devices (Ledger, Trezor). Exchanges including Mercado Bitcoin, Foxbit, NovaDAX and Binance Brasil integrate with Brazilian banks via Pix. Hashdex pioneered crypto ETFs on B3. Stablecoins (USDC, USDT) settled on Ethereum/Polygon are widely used for remittances and payroll. The same Lei 14.478/2022 and Receita Federal IN 1.888/2019 framework that covers Bitcoin applies to Ethereum and ERC-20 tokens.

FAQ

Does case matter in an Ethereum address? For the network it does not — the address is hex. But the EIP-55 checksum uses case to detect typos. Wallets reject mixed-case addresses that fail the checksum.

Is the same address valid on Polygon, BNB Chain and Arbitrum? Yes — every EVM-compatible chain uses the exact same address format. The same key controls the same address on all of them. The asset, however, only exists on the chain where the contract was deployed.

Is ENS free? No. ENS charges an annual rent. As of 2026, 5+ character names cost ~US$ 5/year, 4-character names ~US$ 160/year and 3-character names ~US$ 640/year, plus gas.

Can I tell from the address whether it's an EOA or a contract? No. The string is identical. Only by querying the chain (eth_getCode) can you check if bytecode is deployed at that address.

Does this tool send the address to a server? No. All validation runs locally in your browser, including the EIP-55 checksum.