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
In the current implementation, users cannot select the type of token they want to receive on the destination chain. For example, if a user is bridging WETH from Holesky to Tangle Testnet, they can currently bridge using Hyperlane, but we may also support bridging via the Router protocol in the future. To enhance flexibility, users should be able to select the type of token they wish to receive, such as hypWETH or routerWETH.
Note
This should be implemented after the Router protocol is integrated into the bridge.
The text was updated successfully, but these errors were encountered:
Overview
In the current implementation, users cannot select the type of token they want to receive on the destination chain. For example, if a user is bridging
WETH
fromHolesky
toTangle Testnet
, they can currently bridge usingHyperlane
, but we may also support bridging via the Router protocol in the future. To enhance flexibility, users should be able to select the type of token they wish to receive, such ashypWETH
orrouterWETH
.Note
This should be implemented after the Router protocol is integrated into the bridge.
The text was updated successfully, but these errors were encountered: