chain-registry icon indicating copy to clipboard operation
chain-registry copied to clipboard

Schema Versioning

Open sunnya97 opened this issue 3 years ago • 4 comments

How can we do versioning for the schemas so that we know when there's breaking changes?

sunnya97 avatar Jan 05 '22 00:01 sunnya97

I think we should use a standard that allows for this, most likely IPLD (updating docs) or DID.

hxrts avatar Jan 09 '22 08:01 hxrts

Will be wanting to use chain reg as a sub-module, so this seems increasingly important.

JeremyParish69 avatar May 19 '22 21:05 JeremyParish69

Will be wanting to use chain reg as a sub-module, so this seems increasingly important.

Interesting. Can you say more about your use-case @JeremyParish69? A git submodule?

hxrts avatar May 22 '22 10:05 hxrts

yes, @hxrts , as a git sub-module to be used as a reference for chain and asset information, IBC channel info, token images, etc., and remove all local hard-coded information about tokens and chains. Any changes about a token, e.g., changing symbol of LUNA to LUNC, desired to take effect on Osmosis would instead be done on the chain registry, and anything we need to construct will be done so through lookups using only ( chain_name + coinMinimalDenom ) as primary keys, which are assumed to be immutable.

JeremyParish69 avatar May 30 '22 23:05 JeremyParish69