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

Make the bridge transfer time dynamic based on the chain(s) being used #1350

Open
parrot9design opened this issue Jun 18, 2024 · 1 comment

Comments

@parrot9design
Copy link
Collaborator

During my testing, the average cross-chain transaction takes anywhere from 20 seconds to 2 minutes.

The Swap and Transfer tabs currently display a transfer time of ~30s for every transaction, which is disingenuous when the rest of the metadata is transaction-specific.

Let's figure out the best way to provide an accurate estimation, whether we run a series of transactions ourselves to get an average for each route (less than optimal), or display the most recent transfer time, like Omm does for the sICX unstaking time:
Screenshot 2024-06-18 at 2 01 12 PM

The main downside of the latter approach is if the last transfer time was quite high, that's what we'll be promoting to users.

@FezBox
Copy link
Collaborator

FezBox commented Jul 29, 2024

we will revisit this once the new xcall scan API is done

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

2 participants