ChainDePINDePIN Network Monitor
OverviewTrendsPricingupdated not yet refreshed
Wallet & contract safety

Address Checksum & Revoke Tracker

Generate an EIP-55 checksummed Ethereum address to stop costly typos, then scan your ERC-20 token allowances across major chains and spot risky approvals to revoke. 100% in-browser — no upload, no backend, no private key.

EIP-55 checksumETH address validatorToken allowance checkerRevoke tracker

Checksum generator & allowance scanner

Token allowance check (revoke tracker)
Reads ERC-20 approvals your address has granted to the Uniswap Universal Router and Permit2 on the selected chain — directly from public RPC, no backend.
Everything runs in your browser. The checksum is computed locally with viem and the allowance read is a read-only eth_call — this tool never sends a transaction or asks for a private key.

What is an EIP-55 checksum?

An Ethereum address is 20 bytes, normally shown as 40 hexadecimal characters after “0x”. EIP-55 keeps that length but sets each character to upper or lower case based on the Keccak-256 hash of the address. Because the pattern is deterministic, a single wrong character almost always breaks the checksum — so a wallet can warn you before you send to a mistyped address. Lowercase and uppercase addresses are still valid, but they carry no error detection.

Why mixed case matters

A mixed-case address lets software verify the characters you typed. If you copy a lowercase address and one letter flips during a paste, nothing catches it. A checksummed address turns that silent error into a loud warning.

How the checksum is built

Take the Keccak-256 hash of the lowercase address; for each of the 40 hex characters, upper-case it when the matching hash nibble is 8 or higher, otherwise keep it lower. The result is the canonical EIP-55 string. This tool computes it locally with viem.

Checksum ≠ ownership

A valid checksum only proves the characters are internally consistent — it does not mean the address is a real person or a safe contract. Always confirm the destination in your own wallet before transferring.

Token allowances & why you should revoke

When you use a DEX, bridge or lending app, you “approve” a contract (the spender) to move a token from your wallet. That approval persists until you revoke it. Old allowances to contracts you no longer use are a common attack surface: if that contract is exploited, the spender can still drain the approved token. Periodically reviewing and revoking stale approvals is one of the highest-value wallet-hygiene habits.

Read-only safety check

The scanner above performs a read-only eth_call for each token’s allowance to the Uniswap Universal Router and Permit2. It never submits a transaction and never sees your key — it simply reports what is already on-chain.

Scope of this scan

This is a fast, sample check across the top tokens and two common spenders. For a complete, indexed view of every approval your address has ever granted, use a dedicated permission manager such as revoke.cash. Both are read-only; revoking itself costs gas.

When to revoke

Revoke an approval when you stop using a protocol, when a contract is deprecated, or when an audit flags a spender. Keeping only the allowances you actively need shrinks your blast radius if any approved contract is compromised.

Frequently asked questions

What is an EIP-55 checksum?
EIP-55 is the Ethereum address checksum standard. It keeps the address 42 characters long but mixes upper and lower case based on the Keccak-256 hash of the address. A single mistyped character almost always produces an invalid checksum, so wallets and tools can warn you before funds are sent to the wrong place.
How do I generate an EIP-55 checksum address?
Paste any 0x address into the generator above. If it is all lowercase or all uppercase, the tool rebuilds the correct mixed-case EIP-55 form. If you paste a mixed-case string with a typo, it reports the checksum as invalid and shows the corrected address. No upload, no server — it is computed in your browser with viem.
Why does the checksum use mixed upper and lower case?
The case is not random: each hexadecimal character is upper-cased only when the corresponding nibble of the Keccak-256 hash is 8 or higher. That deterministic rule lets any tool re-verify the address. Lowercase and uppercase addresses are valid but carry no error-detection, which is why checksummed addresses are safer for transfers.
What is a token allowance / approval?
When you interact with a DEX, bridge or lending protocol, you approve (allow) a smart contract — the “spender” — to move a specific ERC-20 token from your wallet. That approval stays active indefinitely until you revoke it, which is why old allowances to contracts you no longer use are a common security risk.
How do I check my token allowances?
Enter your address and pick a chain above, then run the scan. The tool reads the ERC-20 allowance your address has granted to the Uniswap Universal Router and Permit2 directly from each network’s public RPC. It is a read-only check — no transaction is sent. For a full scan of every token and spender, use an indexed explorer such as revoke.cash.
How do I revoke a token approval?
Revoking sets the allowance back to zero via a transaction from your own wallet, which costs a small gas fee. You can do this from the protocol’s own interface or a permission manager (revoke.cash, the Uniswap app, etc.). This tool only reads allowances; it never asks for your private key or sends a transaction.
Is this address checker safe to use?
Yes. The checksum is computed entirely in your browser and the allowance read is a read-only on-chain call. The tool has no backend, stores nothing, and never requests a private key, seed phrase or signature. Always verify the checksummed address against your own wallet before sending funds.
Want the full DePIN picture?
Live node status, on-chain stats and 30-day market trends for the major DePIN networks.
Open the monitor →
OverviewTrendsPricingUnit & Gas ConverterDCA & Liquidation CalcToken UnlocksAddress Checksum
Data is aggregated from public APIs and refreshed on a scheduled basis — values may lag and are shown as-is.
Allowance reads come from public network RPCs and may be briefly unreachable under load. This tool is informational only and is not financial or security advice. Always verify addresses and approvals in your own wallet.
Disclaimer: Nodepay and Grass do not expose official public node APIs; node-level figures are unavailable and only market data is shown. Nothing here is financial advice. Grass/NodePay data is unofficial where noted.