Michael Wuergler

This list is auto-generated from the cryptocompare API. So to see changes on this list, you would need to request the change from https://www.cryptocompare.com/(use the `Contact us` link at the...

Nice idea! I am all for making this list more useful. PR welcome, otherwise I can try to get to this sometime soon.

I think maybe we can generate both lists, one with more detail, and the one we are generating currently, and the users can pull in the list they want.

@angelexevior thanks for the kudos! :) How do you see the current list co-existing with this list that was proposed by @wmbutler above? The current list has a structure of:...

@angelexevior, another option is just maintain a few different lists, and the user just pulls in the list they need. There are use cases for having different types of lists...

@wmbutler I like your proposed structure ```json { "bts" : { "name" : "Bitcoin", "uri" : { "coin": "bitcoin", "amount" : "amount", "message" : "message", "label" : "label" } }...

@angelexevior > Correct me if i'm wrong but the list is just a flat file, not generated by someone automatically(or semi). This list _is_ generated semi-automatically by running `npm run...

> How about the API implementation (.BTC vs .BTC.name)? `.BTC` 👍

> Suggestions for the name of 2nd json file with images? Ideas: - currencies-logos.json - currencies-meta.json (future-proofing, but semantic) - currencies-plus.json (future-proofing, but semantic)

Looks good to me. My main issue is with the GitHub hosting. If anyone is going to use this in a real application they would want the images delivered by...