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

handle native chain parties #138

Closed
bekauz opened this issue Dec 2, 2023 · 1 comment · Fixed by #143
Closed

handle native chain parties #138

bekauz opened this issue Dec 2, 2023 · 1 comment · Fixed by #143
Assignees
Milestone

Comments

@bekauz
Copy link
Collaborator

bekauz commented Dec 2, 2023

currently covenants assume that parties are interchain (non-neutron). this may not always be the case.

this will have impact on the inflow and outflow of funds from the covenant.

for inflows, we should skip the instantiation of ibc-forwarder for any native parties. the deposit address for that party will be the holder. lets combine this with using instantiate2 for the covenant instantiation flow as neutron will be launching it later this month.

for outflows, lets introduce the notion of native receivers on the interchain router. this is probably easiest by having an enum for both cases.

@bekauz
Copy link
Collaborator Author

bekauz commented Dec 5, 2023

updated description

@bekauz bekauz self-assigned this Dec 5, 2023
@bekauz bekauz added this to the v2 milestone Dec 5, 2023
@bekauz bekauz linked a pull request Dec 27, 2023 that will close this issue
@bekauz bekauz closed this as completed Jan 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant