Paste any address, or an ENS name, and pick the chain you are about to send on. On 32 EVM chains it tells you, from public RPCs only, whether funds sent to that address on that chain can be reached, before you send. The same answer tells you, after a mistake, whether funds already sent there can be recovered and by whom.
On 19 other networks, such as Bitcoin, Solana, TRON and Zcash, it checks the address format: it catches a wrong network or a typo, and says so. Only XRP and Stellar are contacted, and only for whether an account asks for a tag or memo. An exact match on the US OFAC list is a Stop, and a reserve wallet an exchange published itself gets a dated note. It is not a scam check.
It never asks for keys, never connects a wallet and never signs anything.
A 0x… address looks the same on every EVM chain, but it does not always mean the same thing:
- a key wallet address comes from a private key, and that key controls it on every EVM chain;
- a smart wallet (a Safe, an Abstract Global Wallet, an ERC-4337 account) is a contract. It exists only on the chains where it was created. On any other chain the same address has no code and no key behind it.
Send to a smart wallet on a chain where it does not exist and nobody may ever reach the funds. In October 2026 a user reported losing about $20,000 of USDC this way, after pasting their Abstract Global Wallet address while sending on BNB Chain. The report is their own post. On chain, the matching address holds 19,998 Binance-Peg USDC on BNB Chain, with no code behind it and no outgoing transactions (checked 5 Nov 2026). Wallets and exchanges accept the address because it is valid; on the chain it was sent on, it looks like an unused account. Abstract shuts down on 15 Dec 2026, so its users are moving funds now.
What existed on 26 Oct 2026 (notes in Cryppit's research repo): Rabby warns about contracts on other chains from its own private index; Abstract's Migration Hub blocks this inside its own bridge flow. MetaMask, Rainbow, Zerion, the exchanges' withdrawal screens and the address-screening APIs we checked do not catch it, and GoPlus marks an Abstract wallet as clean on BNB Chain. Chain-specific address standards (ERC-7930, ERC-7828) reached Review in April 2026 and no wallet ships them yet.
Node 22 or later, no dependencies.
node cli.js 0x<address> --chain bnbchain # or a chain ID: --chain 56
node cli.js 0x<address> --chain 8453 --json # every fact behind the answer
node cli.js vitalik.eth --chain base # an ENS name, resolved on Ethereum first
node cli.js bc1q... --chain bitcoin # any other network: format only
npm test # replays recorded real addresses, no networkThe page (index.html) does the same in the browser; ?address=0x…&chain=56 opens a check directly, and
?address=bc1…&chain=bitcoin does the same for a format check.
First it recognises the address: its format, and its checksum where it has one. A mixed-case 0x address that fails
EIP-55 stops here, and so does an address from another network. For a good EVM address it reads, at the latest block of each of 32 chains: eth_getCode and eth_getTransactionCount. For a
contract it also asks getThreshold() and getOwners() (a Safe), and on the chain you picked symbol() and
decimals() (a token's own contract). It looks the address up in the archive of Abstract Global Wallets, and while
Abstract runs it also asks Abstract's AGW registry (isAGW).
| What it finds | Verdict | Who can reach funds already sent |
|---|---|---|
| An Abstract Global Wallet, and the chain is not Abstract or ZKsync Era | Stop: lost for good. Abstract runs EraVM, which derives contract addresses differently from EVM chains, so the wallet can never exist at this address there | nobody |
| An Abstract Global Wallet, and the chain is ZKsync Era | Caution: don't send. ZKsync Era also runs EraVM and has Abstract's wallet factory, wallet code, registry and signer validator at the same addresses (checked 26 Oct 2026), so the owner can most likely create the same wallet there | the owner, most likely |
| An Abstract Global Wallet, and the chain is Abstract | Caution: works until Abstract shuts down on 15 Dec 2026 | the owner, until then |
An EIP-7702 delegation on this chain or another (0xef0100 + 20 bytes) |
Safe: still a key wallet; its key works everywhere | the owner |
| No code here, but transactions sent from it here or on another chain | Safe: a key wallet | the owner |
| A Safe on this chain, with the same owners everywhere it was seen | Safe | its owners |
| A Safe on this chain, with different owners or a different threshold on another chain | Caution: the same address can belong to different people on different chains | its owners on this chain |
| The token's own contract on this chain | Stop: tokens sent to it usually stay stuck | usually nobody |
| Another contract on this chain | Caution: it must be a wallet that can move funds | depends on the contract |
| A Safe on other chains only | Stop: reachable only if the same Safe is created here; for some older Safes a stranger can do it first (Wintermute lost 20M OP this way in 2022) | maybe |
| Another contract on other chains only | Stop | usually nobody |
| Never used on any chain checked | Can't tell: a new key wallet and an undeployed smart wallet look the same; send a small test | unknown |
A safe answer is about whether funds can be reached, not about who the address belongs to.
For networks it does not read, the answers come from the address alone:
| What it finds | Verdict |
|---|---|
| An address from a different network than the one picked | Stop: wrong network, with a link to check it on its own network |
| A failed checksum, or a test-network or stake address | Stop |
| An old-style address picked for Bitcoin Cash | Caution: Bitcoin and Bitcoin Cash both used this form |
| A well-formed address for that network | Format OK: never "Safe", because no chain was read |
Solana, Sui, Aptos, Movement, Starknet and Fogo addresses have no checksum, so a typo can still pass. The answer says so.
These can only add a warning. Silence never means an address is fine.
- XRP (
xrplcluster.com,xrpl.ws): therequireDestinationTagflag, then the last 200 transactions. An account counts as shared with at least 10 senders and over half of incoming payments tagged above 9999. Our own test of an idea Xaman uses. - Stellar (
horizon.stellar.org):config.memo_required(SEP-29) only. The network doesn't enforce it, and the answer says so. No pattern test yet: it has no false-alarm data on Stellar. data/lists/, rebuilt bynode scripts/update-lists.mjs <date>: OFAC addresses via 0xB10C's extractor (MIT), and exchange-published reserve wallets via GraphSense (MIT). The exchange list dates from 2022 and holds reserve wallets, not deposit addresses. Seedata/lists/LICENSE.
index.html forbids every connection except the RPCs and these services, and test/privacy.test.js keeps that list exact.
Address recognition comes from Cryppit's Where's My Swap (MIT).
data/abstract/ holds every Abstract Global Wallet deployed on Abstract (chain 2741), so the check keeps working after
Abstract shuts down.
- Source. Every AGW is created by one factory,
0x9b947df6…6c1a(SMART_ACCOUNT_FACTORY_ADDRESSin@abstract-foundation/agw-client1.12.3; the AGW registry's onlyFactorySet, block 76,852, never unset). EraVM logs each deployment asContractDeployed(deployer, bytecodeHash, contractAddress)from the ContractDeployer system contract (0x…8006), all indexed.scripts/archive-abstract.mjs scanreads those logs from block 76,851 to a pinned finalized block through Abstract's public RPC, in windows that shrink when the RPC refuses more than 10,000 results. It checkpoints after every window, so it resumes, and a later run reads only the new blocks. - Format.
agw/<xx>.binholds the wallets whose address starts with0x<xx>: sorted, distinct 7-byte records (address bytes 2–8). A lookup matches on the first 8 bytes. With millions of wallets, a wrong match needs a 64-bit collision, about 1 in 3 trillion per lookup; the page fetches only the one shard it needs (about 150 KB).manifest.jsonrecords the block range, the pinned block's hash, the wallet count, the code hashes seen and a SHA-256 for every shard. - Checked.
scripts/verify-abstract.mjspicks wallets at random from the scan and confirms each one is registered in the AGW registry, has code on Abstract and is found in the shards; it also confirms random addresses are not found. - Not covered. A counterfactual AGW (an address computed from a signer but never deployed) is not in the logs, so it is not in the archive. While Abstract runs, the registry covers deployed wallets the archive missed.
Public JSON-RPC endpoints without keys, two per chain where available, all answering browsers (CORS), checked on 26 Oct
2026: Ethereum, BNB Chain, Base, Arbitrum One, OP Mainnet, Avalanche C-Chain, Linea, ZKsync Era, Scroll, Gnosis,
Unichain, Robinhood Chain, Abstract, Sonic, Celo, Mantle, Blast, Berachain, HyperEVM and Ink (src/chains.js).
dRPC and 1RPC are never used. Kaia is left out because an account there can change its key. The endpoints are rate
limited and offered as is.
MIT. A Cryppit tool. The chain logos in logos/ are from
web3icons (MIT), unmodified; see logos/LICENSE.