Path A: TIA on Celestia -> Osmosis -> Penumbra
Path B: TIA on Celestia -> Penumbra
The tokens that eventually end up on Penumbra would not be the same. The canonical one is the one that came from the originating chain. So if users want to take their Osmosis TIA to Penumbra they must be able to "unwind":
TIA on Osmosis -> Celestia -> Penumbra
The Skip API is specifically designed for this purpose: https://api-docs.skip.money/docs/getting-started. It can assemble cosmos messages that allow for the automatic forwarding/unwinding through the native chain of each cosmos token.
Task: in the Dex explorer ibc/shielding page, utilize the api to support IBC'ing any token from any cosmos chain to Penumbra. Should be able to query Skip for route and pass the message to cosmos-kit. After that, there should not be any asset restriction on IBC'ing in.
Not all ibc'd tokens are fungible. For example:
The tokens that eventually end up on Penumbra would not be the same. The canonical one is the one that came from the originating chain. So if users want to take their Osmosis TIA to Penumbra they must be able to "unwind":
The Skip API is specifically designed for this purpose: https://api-docs.skip.money/docs/getting-started. It can assemble cosmos messages that allow for the automatic forwarding/unwinding through the native chain of each cosmos token.
Task: in the Dex explorer ibc/shielding page, utilize the api to support IBC'ing any token from any cosmos chain to Penumbra. Should be able to query Skip for route and pass the message to cosmos-kit. After that, there should not be any asset restriction on IBC'ing in.