EIP-55: the checksum in letter case
How EIP-55 hides a checksum in the letter case of an Ethereum address, why an all-lowercase 0x address cannot be checked, and how to add the checksum.
0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAedOpen the checkerHow it works
An Ethereum address is 20 bytes written as 40 hex characters. EIP-55 takes the Keccak-256 hash of the lower-case address and, for every letter a–f, writes it in upper case when the matching hex digit of the hash is 8 or higher. Digits stay digits.
So 0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed (a test vector from EIP-55) carries a checksum, and changing any character almost always breaks the pattern of upper and lower case.
When there is no checksum
An address written all in lower case (or all in upper case) carries no checksum at all. It is still valid, but a typo in it gives another valid-looking address. That is why the checker shows “no checksum in this form” for it and offers the EIP-55 form.
The same on every EVM chain
BNB Smart Chain, Polygon, Arbitrum, Base and other EVM chains use the same 20-byte address and the same EIP-55 rule. (EIP-1191 defines a chain-specific variant that only a few chains use; the checker follows EIP-55.)
FAQ
Is a lower-case Ethereum address wrong?
No, it is valid. It just has no checksum, so a typo cannot be detected. Converting it to EIP-55 adds the checksum without changing the address.
Does EIP-55 work on BNB Smart Chain and Polygon?
Yes. They use the same address format and the same letter-case checksum.