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

connect: receipt destination tx hash not always set #659

Open
kev1n-peters opened this issue Aug 7, 2024 · 0 comments
Open

connect: receipt destination tx hash not always set #659

kev1n-peters opened this issue Aug 7, 2024 · 0 comments

Comments

@kev1n-peters
Copy link
Contributor

There are some cases where the destination tx hash won't be set even after the tx is completed. We should try as best we can to find the destination tx hash (check wormholescan or fall-back to fetching on-chain data). This is applicable to every route.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant