Resuming here a suggestion by @ligi :
Removed some extra spaces - also wondering if we should DRY up the tokens and just reference to the tokens repo - feels a bit WET this way
We are currently duplicating two sets of info: 1) info on the token contract (symbol, decimals, name, etc) and 2) on the project (github, support email, etc).
Regarding (1), we could drop symbol, decimals, and name, and just reference the address, so clients can use it to retrieve the missing info from the tokens list. On the other hand, these are attributes that rarely change, and including them here can save a client a roundtrip to the tokens list.
As for (2), I agree that it is info more annoying to track in both places. However, I can see a case where a project is not identified by a token, so we don't have an entry to reference.
Thoughts?
Resuming here a suggestion by @ligi :
We are currently duplicating two sets of info: 1) info on the token contract (symbol, decimals, name, etc) and 2) on the project (github, support email, etc).
Regarding (1), we could drop symbol, decimals, and name, and just reference the address, so clients can use it to retrieve the missing info from the tokens list. On the other hand, these are attributes that rarely change, and including them here can save a client a roundtrip to the tokens list.
As for (2), I agree that it is info more annoying to track in both places. However, I can see a case where a project is not identified by a token, so we don't have an entry to reference.
Thoughts?