[General] ETH Sepolia L1NativeTokenVault doesn't have enough $ETH to finalize my withdrawal #971
-
Team or ProjectNo response ZK chainzkSync Era Sepolia EnvironmentTestnet L2 block numberNo response Provide a brief description of the functionality you're trying to implement and the issue you are running into.P.S. Didn't know which label to add here, nothing felt super appropriate. Also cc @uF4No I deposited a few hundred ETH from Ethereum Sepolia to zkSync Era Sepolia a long time ago. Today, I tried withdrawing 100 ETH out. The withdrawal on L2 went through, but it's not letting me claim on Ethereum Sepolia. I debugged the Tenderly Simulation = https://www.tdly.co/shared/simulation/c4104834-3ca8-4745-9c68-21d2a292597a Now I'm not sure how this is even possible? Isn't the ETH supposed to be locked on the L1 when deposited into the L2? How can L1 contracts not have enough ETH to pay me? Anyway - now my funds are stuck. I lost them on L2 and cannot claim on L1. I would love to claim them on the L1 asap - so please let me know what can be done about this. Repo Link (Optional)No response Additional DetailsNo response |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
@haardikk21 We are sorry that you experienced this issue :( We are not sure why it happened, most likely we did not migrate the ETH token balance during the finalization of the v26 upgrade there. I have completed the migration of ETH to L1NativeTokenVault. It should now have enough funds: https://sepolia.etherscan.io/address/0x746DBBa1edfBe1b547c87189eFE91B77d53d9E39. This is most likely a small issue in the scripts that we used, we will investigate. Thank you for the report! |
Beta Was this translation helpful? Give feedback.
@haardikk21 We are sorry that you experienced this issue :( We are not sure why it happened, most likely we did not migrate the ETH token balance during the finalization of the v26 upgrade there. I have completed the migration of ETH to L1NativeTokenVault. It should now have enough funds: https://sepolia.etherscan.io/address/0x746DBBa1edfBe1b547c87189eFE91B77d53d9E39.
This is most likely a small issue in the scripts that we used, we will investigate. Thank you for the report!