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

Payments for the non abacus works IGP should be highlighted on the explorer #1920

Open
Tracked by #1578
nambrot opened this issue Mar 9, 2023 · 7 comments
Open
Tracked by #1578
Assignees

Comments

@nambrot
Copy link
Contributor

nambrot commented Mar 9, 2023

Once #1736 gets in, indexed payments on the abacus works IGP will be surfaced. However, if a different IGP was used to pay (which may result in non-delivery), the dev can be confused due to the explorer error message of "origin IGP not paid". The explorer should try to find those payments and surface those, with an indication that that maybe a reason for non-delivery

@nambrot
Copy link
Contributor Author

nambrot commented Mar 22, 2023

@jmrossy probably overlap with the PI IGP work in #1984 as well

@nambrot
Copy link
Contributor Author

nambrot commented Mar 24, 2023

This detection should also surface if the inner IGP was used and not the overhead igp (when using the abacus works relayer)

@jmrossy
Copy link
Contributor

jmrossy commented May 12, 2023

Halfway there with hyperlane-xyz/hyperlane-explorer#40 but still more to do

@nambrot
Copy link
Contributor Author

nambrot commented Mar 1, 2024

A lot of overlap with #2229 , but this is independently useful for PI chains

@avious00
Copy link
Contributor

avious00 commented May 13, 2024

@jmrossy would it be possible to see which IGP/relayer was used as a byproduct of this? e.g. a community dev asked to know

if that's a different ask, can create a separate issue

@jmrossy
Copy link
Contributor

jmrossy commented May 14, 2024

@avious00 it would be a pre-requisite for this yes.

@jmrossy
Copy link
Contributor

jmrossy commented May 16, 2024

Related: #1999

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

3 participants