Dispute #825

Court Start Date Dispute Status Current Period Time remaining End Date
Humanity Court 2021-06-11 06:55 Already Ruled Execution Already Ruled 2021-07-01 15:32
Arbitrable Creator
Proof of Humanity

Unique Votes in all the rounds

Yes No Refuse to arbitrate Pending
0 8 0 1

Round 0

Yes No Refuse to arbitrate Pending
0 3 0 0
Round 0 Vote Casting Date
No 2021-06-21 20:35
No 2021-06-21 20:33
No 2021-06-19 08:33

Round 1

Yes No Refuse to arbitrate Pending
0 6 0 1
Round 1 Vote Casting Date
No 2021-06-26 01:26
No 2021-06-23 22:58
No 2021-06-23 22:58
Pending
No 2021-06-24 14:26
No 2021-06-27 09:20
No 2021-06-24 21:07

Evidences

Evidences provided by Vagarish

Evidence #1:

Wrong challenge type I insist: Duplicate and Incorrect Submission are mutually exclusive. "This kind of challenge does not claim that the submitter is trying an attack". As ruled in 829, 830, 831, 834 (and probably in 861, 864) profiles controlled by Cryptoevangelist are an attack and should be treated as duplicates.

Evidence #2:

Challenge types matter This challenge type does not comply with the policy and makes POH vulnerable. Therefore it should be rejected so that this submission gets later challenged as a "Duplicate". See doc attached.

Evidence #3:

The jurors must vote NOT to accept this submission The submitter is not the owner of the Ethereum address and perhaps he is recently dead because he has not uploaded a proof of life in this process, as required by the registration policy. ----- Please, see attached evidence

Evidence #4:

The submitter did not yield proof of life It could not do it because it is dead or does not have access to the Ethereum address. As the registration policy says: "Submitters not able to give recent proof of life are to be considered deceased". Therefore the request to register should not be accepted.

Evidence #5:

Reject the "Incorrect Submission" challenge The voucher should be removed, because this submission belongs to a person who is already registered with other addresses. I agree: this is a duplicate, not an incorrect submission.

Evidence #6:

This is a duplicate, not an incorrect submission For the reasons mentioned in the file attached, I'm contributing to the loser's side of the appeal and I invite the entire POH community to support this action.

Evidence #7:

The submitter didnĀ“t provide proof of life Submitter did not provide proof of life after the challenge. Submission non-compliant with the registration policy. Registration policy: "Submitters not able to give recent proof of life are to be considered deceased". This is why the request to register should not be accepted.

Evidence #8:

Proof of Willingness 2 Work 4 Change from Inside I am trying... Please look past this flawed system for your answers. My hands are tied behind my back here.

Evidence #9:

Still no second video as requested 4 days ago This is a puppet profile of Agent99 as shown by the common modus operandi, the vouch graph (Agent99 -> FarEy -> PierreDeCaz -> MexMax -> El Gato) and Agent99's own admissions. Absence of requested 2nd video indicates Agent99 couldn't find this puppet again. Details in case 833 and attachment.

Evidence #10:

Direct interaction request There seems to be a lot of cases like this one. I think to try to find out what is happening, it would be good for the individuals to provide jurors a time they are available on jitsi (https://meet.jit.si/POHDispute) to interact directly.

Evidence #11:

Submitter must provide new video evidence See attachment.

Evidence #12:

Challenge Justification ownership of the ETH address is the implicit rule in element#4 and this guy's submission go against it as well as the these other similar pic/videos taken on the streets https://app.proofofhumanity.id/profile/0x2727c97172b496b60f6e97865b49a0ca34a3f477 https://app.proofofhumanity.id/profile/0xc082fd778b21edd415641138981f0df329f5109f https://app.proofofhumanity.id/profile/0x7b62f8495cf88b4716da3f420cc75de0404aa9a7 https://proof-of-humanity.netlify.app/profile/0x5a4c3277da56c1920d176bc3a22c8e04e64cc1f7

Evidence #13:

Registration
Check this Case on Kleros Resolve