Need dependable mechanism for getting Vault issuers into your wallet

[Tartuffo]

A pet naming the wallet maintains and imports into the DApps.

One namespace shared across all user interfaces. Also needs to work for Pegasus imports.

[michaelfig]

We intend to use ibc-go's transfer module (running on the transfer port) to send tokens to the Agoric chain. Then, we will "bless" the relevant denom (ibc/xxx) to correspond to a bank purse, so that every wallet automatically gets an ERTP purse for the asset, pegged to their Cosmos ibc/xxx token balance.

[Tartuffo]

Currently, the Vault UI suggests issuers and what to call them, which are stored in the wallet.
Wallet Bridge is where DAPP communicates with user Wallet, Wallet has objects -> paths.
Needs to be a pet name path, in the Agoric supported naming hub. So user's pet name for the naming hub, + the path in the naming hub.
The Vault is the pet name, Vault.ATOM would be the path for ATOM.
Governance should install a naming hub.
The missing piece is to be able to say "sign me up for (the chain's gov-approved) standard names, or Joe's standard names)
one question is whether we show the path explicitly in the UI, or make that available via mouse-over.

[michaelfig]

If the assets already need to be exposed by the bank vat (like IBC transfer assets), we have an automatic solution. This ticket is for assets that aren't part of the bank.

[dckc]

I talked about this with @michaelfig .

The VBANK currently provides a solution in this space that seems adequate for some near-term scenarios: issuers for assets added to the VBANK get into wallets of all users. The ATOM issuer used for vaults will be created via VBANK.

It doesn't accomodate Pegasus, decentralized lists, etc.

[Tartuffo]

This issue is about getting a denom into the purse.

1. I have to know the name of the denom up front. You need the IBC path (a hash).
2. Write about 30 lines of code, submit to Gov vote, and execute the 30 lines on the vote passing.

Making this less centralized is not needed for MN-1.

[dckc]

@dtribble and @michaelfig refined the design above:

• subscription for updates to the naming hub
• object to name(s) lookup (Naming hub: interface to look up an Issuer object and get a (set of) name(s) #5107)
• provide same interface from VBANK

[dckc]

I suppose this recent problem report means this issue came up in production:

• clarify why tokens from unsupported IBC paths do not show up in smart wallet #6507

it would be nice if

• our wallet followed the convention of defaulting to the cosmos chain registry for IBC asset naming.
• users could also add unregistered tokens or rename registered tokens

As to solutions, at one point we planned to do these two; that plan still makes sense to me:

• expose VBANK brand list via chainStorage RPC #5762
• Naming hub: interface to look up an Issuer object and get a (set of) name(s) #5107

Supporting the chain registry would be another work item. Getting the data from github on chain would need something like oracle price submission. I suppose it's possible for the wallet UI to query github rather than the chain, but that mixes trust models in a weird way.

Supporting user-configured names -- basically petnames -- would be another item.

cc @otoole-brendan @michaelfig @ivanlei @erights