search

cosmos / chain-registry

Creative Commons Attribution 4.0 International
507 stars 1.22k forks source link

Duplicate images for each bridged/synthetic crypto assets #351

Open JeremyParish69 opened 2 years ago

JeremyParish69 commented 2 years ago

With our current system of cataloging images on the Chain Registry, we have and will be running into more duplicate images for bridged or synthetic crypto assets that are native to non-ibc chains. We should come up with a system the can avoid this needless duplication.

E.g., Axelar and Gravity both have bridged USDC, and on their respective chains, they both use the standard USDC token logo. Our current system would have them both upload the USDC image to their chain's directory in the Chain Registry--so, one axelar/images/usdc.png and gravitybridge/images/usdc.png.

I'd propose something like a shared _images\ folder where we can use and re-use the official/standard image for crypto tokens. (there might be cases where this can expand beyond crypto assets, e.g., for commodities or Stocks, but I don't know how those would be standardized)

_images\\\.png || .svg For example: _images\crypto\ethereum\usdc.png

and then have all assets that use that logo refer to the one copy of the image: \axelar\assetlist.json::usdc::logo_URIs: -> _images\crypto\ethereum\usdc.png \gravitybridge\assetlist.json::usdc::logo_URIs: -> _images\crypto\ethereum\usdc.png

JeremyParish69 commented 2 years ago

For cases where the asset originates off-cosmos, for now we have _non-cosmos/ethereum, and intend to do similar going forward. E.g., _non-cosmos/polkadot .../avalanche etc. This can also be used for assetlist and chain json files going forward, not just for images. This can be changed if there are any objections.