Dispute #534

Court Start Date Dispute Status Current Period Time remaining End Date
Non-Technical 2020-12-29 20:38 Already Ruled Execution Already Ruled 2021-01-06 23:25
Arbitrable Creator
Tokens 0x4a2c...0488

Unique Votes in all the rounds

Yes No Refuse to arbitrate Pending
0 3 0 0

Round 0

Yes No Refuse to arbitrate Pending
0 3 0 0
Round 0 Vote Casting Date
0x48909739001fa130ea554d45508714824c2467b5 No 2020-12-31 19:07
0x982f5698febb2b8d1b9a560228abbceafbb11568 No 2021-01-02 22:12
0xa64a17a51482f96a794c08fa3e61bb6260eeb2ca No 2021-01-03 11:22

Evidences

Evidences provided by Vagarish

Evidence #1:

Name is not the official, nor the most commonly used name The requester falsly states the official name to be "Aave interest bearing YFI(V2)", while it's not. Furthermore, there are multiple irregularities with the name "Aave interest bearing YFI(V2)": 1. That name is not used anywhere, not by any source, thus it is by fact not the most commonly used name. 2. The naming convention by Aave itself is "Aave v2", not "Aave (V2)" (https://docs.aave.com/developers/change-from-v1-to-v2). 3. There is no whitespace between "YFI" and "(V2)". The most commonly used name by all the aggregators is still "Aave YFI", they just didn't upgrade the contract address yet. The accepted naming condition is still "Aave YFI" though, so it should also be listed like that in the T2CR.

Evidence #2:

No duplicate Could the challenger point to the duplicate link? This is version 2 with a different contract address. Coin aggregators listings are V1. The official name is a better option. See listings from Aave. https://etherscan.io/token/0x5165d24277cD063F5ac44Efd447B27025e888f37 https://tokenlists.org/token-list?url=tokenlist.aave.eth Synthetix listings in T2CR were also derived from Synthetix naming convention, not the coin aggregators. Adding (V2) is for distinction from V1 since they have the same ticker.

Evidence #3:

Token challenge Incorrect name and duplicate.
Check this Case on Kleros Resolve