The idea
An address is like a house number, and a chain is like a city. The same number can exist in many cities. In one it's your smart wallet — a Safe, or an account-abstraction wallet. In another the same address is an empty plot: no code, no owner, nobody home.
If you sent funds to a smart-wallet address on a chain where that address is empty, your wallet can't see the problem — it only checks the address looks valid. This tool looks at what is really at that address on the chain you picked, and on the others, then tells you honestly whether the money can be reached, and the risky steps if it can. Some losses — Abstract Global Wallets especially — usually can't be recovered, and we say so.
How a check works
Everything runs in your browser. Nothing is ever signed or deployed — reading a chain needs no key.
- 1. Pastethe address and the chain the money landed on
- 2. Readthe address on 34 EVM chains at once, read-only
- 3. Findwhere it's a smart wallet, and what kind
- 4. Checkwhether the destination already has code, and whether the Safe's factory is live there
- 5. Answerone honest verdict, with the reasons and any steps
The answers
Every check ends in one of these. Colour is always paired with a mark and a word.
- ⚠ Possibly recoverable
A modern CREATE2 Safe that lives on another chain, with its factory live on the destination. The owner may be able to redeploy the identical Safe at the address.
Read every step and warning first. It carries a deploy-race risk; you act, we never do.
- ⚑ Occupied
Something already has code at this address on the destination chain. Whoever controls that contract controls what's there — it could be an attacker.
Don't send more until you've verified the owners are yours.
- ✗ Very likely unrecoverable
An Abstract Global Wallet, a zkSync-stack destination, or an old create-opcode Safe. The identical wallet can't be reproduced at this address.
Treat the funds as gone. Beware anyone who says otherwise.
- ? Unknown
A smart wallet we can't classify, a Safe version we couldn't read, a factory we can't confirm, or an address never used anywhere. Unproven is not a yes.
Get expert review, or send a small test first — never assume recovery.
- • Not a smart-wallet case
A regular key-controlled address, not a smart wallet. If you hold its private key, funds on that chain are already yours to move.
This tool is for smart-wallet-on-the-wrong-chain losses, which this isn't.
What decides recovery
Whether a smart wallet can be reproduced at the same address on another chain comes down to a few exact facts. This is the heart of it.
◆A smart wallet lives where it was deployed
A smart wallet is a contract, not a key. It exists only on the chain where it was created. On any other chain the same address has no code and nobody behind it — until, for some kinds, it can be created there too.
≡A Safe's address repeats only if everything matches
The same Safe address appears on another chain only when the factory, the singleton (mastercopy), the initializer (owners, threshold, fallback handler) and the salt (saltNonce) — and the proxy creation code — all match. Change any one, and it's a different address.
⚠Modern CREATE2 Safes — a deploy race
Safe v1.3.0 and v1.4.1 use CREATE2. If the matching SafeProxyFactory is live on the destination chain and you still have the original owners and saltNonce, the owner can redeploy the identical Safe at the address. But whoever deploys first wins — this is the 2022 Wintermute/Optimism theft of 20M OP. jonluca/safe-everywhere automates this for opted-in Safes; it excludes zkSync.
✗Old create-opcode Safes can't be re-made by the owner
Safe v1.0.0 and v1.1.1 got their address from create(deployer, nonce). The legitimate owner can't reproduce the original deployer's nonce on a new chain, so they can't redeploy there. Only an attacker replaying the old factory could — which is exactly what happened to Wintermute.
✗Abstract / zkSync Era wallets can't follow
Abstract Global Wallets and zkSync Era derive addresses with EraVM's own formula (a different create2 and a split nonce). The same bytecode and salt do not yield the same address on an ordinary EVM chain, so the wallet can't be re-created at that address. A zkSync-stack destination has the same problem in reverse.
⚑If the destination is already occupied
If code already exists at the address on the destination chain, funds there are controlled by whoever owns that contract — possibly an attacker who got there first. Verify the owners are yours before trusting it.
Recovery scams
Losing funds this way is stressful, and that makes people targets. Be plain with yourself about this:
- Nobody can "recover" an Abstract Global Wallet sent to another chain. If someone offers to, for a fee or otherwise, they are lying.
- We never ask for a seed phrase, private key or one-time code, and we would refuse one if you pasted it. Anyone who asks is trying to steal from you.
- We never deploy or sign anything. If a verdict is "Possibly recoverable", the steps are yours to take, at your own risk — not a service we sell.
- Ignore unsolicited messages promising to get your money back. Real recovery, where it exists at all, is the steps shown here, done by you.
What it can't tell you
- It can't recover funds for you. It reads chains and tells you the honest answer. Any deployment you attempt, you do yourself.
- It reads only the 34 EVM chains listed below. A smart wallet on a chain not in that list won't be found, and a destination not in the list can't be checked.
- A "Possibly recoverable" needs the exact original parameters. Redeploying a Safe needs its precise factory, singleton, initializer and saltNonce to all exist and match on the destination. Without them, the address won't match.
- Unknown means unknown. A brand-new wallet and an undeployed smart wallet look identical from the outside. We never turn that into a yes.
- It's true for the moment it was read. Contracts, owners and factories can change; an answer is a snapshot.
- It isn't a scam check. It tells you whether funds can be reached, not whether a person is honest.
Your privacy — what leaves your browser
- No account, no tracking. There's no sign-up, analytics or cookies, and nothing is saved in your browser.
- No Cryppit server. Your browser does the work. The page itself blocks every connection except the public services below.
- The chains see the address. To read it, your browser asks each chain's public RPC service about the address, so those services can see the address and your IP address.
- The Abstract archive is fetched in small pieces. One small shard per address prefix is downloaded on demand to spot Abstract Global Wallets after Abstract shuts down; it reveals only which prefix you looked at.
- Nothing else leaves your browser. No keys, ever. We never ask for a seed phrase or private key, and would refuse one if pasted.
Words you'll see
- Smart wallet
- A wallet that's a contract, so it only exists on chains where it was deployed.
- Safe
- A popular smart wallet shared by several owners. "3-of-5" means 3 of its 5 owners must approve.
- Factory
- The contract that deploys a Safe. The same Safe address can only be made on a chain where its factory is live.
- Singleton (mastercopy)
- The shared Safe logic every Safe proxy points to. Reading storage slot 0 gives it, which tells us the Safe's version.
- CREATE2
- A way of making a contract's address from the factory, the code and a salt — so it can be the same on another chain, if all of those match.
- create opcode
- The older way, where the address came from the deployer and its nonce. The owner can't reproduce that nonce on a new chain.
- saltNonce / initializer
- The salt and the setup (owners, threshold, fallback) baked into a CREATE2 Safe's address. Both must match to land at the same address.
- Abstract Global Wallet / EraVM
- An account-abstraction wallet on Abstract/zkSync. EraVM derives addresses differently, so it can't be re-made on an ordinary EVM chain.
- Deploy race
- When a Safe can be redeployed at an address, whoever deploys first controls it. The risk behind "Possibly recoverable".
- Occupied address
- An address that already has contract code on the destination chain — controlled by whoever owns that contract.
Networks
A check reads the address on 34 EVM chains, all at once, read-only. The full row is on the Check tab, under "The chains we read". A smart wallet or a destination on a chain outside that list can't be checked.