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

Make transfer module v2 use same core paths as v1 #7687

Open
gjermundgaraba opened this issue Dec 12, 2024 · 0 comments
Open

Make transfer module v2 use same core paths as v1 #7687

gjermundgaraba opened this issue Dec 12, 2024 · 0 comments
Assignees

Comments

@gjermundgaraba
Copy link
Contributor

Currently, in transfer module v2 we have a lot of duplicate code in the keeper. Ideally, we should have the msgServer be the main place where changes are, and that the keeper sendPacket is the same for v1 and v2.

In other words, transfer module v2 implementation should be as thin as possible and reuse from v1 where it makes sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In progress
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant