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
Right now, the same token can exist both on the default bridge and on a specific bridge.
Example would be WETH, right now on the token page you can see two WETH tokens:
0x5AEa5775959fBC2557Cc8789bC1bf90A239D9a91
0xf00DAD97284D0c6F06dc4Db3c32454D4292c6813
Right now it's not clear which one should be used.
What we can do is to add labels, e.g. "Default bridge" or "L2-native", which will provide more context on hover.
Similar case exists for wstETH.
🤔 Rationale
Having two versions of token without additional context is confusing.
The text was updated successfully, but these errors were encountered:
Bump. This took me a long time. Also, different projects (like aave) use different tokens. For WETH, it's odd that the WETH with the deposit function is not used.
🌟 Feature Request
📝 Description
Right now, the same token can exist both on the default bridge and on a specific bridge.
Example would be WETH, right now on the token page you can see two WETH tokens:
Right now it's not clear which one should be used.
What we can do is to add labels, e.g. "Default bridge" or "L2-native", which will provide more context on hover.
Similar case exists for wstETH.
🤔 Rationale
Having two versions of token without additional context is confusing.
The text was updated successfully, but these errors were encountered: