Multiple assets with same name and different trace are shown on the Select Asset dropdown

[neocybereth]

I'm seeing this in the work on #1687.

From this log you can see that it's the same asset just coming from different traces:

Sidenote, this trace seems like it's a bug with double transfer/channel-7

'transfer/channel-7/transfer/channel-7/uosmo'}

[neocybereth]

@brentstone @euharrison any particular way you'd like me to go about solving this? Do I merge the similar traces or is this expected etc?

[brentstone]

So hopefully we don't ever run into this on mainnet, it's happening bc on Housefure some older channels expired and we had to open new ones.

@pedrorezende @euharrison def curious what is going on with the transfer/channel-7/transfer/channel-7/uosmo.

Ideally in my mind, we would only use an alias for a single instance of a given token type and then use the transfer/channel-X/yyyy string otherwise. So in this example, transfer/channel-7/uosmo would appear as Osmosis while transfer/channel-0/uosmo would appear as transfer/channel-0/uosmo. Would this be done using the chain registry? How does Namadillo get Osmosis for the token anyway?

[euharrison]

another ref #1672

[euharrison]

Agree, we should render the tnam... for transfer/channel-0/uosmo as the easiest path, or render transfer/channel-0/uosmo if we create this map on the code

Related to the transfer/channel-7/transfer/channel-7/uosmo, @Fraccaman @grarco it came from the indexer, do you have any idea why it's happening?