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. Unclaimed OP Stack chain withdrawal

   Blast, Mantle, Mode, Zora, Lisk, Ink, Unichain and other OP chains

   $2 · 1 position

   You withdrew from an OP Stack chain to Ethereum but never completed the last step. The funds wait in that chain's bridge.

   1. Use the official bridge of the chain you withdrew from (linked next to each of your positions).
   2. Connect the receiving wallet and open your transactions. Press Prove, wait out the challenge period shown on the page, then press Finalize.
   3. Pay the Ethereum gas fee each time.

   Official bridges for the chains your positions are on:

   • Manta Pacific Bridge (opens in a new tab)

   Official docs (opens in a new tab)

2. zkSync Lite balance not claimed

   <$1 · 1 position

   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)

3. Hyperlane transfer not delivered

   Hyperlane warp routes

   $0 · 1 positionMay not work

   Your tokens were taken on the origin chain by a Hyperlane route, but the message was not delivered after 7 days. Anyone can deliver it.

   1. Open Hyperlane Explorer and search your transaction hash.
   2. If the message is undelivered and 'Underfunded', pay more interchain gas as shown in the Hyperlane docs, or relay it with the Hyperlane CLI.
   3. Once delivered, the recipient gets the tokens. If delivery keeps failing, the route owner must fix it.

   Hyperlane Explorer (opens in a new tab)Official docs (opens in a new tab)