This is a curated list of Ethereum blockchain tokens.
Name And Ticker
The name should be the most commonly used display (marketing) name to refer to the token. It does
not necessarily need to be the canonical or official name given by project creators nor the one in
the token contract.
Token and coin suffixes should be avoided, unless a name with suffix is already well established.
Name and ticker should be treated like brand names (spelling-wise). This means that the
correct spelling is dictated by the project owners, unless consensus forms around a
different spelling.
Symbol
The symbol should represent the token.
The symbol should be a transparent PNG (Portable Network Graphics) of at least 128x128 and at most 2500x2500 pixels. It should
not be more than 1 Megabytes. It should be centered and take most of the space
available in the image. It should not include the project or token name unless the
symbol always includes it. It should be of a definition high enough such that it should
not appear pixelated or blurry unless those are on-purpose features of the symbol.
The logo should be fully included.
Warning
Contract addresses are an attack vector and should be checked carefully.
In case of duplicates, only the first submission should be accepted. The most
recent submissions appear highest in the list.
So which items do you want to add to the proposal? I can try and compare with the current policy, but I noticed you also changed some language so I think it would make sense to point out specific things you want to change.
Thing is I agree with some of the additions you made in your rewrite. I also disagree with some of the things you wrote. But I don’t know which rules other people would want to see included or rewritten. Writing it as a whole new proposal makes it hard to discuss it’s substance or entirely agree with it, especially since there seems to be no motivation for any of the changes.
For example I noticed you rewrote this rule to include only Token and coin suffixes which is something I highly disagree with.
So I guess I would not be in favor of your proposal.
Well in my specific example of the suffix rule, I think there are way more suffixes that should be avoided like version numbers etc. We can’t possibly know which ones will appear so that’s why the catch-all is there. I see no reason to rewrite that.
@clesaege When do we vote in this proposal? Do we wait on the other proposals so we can batch them?
I guess I do not really understand what you’re trying to say. The argument for listing all tokens, ERC20 or not, migrated or not, is that we don’t know which dApps will pull data from the TCR. Say for instance I wanted to make a trustless dApp tracking my historical token amounts, or which cryptokitties I bought/sold. Like you said, some new tokens aren’t even ERC20.
I see, old delisted migrated tokens can be OK for historical reasons.
I wish it was clearer. Maybe addition of “deprecated” badge?
Otherwise - as I said - it can be dangerous.
Kleros has some reputation.
TCR has some reputation.
Hundred thousand ETH worth of dollars.
Someone can have a look, see something, assume “yeah it’s legit”
That’s why adding old / migrated / scam / deprecated tokens is dangerous, unless we add badges to them.
I did not participate in the discussion earlier because I couldn’t care less
The 128px or 200px does not matter to me, the whole TCR is just an experiment in governance and creating loads of cases… I think it succeeded
EDIT / UPDATE: couldn’t care less about he exact wording. One way or another it’s an experiment in governance, decision making, reaching consensus.
I joined the discussion late. I genuinely think that tokens that are migrated are no longer cool. But yeah, historical reasons. To indicate that - need to add badge. Also a bounty to add badged. Bounty for removal: Bounty discussion - rewards for removing tokens? - #4 by clesaege