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

E2E: Fee middleware counterparty payee not set #1686

Closed
3 tasks
Tracked by #1583
chatton opened this issue Jul 11, 2022 · 0 comments · Fixed by #1746
Closed
3 tasks
Tracked by #1583

E2E: Fee middleware counterparty payee not set #1686

chatton opened this issue Jul 11, 2022 · 0 comments · Fixed by #1746
Milestone

Comments

@chatton
Copy link
Contributor

chatton commented Jul 11, 2022

Summary

Write an e2e test which verifies the following:

When packet is incentivized from single sender AND counterparty payee address is not set AND token transfer succeeds, then recv fees are refunded.

Problem Definition

Proposal


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged/assigned
@chatton chatton added this to the e2e testing milestone Jul 11, 2022
@chatton chatton mentioned this issue Jul 11, 2022
33 tasks
@crodriguezvega crodriguezvega moved this to Todo in ibc-go Jul 11, 2022
@chatton chatton changed the title E2E: Fee middleware counterparty payee not set (E2E) Fee middleware counterparty payee not set Jul 20, 2022
Repository owner moved this from Todo to Done in ibc-go Aug 10, 2022
@chatton chatton changed the title (E2E) Fee middleware counterparty payee not set (E2E Fee middleware counterparty payee not set Aug 16, 2022
@chatton chatton changed the title (E2E Fee middleware counterparty payee not set E2E: Fee middleware counterparty payee not set Aug 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant