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

Ics20Withdraw skip unwinding support #84

Open
grod220 opened this issue Oct 3, 2024 · 1 comment
Open

Ics20Withdraw skip unwinding support #84

grod220 opened this issue Oct 3, 2024 · 1 comment

Comments

@grod220
Copy link
Contributor

grod220 commented Oct 3, 2024

This will be trickier than #83 and require protocol-level changes.

At the moment, we can only allow IBC-out if:

  • the token is UM
  • the ibc asset channel matches the destination chain's channel (native tokens back to their home)

After #83 is implemented, we will have the ability to request unwinding for assets routes for IBC-out as well.

Considerations:

  • What is the Skip API's registry source? They would need to recognize our asset registry that has all of the denoms present (or perhaps these need added to the cosmos chain registry?).
  • After they return the route, we'd need to take this and put it in our Ics20Withdraw memo field
  • Chains along the unwinding route should be able to acknowledge the memo field and forward on.
@github-project-automation github-project-automation bot moved this to 🗄️ Backlog in Penumbra web Oct 4, 2024
@hdevalence
Copy link
Member

Rather than use the Skip API to build the tx (since we have a different format than cosmos) we will want to grab the routing data and build the PFM data on the frontend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🗄️ Backlog
Development

No branches or pull requests

2 participants