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

Sealevel: index gas payments in relayer #2501

Closed
tkporter opened this issue Jul 10, 2023 · 0 comments · Fixed by #2585
Closed

Sealevel: index gas payments in relayer #2501

tkporter opened this issue Jul 10, 2023 · 0 comments · Fixed by #2585
Assignees
Labels
Milestone

Comments

@tkporter
Copy link
Collaborator

Blocked by #2217

@tkporter tkporter added this to the Sealevel MVP milestone Jul 10, 2023
@tkporter tkporter mentioned this issue Jul 13, 2023
@tkporter tkporter assigned daniel-savu and unassigned tkporter Jul 27, 2023
daniel-savu added a commit that referenced this issue Aug 30, 2023
### Description
 
Depends on #2583

Indexes IGP payments related to the relayer's data pda address. Unless
this address is specified in the config (`sealevel.relayer_account `),
no filtering is applied and all IGP payments are stored in the local
database.

<!--
What's included in this PR?
-->

### Drive-by changes

- Sets `HYP_BASE_GASPAYMENTENFORCEMENT` in `run-locally` for the
relayer, to test that it correctly indexes the IGP payment before
submitting the message
- A new config section (`sealevel`) is added to the relayer
- The `MessageIndexer` trait is replaced with
`SequenceIndexer<HyperlaneMessage>`, renaming `fetch_count_at_tip` to
`sequence_at_tip`. `SequenceIndexer` is now common to both the message
and igp indexers.
- The `parse_addr` macro is modified so it can be reused when parsing
the sealevel relayer address config too
- `rust/utils/sealevel-test.bash` is included because I was using it to
test locally, but I can remove it if the sealevel e2e test already does
all the steps there @mattiecnvr
- Performs a `try_into` conversion that can be removed once
#2610 is done

### Related issues

- Fixes #2501


### Backward compatibility

<!--
Are these changes backward compatible? Are there any infrastructure
implications, e.g. changes that would prohibit deploying older commits
using this infra tooling?

Yes/No
-->

### Testing

<!--
What kind of testing have these changes undergone?
-->
e2e tests but the pipeline is failing, likely fixed by
#2602

---------

Co-authored-by: Trevor Porter <trkporter@ucdavis.edu>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants