KIP-0031: Fungible token Metadata

[CryptoPascal31]

The goal of this KIP is

• to propose a standard way for token issuers to include meta-data in their token modules codes.
• a way to allow wallets, frontends ... to retrieve and use these data

This KIP is an early draft. I'm not sure that all needs are covered.
Reviews, pros, cons, comments, improvements, and suggestions are welcome and desired

GH Formatted Markdown document link:
https://github.com/CryptoPascal31/KIPs/blob/kip-031/kip-0031.md

GH formatted interface code:
https://github.com/CryptoPascal31/KIPs/blob/kip-031/kip-0031/fungible-meta-v1.pact

And example:
https://github.com/CryptoPascal31/KIPs/blob/kip-031/kip-0031/example-token.pact

EDIT: Added 3 new paragraph to address questions

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1208668844268908

[daplcor]

I am not sure 100% about circulating supply, it might be easier/better to have a trusted ecosystem project run a daily or weekly update service for this but max supply is definitely good to capture. Worth a wider discussion at the very minimum. I'd love to hear from wallets, dexs, and other services that pull in token information.

[CryptoPascal31]

I am not sure 100% about circulating supply, it might be easier/better to have a trusted ecosystem project run a daily or weekly update service for this but max supply is definitely good to capture. Worth a wider discussion at the very minimum. I'd love to hear from wallets, dexs, and other services that pull in token information.

The idea behind this is to have "Best effort approach". Nothing is mandatory, and based of good faith and interpretation of tokens issuers. It let the responsibility for tokens to report the information themselves. Several cases could happen:

• Some tokens may have always total-supply = circulating-supply => They just return the same value
• Some tokens may decide that circulating-supply is not relevant, or impossible to estimate => They return 0.0
• Some tokens contracts may have appropriate counters and/or special internals to account the supply => They can use (circulating-supply) to return the exact value to users. (eg $BRO token, or future Linx wrapped tokens)

=> But in all cases, it's at least better than nothing.

Note that this is not incompatible with third party scripts, that could provide this information too, and spot scammers. Anyway 3rd party projects may have some limitations for exacting data if they are not aware of the internals of the token. Think for example about $BRO, whose the "non-circulating" supply is kept on a special account... and a dumb script won't be aware of that.

[daplcor]

I believe that's fine as we are talking best case for circulating supply and something is better than nothing. I would however like to consider removing the color field, as I don't feel like it adds anything.