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

Store the packetID instead of the entire packet for forwarded packets #6636

Open
3 tasks
colin-axner opened this issue Jun 18, 2024 · 3 comments
Open
3 tasks
Labels
20-transfer needs discussion Issues that need discussion before they can be worked on type: performance Performance or storage optimizations
Milestone

Comments

@colin-axner
Copy link
Contributor

Summary

Following #6635, transfer could store only the packetID for the packet received which generated a forwarded packet. Currently we store the entire packet, when only the packetID information is needed


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged/assigned
@colin-axner colin-axner added 20-transfer type: performance Performance or storage optimizations labels Jun 18, 2024
@colin-axner colin-axner added the needs discussion Issues that need discussion before they can be worked on label Jun 18, 2024
@NisTun
Copy link
Contributor

NisTun commented Jun 24, 2024

Can I handle this issue @colin-axner ?

@colin-axner
Copy link
Contributor Author

Hi, @NisTun. Thanks for asking and thanks for your interest. Unfortunately you cannot, the issue is on hold and requires changes to core IBC before it can be worked on. Once that is done, I think the team would like to handle this issue ourselves

@colin-axner
Copy link
Contributor Author

This issue is on hold until informalsystems/hermes#4078 is addressed. I have moved the issue out of the v9 milestone and into v10, but the exact release it can be addressed in is dependent on the relayers

@crodriguezvega crodriguezvega added icebox Issues that we will not address for the time being and removed icebox Issues that we will not address for the time being labels Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
20-transfer needs discussion Issues that need discussion before they can be worked on type: performance Performance or storage optimizations
Projects
Status: On hold ❌
Development

No branches or pull requests

3 participants