Discussion: json-file per token about ethereum-lists HOT 9 CLOSED

Great - then I see no issue in doing it as you propose 👍

from ethereum-lists.

Essentially, are you proposing we have 1 .json file per token?

from ethereum-lists.

yes - in the repo - for consumption in apps like MEW or WALLETH they would be combined to one large json containing the array as currently

from ethereum-lists.

Gotcha. Would they be combined into one large json with something like a CI or is that down the consumers side?

from ethereum-lists.

Could be done with a CI - would add this to the scripts and kontinuum could build them like it is building the current minified jsons:

https://gateway.ipfs.io/ipfs/QmeUvS1KxRobZD5fjPeAL6jKLuyB7xve1LZ4G5zAmz2eqm

from ethereum-lists.

I agree. We discussed this as well. We will likely include token symbol, name, decimals, address in one API endpoint (and with build of MEW) and API endpoints for each individual token with the additional data.

from ethereum-lists.

now implemented in the ethereum-lists organisation: http://walleth.org/2018/02/15/ethereum-lists

from ethereum-lists.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed within 10 days if no further activity occurs. Thank you for your contributions.

from ethereum-lists.

Closing because of inactivity

from ethereum-lists.