Dispute #114

Court Start Date Dispute Status Current Period Time remaining End Date
Non-Technical 2019-10-12 19:22 Already Ruled Execution Already Ruled 2019-10-22 11:03
Arbitrable Creator
Tokens 0x80c1...b322

Unique Votes in all the rounds

Yes No Refuse to arbitrate Pending
1 1 0 1

Round 0

Yes No Refuse to arbitrate Pending
1 1 0 1
Round 0 Vote Casting Date
0x1d899a06fb04b276aedd87ee3a9d937292884f4a Pending
0x27fe00a5a1212e9294b641ba860a383783016c67 No 2019-10-18 15:52
0x5e7b645d5bf86750cb1913122ba8a8545e2a9fd1 Yes 2019-10-15 06:05

Evidences

Evidences provided by Vagarish

Evidence #1:

Correct naming is OVCODE See pdf file.

Evidence #2:

Evidence that OVCode is the correct name. OVCode is the asset correct name. One can check the following links. Main site: https://ovcode.com/ Facebook: https://www.facebook.com/OVCodeSwitzerlandAG/ Twitter: https://twitter.com/OVCode Medium: https://medium.com/@OVCodeSwitzerlandAG Pinterest: https://www.pinterest.ch/OVCodeSwitzerlandAG/ Considering those evidence the name is correct and token should accepted on the list.

Evidence #3:

Token challenge Incorrect name. Should be OVCODE.
Check this Case on Kleros Resolve