JeremyParish69

> small nit pick — should we standardize on something like `-testnet`, in this case would be `osmosis-testnet` with hyphen? > > just my 2c, happy either way ;) >...

what should we do when it is the same? just add a '...testnet' suffix? e.g., 'osmosistestnet' ?

resolved by @pyramation via #680

looks good. With your permission, I'd like to update the token images again once merged, because many dApps will crop the image to an inner circle, and based on how...

Implemented Dan's idea to move the specification of the Cosmos Chain Registry folder '_non-cosmos/' from the platform field to its own property which defaults to false. True means the platform...

Implemented @pyramation idea to move the specification of the Cosmos Chain Registry folder '_non-cosmos/' from the platform field to its own property which defaults to false. True means the platform...

was addressed with the addition of traces: https://github.com/cosmos/chain-registry/pull/558 https://github.com/cosmos/chain-registry/pull/731

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...

Here is my schema suggestion: ``` "oracle_ids": { "type": "object", "properties": { "coingecko_id": { "type": "string" }, "coinmarketcap_id": { "type": "string" }, "osmosis": { "type": "object" "properties": { "osmo_spot": {...

> I like this, but how do we make sure this is updated after a governance proposal changes the param? Responsibility of chain.json maintainers? Is this something the lens tool...