I get this error at zksync portal after I sign the transfer in the metamask/ledger for few days trying to bridge storj from ZkSync Era to different ETH addresses. I have enough ETH on Era and L1 wallet to pay the fees.
You’re having trouble with a mystery wallet, using a mystery service, to bridge from Era to L1? Most of the answers here are for software provided by Storj.
Set your payout to a CEX L1 address like a normal person 
i did some L2 to L1 transfers but more than 4 days ago and No Problem.
(i recommend Rabby wallet as its way better than metamask)
I can recommend this way:
Starting point:
- HAVE Storj at L2
- Don’t have any ETH on L2 for fees
Need to free Storj from L2 to L1
Use relayer (https://relay.link/bridge) to send:
L1 eth → L2 eth $0.05 (relayer says fee like $0.01 but total cost was $0.04 so totally spend $0.09)
Then use ZKsync Bridge | Transfer funds between ZKsync and Ethereum to send Storj tokens from ZkSync Era network (L2) to L1 Eth network
If You use Ledger hardware wallet, You need to connect it to some Rabby browser wallet first, and in portal.zksync.io connect with that Rabby wallet
so portal.zksync.io can send it (because ledger does not support L2 zkSync Era directly)
so when You have some ETH on L2 to pay the fees, in portal.zksyn.io/bridge/withdraw You just make sure :
- the network is ZkSync Era selected
- From: is ZkSync Era
- token From is Storj (choose max)
- To is Ethereum
- address of To can be the same ETH receive address or other receive ETH’s wallet. It will receive storj tokens there.
The fee said it was $0.05 of ETH at the moment, now You can press “continue” and the auth window will pop-up from Your Rabby wallet (or other a like, for eg. like metamask)
You have to confirm, and if You have ledger wallet connected, approve on the device.
Rabby will display a warning about the address that is unknown, but thats okay, because thats how L2 to L1 works, click “ignore” and now You will have to wait like 5-6 hours
and Your storj tokens will be avaiable to claim at the receivers wallet.
To claim, You will have to conenct to the portal.zksync.io and click claim, that will cost eth transaction, which is low at the moment, like $0.02 of ETH
So totally process of sendting Storj tokens from L2 to L1 took like $0.09 + $0.02 and 5-6 hours which is very cheap compared to other methods and swaps i tried.
Hello @mihalko,
Welcome back!
It looks like a problem with Metamask, you need to update it to the latest version and probably clear its cache. The Google AI thinks, that it might help.
See also How to fix 'Internal JSON-RPC error' on networks in MetaMask | MetaMask Help Center
Thank you gentlemen. Clearing Metamask did not help, but it went all well with signing through different (Rabby) wallet!
I am wondering what did break the Metamask plugin, maybe when I tried to bridge storj to my deposit Binance address is in unknown state to me now, who knows..
Or a Metamask’s node is behind the network. Since you used your own address to send tokens to Binance, I guess you can prove it for them and they should add tokens to your balance. Because if they sent them back, the bridge contract unlikely can support this and they could be lost.
Having same issue with metamask, thought it is just me having it
I try to send some storj to my storj account to pay for backup fee
But got the same issue
This confirms that the default Metamask node might have issues and you need to try to clear stuck transactions or switch to use other RPC provider like suggested by AI.
I had the same issue recently. Turned out to be outdated ZKSync Era configuration in my metamask wallet. I have deleted ZKSync era from metamask and added it again using new information from their documentation ZKsync Era RPC - ZKsync Docs
I had outdated RPC URL information.
After the change transaction bridged with no issues.
thanks confirm this work for me