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
{{ message }}
This repository has been archived by the owner on Sep 27, 2023. It is now read-only.
From my understanding, tokens transfers from NEAR to ETH can take from 0 to ~16 hours to confirm. This is quite a wide range and I think that not having an estimated time is poor UX since the user:
might check for confirmation multiple times before the transfer is effectively confirmed,
doesn't know what to expect.
Proposal
Add an approximate countdown showing the number of hours until the next batch of confirmations on Ethereum, as added in the pic below in green. The text "this can take around 16 hours" might be modified as well.
Edit: another solution (only works for advanced users) might be to provide a link on Etherscan to the Ethereum smart contract responsible for proofs validation, so that the user can check when were the last confirmations and use that to anticipate the next.
The text was updated successfully, but these errors were encountered:
0xEffAlt
changed the title
Add an countdown for NEAR -> ETH transfers confirmations
Add a countdown for NEAR -> ETH transfers confirmations
May 28, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
From my understanding, tokens transfers from NEAR to ETH can take from 0 to ~16 hours to confirm. This is quite a wide range and I think that not having an estimated time is poor UX since the user:
Proposal
Add an approximate countdown showing the number of hours until the next batch of confirmations on Ethereum, as added in the pic below in green. The text "this can take around 16 hours" might be modified as well.
Edit: another solution (only works for advanced users) might be to provide a link on Etherscan to the Ethereum smart contract responsible for proofs validation, so that the user can check when were the last confirmations and use that to anticipate the next.
The text was updated successfully, but these errors were encountered: