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

Fast path estimate doesn't account for buffer and xERC20s #5945

Open
3 tasks
just-a-node opened this issue Mar 29, 2024 · 1 comment
Open
3 tasks

Fast path estimate doesn't account for buffer and xERC20s #5945

just-a-node opened this issue Mar 29, 2024 · 1 comment
Assignees

Comments

@just-a-node
Copy link
Collaborator

just-a-node commented Mar 29, 2024

Background

Fast path estimates should currently account for a buffer of current available router liquidity. Right now that is not the case for some paths/assets.

Also, xERC20s need to check router liquidity as wlel.

Definition Of Done

UI should show slow path time estimate if transfer amount > 70% of total available router liquidity. Additionally, only the top 4 routers by available liquidity for a specific asset should be considered in the total available liquidity of this estimate.

Tasks

  • Identify whether the buffer rule is applied and fix if not
  • Identify if only top 4 routers is being considered and fix if not
  • Identify if xERC20s are handling available router liquidity
@just-a-node
Copy link
Collaborator Author

A more efficient method to use in the UI for determining fast path: #6018

@just-a-node just-a-node added the ui 🎨 Component category label Apr 18, 2024
@just-a-node just-a-node changed the title Fast path estimate doesn't account for buffer Fast path estimate doesn't account for buffer and xERC20s Apr 18, 2024
@just-a-node just-a-node removed the ui 🎨 Component category label May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant