ics20 clarification

[colin-axner]

No description provided.

[ethanfrey]

Better explanation than I had. Happy to merge this in.

I still have an open question what denom looks like when it goes for the second hop. Do we keep prepending multiple hops, or hash then prepend? Or is this left up to each implementation to determine and the sink just needs to know that {denom} is understood by the source?

[colin-axner]

I still have an open question what denom looks like when it goes for the second hop. Do we keep prepending multiple hops, or hash then prepend? Or is this left up to each implementation to determine and the sink just needs to know that {denom} is understood by the source?

Hashing is outside the scope of ics20. Hashing the full denomination is a characteristic of ibc-go to avoid denomination validation errors from the SDK. It seems IBC go to market is adopting this as a cornerstone aspect of ics20 so we might want to add it as a recommendation for internal use.

ics20 needs the entire denomination unhashed. Multiple hops just adds the prefix. I wrote up a simplified explanation here. The letter used in the example would just be the destination port/channel

To answer the question directly, we keep prepending once the denomination is received.