We are using the Cosmos chain registry and the Namada chain registry in Namadillo, and we should decide how we want to access these. We don't know which chains/assets we need to look up at compile time, so a static configuration won't work.
Possibilities:
Currently as of #1216 we are loading the whole cosmos registry at once. This leads a jump in the bundle size (from an initial ~5kB jumps to ~8kB).
Still use the registry packages installed from npm, but dynamically import what we need. Better for bundle size but if registry information changes then Namadillo needs updated.
Call a remote server for the registry information. Keeps bundle size lower and no need to update Namadillo to get the latest information, but relies on server being up for Namadillo to work.
We are using the Cosmos chain registry and the Namada chain registry in Namadillo, and we should decide how we want to access these. We don't know which chains/assets we need to look up at compile time, so a static configuration won't work.
Possibilities: