You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
This will be trickier than #83 and require protocol-level changes.
At the moment, we can only allow IBC-out if:
After #83 is implemented, we will have the ability to request unwinding for assets routes for IBC-out as well.
Considerations:
The text was updated successfully, but these errors were encountered: