JeremyParish69
JeremyParish69
Another thought is to remove the URL entirely. If/when this registry moves to another location, all the URLs will be inaccurate. In addition, image overrides and image name changes can...
another suggestion: -Images array contains any amount of image pointers and/or asset pointers: -An image pointer contains: --platform (folder name): required, defaults to *this folder, --name: required, the name of...
-next iteration idea allows for the "legacy" format, being the URL/URI. -still allows for local file names, and themes -still allows for inheriting another token's images ``` "images": [ {...
Most seems to be good, but I found some that aren't up to date: Missing from SLIP173: - [x] bitcanna - [x] comdex - [x] crescent - [x] cronos -...
Not only are all these chains' prefixes registered and identical in SLIP173, but now there is a data validation script as an on-PR GitHub action that throws exception when bech32...
It has been agreed upon how to handle IBC data in https://github.com/cosmos/chain-registry/pull/379
I'm unclear on what exactly you are trying to do... Which API are you using? Do you think the API is broken? Or are you just unsure what an API...
archive boolean added to endpoint object in https://github.com/cosmos/chain-registry/pull/454 is this suggestion asking for precisely that? Or is there anything else, like an 'archive nodes' array or something? Otherwise, I'd like...
> I like the idea of generalizing the bridge transfer mechanisms. I think "transition" is maybe a bit vague, so potentially a new name for that. Let's try filling out...
> I like the idea of generalizing the bridge transfer mechanisms. I think "transition" is maybe a bit vague, so potentially a new name for that. Let's try filling out...