Check your wallets · hiddenfunds

Wallet 0x1505…a20f

Found in this wallet

$33

3 positions

Where it is

Chains that shut down2 positions$3091%
Bridges1 position$39%

Findings

Positions found for the checked wallets
Where	Chain	Amount		Links
zkSync Lite balance not claimed	Ethereum	0.00855428 ETH	$23	Claim
zkSync Lite balance not claimed	Ethereum	6.80277 USDC	$7	Claim
Hop transfer not receivedHop Protocol	OP Mainnet	0.00104348 ETH	$3	Claim

How to get it back

2 guides, the largest amount first

Use only the official links below. No real recovery asks for your seed phrase or private key. If anyone offers to recover funds for you, it is a scam.

zkSync Lite balance not claimed
$30 · 2 positions
zkSync Lite was shut down on 2026-05-04. Remaining balances are claimable on Ethereum through a claim contract and a withdrawal portal. Your account is on that list and has not claimed.
1. Open the zkSync Lite withdrawal portal and connect the wallet that owned the account.
2. The portal finds your address in the final state, builds the proof and sends the claim. Follow its prompts.
3. Confirm the Ethereum transaction. Tokens go to your L1 address. Matter Labs sponsors gas for the first 100,000 withdrawals.
zkSync Lite withdrawal portal (opens in a new tab)Official docs (opens in a new tab)
Hop transfer not received
Hop Protocol
$3 · 1 position
You sent a Hop transfer long ago and it was never paid out on the destination chain. The funds are still in Hop's bridge contract and its withdraw function still works, but Hop's website and data service are gone, so there is no ready tool: the withdrawal has to be built from on-chain data.
1. hop.exchange and every address under it (app.hop.exchange, docs.hop.exchange) no longer belong to Hop: hop.exchange now shows a gambling site. Do not open them or connect a wallet there.
2. Find your transfer in the TransferSent event of your transaction on the origin chain (block explorer, Logs tab). It holds the transfer ID, recipient, amount, transferNonce, bonderFee and the swap values.
3. The withdraw function also needs a Merkle proof of your transfer. Hop's open-source node tool has a withdrawal-proof command for it, but the tool reads Hop's data service at subgraph.hop.exchange, which no longer answers, so a developer has to point it at another source or rebuild the proof from on-chain events.
4. With the proof, call withdraw on the Hop bridge contract of the destination chain (block explorer, Write tab) from the wallet that should receive the funds. You pay gas.
5. On a Layer 2 destination you receive hTokens (for example hUSDC). They can be swapped to the native token in Hop's AMM on that chain.
Hop's open-source node tool (GitHub) (opens in a new tab)Hop bridge contract (withdraw function) (opens in a new tab)