It is possible for users to hold and deposit with IBC tokens (and factory tokens) that are unknown to the official chain-registry data, and are not included in our custom ENV var data that adds extra known assets. These assets should still be displayed to the end user as they do exist. We should find reasonable ways to display these types of tokens.
In general there is an issue in that we attempt to display all possible IBC tokens that could exist on Neutron related to previous issue:
this exists in the TokenPicker list of "All Denoms" and the Bridge page list of "All Bridgable Denoms". This is not such an issue on Testnet (about 5 bridgable tokens), but is an issue on mainnet which has about 300 "bridgeable tokens" >100 of which are IBC tokens on the Osmosis chain.
It is possible for users to hold and deposit with IBC tokens (and factory tokens) that are unknown to the official chain-registry data, and are not included in our custom ENV var data that adds extra known assets. These assets should still be displayed to the end user as they do exist. We should find reasonable ways to display these types of tokens.
In general there is an issue in that we attempt to display all possible IBC tokens that could exist on Neutron related to previous issue:
this exists in the TokenPicker list of "All Denoms" and the Bridge page list of "All Bridgable Denoms". This is not such an issue on Testnet (about 5 bridgable tokens), but is an issue on mainnet which has about 300 "bridgeable tokens" >100 of which are IBC tokens on the Osmosis chain.