Inconsistencies in README and registry Re: maxSupply

This is minor, but the README specifies maxSupply can be provided in integers or URLs, but I've noticed a handful of tokens provide the assetID here.  It makes sense to supply assetIDs here, but it's just not reflected explicitly in the README.

examples: (linked to .yaml)

[**iBTC**](https://github.com/minswap/minswap-tokens/blob/main/src/tokens/f66d78b4a3cb3d37afa0ec36461e51ecbde00f26c8f0a68f94b6988069425443.yaml) - f66d78b4a3cb3d37afa0ec36461e51ecbde00f26c8f0a68f94b6988069425443

[**iETH**](https://github.com/minswap/minswap-tokens/blob/main/src/tokens/f66d78b4a3cb3d37afa0ec36461e51ecbde00f26c8f0a68f94b6988069455448.yaml) - f66d78b4a3cb3d37afa0ec36461e51ecbde00f26c8f0a68f94b6988069455448

[**MyUSD**](https://github.com/minswap/minswap-tokens/blob/main/src/tokens/92776616f1f32c65a173392e4410a3d8c39dcf6ef768c73af164779c4d79555344.yaml) - 92776616f1f32c65a173392e4410a3d8c39dcf6ef768c73af164779c4d79555344

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Inconsistencies in README and registry Re: maxSupply #103

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Inconsistencies in README and registry Re: maxSupply #103

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions