Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

incorrect routes is fetched for sender in case when L2 prefix is used for receiver address #19846

Open
VolodLytvynenko opened this issue Apr 30, 2024 · 0 comments

Comments

@VolodLytvynenko
Copy link
Contributor

Steps:

  1. Recover user with available assets on Mainnet and on any L2 network
  2. Enter the receiver address with L2 network prefix for address (example: opt:0x8d....23)

Actual result:

The mainnet route is fetched for the sender, and the L2 route is fetched for the receiver

Example:
Sender: Mainnet route -> Receiver: Optimism route
image

fees.mp4

Expected result:

The most optimal route based on fees should be fetched. For example, both sender and receiver should have the Optimism route fetched when the sender intends to send assets to an address with the opt prefix.

Example:
Sender: Optimism route -> Receiver: Optimism route

reference
https://discord.com/channels/1210237582470807632/1217175448828514344/1234414135241085019

Additional info:

Same issue is on the desktop
image

OS:

IOS, Android, Desktop

Devices:

  • Pixel 7a, Android 13
  • iPhone 11 Pro Max, IOS 17
  • Desktop master status go 0.179.8

Logs

logs.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

1 participant