Dispute #445

Court Start Date Dispute Status Current Period Time remaining End Date
Non-Technical 2020-10-29 11:05 Already Ruled Execution Already Ruled 2020-11-13 06:17
Arbitrable Creator

Unique Votes in all the rounds

Yes No Refuse to arbitrate Pending
0 6 0 0

Round 0

Yes No Refuse to arbitrate Pending
0 3 0 0
Round 0 Vote Casting Date
No 2020-11-03 08:50
No 2020-11-02 15:06
No 2020-11-02 16:35

Round 1

Yes No Refuse to arbitrate Pending
0 7 0 0
Round 1 Vote Casting Date
No 2020-11-09 18:07
No 2020-11-09 18:07
No 2020-11-09 18:07
No 2020-11-08 13:19
No 2020-11-08 13:19
No 2020-11-08 13:19
No 2020-11-09 14:00


Evidences provided by Vagarish

Evidence #1:

To 0xf567...F617 Find your demise in the attachments.

Evidence #2:

Rebunked Dear Challenger, I legitimately am uninvolved and do not intend on funding this case regardless, only trying to contribute. You are a liar insofar as you claimed requester had submitted fake evidence and lies, which was an intentionally incorrect and unsubstantiated claim. You can confirm on github, as close to an official source for accurate logos as you can get, that requester is correct (https://avatars2.githubusercontent.com/u/73111281?s=200&v=4, https://github.com/keep3r-network). Your "evidence" (which does not destroy anything nor demonstrate to anyone that there is an attempt to confuse them other than coming from you) consists of zoomed low-resolution photos, and does not actually demonstrate that you are correct. T2CR requires the correct logo, not the most used logo. The only real argument which has been discussed is that the background resembles a screenshot out of a photo editor, but this is 100% refuted by the usage on github (linked above). I would not be surprised if challenger is the same wank I've seen in other cases submitting changes to logos around the place to fabricate evidence, given this totally unconvincing twitter account (https://twitter.com/keep3rNetwork) created Nov 2020. The argument is that the checkered pattern on the background of the logo is an error and that it should be a transparent lock. This is refuted by the fact that there is no transparent lock pattern even in your own evidence, and the most official high-res available photo demonstrates it is part of the logo (github). You were clearly not right from the start, and some allegations of lying and deceiving are absolutely self evidently correct.

Evidence #3:

Rebuttal 0x4a2c and 0xf567 Watch out for the two evidence posts below by "seemingly" uninvolved parties calling me a liar. In the attached evidence, I put together a document destroying their attempt at confusing everyone in this case. This document proves that not one of the platforms uses the icon with the transparent check background submitted by the requester. Unlike the requester and his defenders claim, neither Coinmarketcap, Coingeck, or Etherscan use that "White + Grey Checks background". This means I was right from the start and all allegations of lying and deceiving are false. I added links and screenshots so everyone can verify for themselves. Reject this submission.

Evidence #4:

Seconded Also not requester, funder, juror or involved in the case in any way, but have been keeping an eye on it since the beginning due to how obviously justice has been being miscarried and facts ignored. The funny pixels in the background are CLEARLY a part of the logo as evidenced by every occurrence both officially and on aggregators. They are not a photo editing mistake though the logo is designed as such. This can be confirmed on github https://github.com/keep3r-network/keep3r.governance/blob/master/public/android-chrome-512x512.png, both in the asset folders and the profile pics used. The previous "third party" claiming that requester had submitted "fake evidence and lies" as is "trying to deceive" and that the ""pattern" isn't used anywhere" is blatantly lying as a 5 second search will verify.

Evidence #5:

Rebuttal of juror's (0x9f11...CEF7) fake evidence I am not the requester, nor appeal funder, nor a juror, but I still want to give my opinion on this case. This transparent pattern is actually used on all the sources you just mentioned (CoinMarketCap, CoinGecko, and Etherscan). Just go to these websites, right click on the logo, and open it in another tab. As you will see, all those 3 sources use the same pattern. How weird as it looks, it's actually used everywhere. The requester DID NOT try to deceive the jurors with fake evidence and lies. Instead, juror 0x9f11...CEF7 posted fake evidence which is full of lies. I don't know what his reason is for posting fake evidence, but he just did. I want to advise the remaining jurors to do the right thing, and accept this submission.

Evidence #6:

Rebuttal Requester 0x5dCE...025C The requester is trying to deceive us with fake evidence and lies. This transparent "pattern" isn't used anywhere. It's not used on Coinmarketcap, not used on Coingecko, and not used on Etherscan. Reject this submission.

Evidence #7:

Policy says "transparent" Image looks like it had a bad screenshot out of photoshop, that background is the default stock "to be transparent" background. Authors of the projects likely messed it up when making it, why accept it as a feature? Logos like in https://tokens.kleros.io/token/0x7f173ddbceb44dcb8d4221f23906e6f2822d5c53a1be8359804cbdc653a8b440 or https://tokens.kleros.io/token/0xbf20ea2d9683261244c15302c402cb8a0d0adf392a3c0324ed1f6239887ad39d are fundamentally different than backgrounds in 445 or 469 This is the kind of thing Kleros is for. Policy prefers transparent, and this kind of logo is possible to make with a transparent background unlike logos with colored backgrounds or logos in which background is the feature that makes it visible. This is not the case here, not in 469,.

Evidence #8:

Requester was correct and should be crowdfunded https://keep3r.network/ https://keep3r.network/apple-touch-icon.png https://keep3r.network/favicon-32x32.png

Evidence #9:

part of the logo The challenger failed to see that the background is part of the logo as shown in the project website, CMC and Coingecko See attached

Evidence #10:

Token challenge Icon background should be transparent not transparent pattern
Check this Case on Kleros Resolve