Idea: Make it easier to display an asset given an ID and an Amount

[cronokirby]

Right now, you need to know about the Registry system, figure out what chain ID you have, manually create a specific variant of ValueView, and then pass that to the appropriate UI component.

The registry is static information, once you have picked a chain ID, so it would be nice if you could pass the registry to the top level PenumbraUIProvider, which would then let you automatically view assets given just an ID, without having to manually thread all of this logic through.

[VanishMax]

Is @penumbra-zone/client package what you're looking for? https://github.com/penumbra-zone/web/tree/main/packages/client

[grod220]

This may be a bit tricky as consumers of the registry npm package have two options: bundled vs remote. In some cases, like stakingAssetId, it's safe to grab it via the field in the bundled registry (synchronous). However, the rest of the usages of the registry should be using the remote registry (asynchronous). This allows the apps to have the latest rpcs, metadata, ibc info, etc----without having to publish a new version of the package and consumers install+redeploy.

Given the async nature, I wonder if it would be too complicated for the library to have to handle in every component that uses metadata the loading/error/loaded states.

[cronokirby]

Yeah, I guess maybe the solution there is to just accept a Registry as part of the UI context? Then the client could decide how they want to get that registry, but would then benefit from threading through the UI.

Maybe we should see how this pattern plays out in the dex explorer for a bit before coming back to this.