You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I do notice /experience an ambiguity in gas estimate when trying to bridge while using the Hyperlane CLI
For instance while bridging Warp route tokens like USDT from Scroll to Base. There's often an incorrect / ambiguity in gas estimate of 0.0312 eth on both source and destination chains which is rather outrageous. And especially for first timers and inexperience users, they might feel so confused and unsure about being on the right track while carrying out the task
However because i have enough gas on both source and destination chains. I was able to bridge the warp token successfully while using my active wallet
Solution
I will love to see a situation whereby gas estimation can be read accurately, hence removing a situation of unnecessary ambiguity. Also I suggest if gas can only be requested on the source chain rather than both the source and destination chains while bridging warp tokens
The text was updated successfully, but these errors were encountered:
Problem
I do notice /experience an ambiguity in gas estimate when trying to bridge while using the Hyperlane CLI
For instance while bridging Warp route tokens like USDT from Scroll to Base. There's often an incorrect / ambiguity in gas estimate of 0.0312 eth on both source and destination chains which is rather outrageous. And especially for first timers and inexperience users, they might feel so confused and unsure about being on the right track while carrying out the task
However because i have enough gas on both source and destination chains. I was able to bridge the warp token successfully while using my active wallet
Solution
I will love to see a situation whereby gas estimation can be read accurately, hence removing a situation of unnecessary ambiguity. Also I suggest if gas can only be requested on the source chain rather than both the source and destination chains while bridging warp tokens
The text was updated successfully, but these errors were encountered: