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.

1. zkSync Lite balance not claimed

   $38 · 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)

2. Ended Sablier stream not withdrawn

   $8 · 1 position

   A Sablier payment stream to you has ended or was canceled, and the tokens in it were never withdrawn. The tokens are still in the Sablier contract.

   1. Open the Sablier app and connect the wallet that owns the stream.
   2. Find the ended stream and press Withdraw.
   3. The tokens go to the stream recipient. Pay the gas fee.

   Sablier app (opens in a new tab)Official docs (opens in a new tab)

3. Funds in frozen StarkEx apps

   Sorare, Immutable X, ApeX Pro, edgeX v1, Myria

   $8 · 1 positionMay not work

   Some StarkEx apps keep balances off-chain. A pending withdrawal can be claimed now. A deposit-only record cannot: the app operator must first publish data.

   1. Check the row type. A pending withdrawal can be claimed now; a deposit ledger row cannot.
   2. For a pending withdrawal, call withdraw with your owner key and asset type on the app's StarkEx contract (Etherscan). Funds go to your registered address.
   3. For a frozen app, the escape hatch needs the operator or data committee to publish state first. See the StarkWare docs.

   Official docs (opens in a new tab)

4. 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)

5. Alpaca v1 vault tokens

   Alpaca Finance

   <$1 · 1 position

   You hold Alpaca v1 ibTokens (deposit receipts) on BNB Chain. The vault still pays out the underlying token.

   1. Open the ibToken contract (contract column) on BscScan and go to Write Contract.
   2. Connect the owner wallet and call withdraw(shares).
   3. ibBUSD, ibETH, ibBTCB and ibUSDC were migrated: withdraw may pay a different token. If it reverts, read the contract's functions on BscScan.