[Phase-2] HIP-58 - Removal of vouchallengers

HIP: 58
title: Removal of vouchallengers
authors: ludoviko.eth, herniadlf.eth
status: Phase-2
created: 2022-07-16
updated: 2022-10-18

Simple Summary

This HIP proposes a framework to allow to make removal requests under any of the already existing reasons for removal, in cases where an account is evidently vouching maliciously.

Abstract

The proposal will allow vouchallengers to be removed if they meet the vouchallenger definition in the body of this HIP. Vouchallengers will be removed and cannot re-register after a period. This will be enforced by a modification of the PoH policy. It will not be retroactive but the historical actions will be considered if there is a new vouchallenge.

Motivation

Vouching a profile is an act of responsibly giving the recognition of a legitimate and valid submission to the registry. Since the launch of Proof of Humanity, vouchallenging as in “the act of using the vouch feature of registered humans to make another profile vulnerable to challenge” has become a serious issue. As of the day that this HIP is being written, 57 profiles have more challenged vouched profiles than valid vouches, resulting in 211 challenges and a damage to the registrants totalling around 25 ETH. and the number is growing. A series of governanceposts raising the issue and some solutions were proposed during this time. @donosonaumczuk has proposed a robust and good approach for L2 rollups and future upgrades to PoH’s smart contract, but in the meantime there are possible solutions that could make it harder (important! not impossible!) for malicious actors to continue this attack.

Specification

1. Add removal criteria
In the latest PoH policy version, there are some explicit criteria to ask for a profile removal. A new removal criteria that allows a vouchallenger to be removed can be added. We can instruct jurors that in the case of a removal of a vouchallenger, if the alleged vouchallenger challenges this removal, to rule against the vouchallenger (effectively removing them from the registry).

2. Add admission criteria
In order to avoid the vouchallenge to re-register after a removal, another modification to the document will allow the cases where the removal was due to a vouchallenge to be inadmissible for a period. That base period is 120 days (4 months). A vouchallenger that continue vouchallenging after a removal will be removed again folowing 3. Conditions to consider a vouchallenger as such. The next inadmissible periods will be calculated as base_period*(times_removed). No matter the cause of the removal.

Parameters to consider: base_period

3. Conditions to consider a vouchallenger as such

  • A profile that has vouched 2 (two) submissions that ended with ‘Incorrect Submission’ removal.
  • A profile that make a single (1) vouch for a submission that ends with ‘Incorrect Submission’ removal, after being already removed previously for being a vouchallenger.

Parameters to consider: initial_vouchallenge_threshold=2, repeated_vouchallenge_threshold=1

4. “Refuse to arbitrate” in challenges made from a re-entrant vouchallenger

If a vouchallenger is removed and then re-registered in Proof of Humanity, every new vouchallenge must be voted as “Refuse to Arbitrate”.

5. Retroactivity
This HIP is not retroactive to profiles that performed vouchallenged in the past that cross the initial_vouchallenge_threshold. However, if a previously active vouchallenger performs a new vouch for a profile that ends with ‘Incorrect Submission’ removal, it will be consider a vouchallenger and will be removed.

Rationale

  • More robust solutions than this one will come in the future, but this solution tries to ammend the situation as of today, which has brought a large impact to the registration process.
  • The parameters are very strict to stop the abuse of these days. Such parameters could be changed in future HIPs.
  • The vouch process need to be enhanced and be taken seriously.

Implementation

…More details in Phase 3… Basically, write clearly these changes in the policy. Make a PR and update the evidence in the Governor.

2 Likes

Thanks @ludovico ! As a co-author I help to create a merge of the ideas already discussed. It’s important to clarify once more that, hopefully, this proposal will be deprecated/replaced for better solutions.

The vouch means (IMHO) “I support that the submitter is a real human and he/she mets the requirements to be included in the registry”. If you vouch a submitter just to do a challenge and win some money later, you are abusing the protocol. For that reason, even though this is not the better solution, I encourage everybody to vote “Make Changes”. For sure, discuss and suggest ideas about this procedures and parameters, but let’s not delay the implementation too long.

2 Likes

Vouchallengers go home. Lets go to phase 3

1 Like

Link to proposal:
https://snapshot.org/#/poh.eth/proposal/0xb39c45c40a6d6c71d6a4ed28fa50c781a7e5e3114b825f6d62cfa4fb8650f838

I think that we should discuss the policy updates for the next phase. Here is a first version that implements the specifications from phase 2

1 Like

Thanks @nicobilinkis.eth for your comments. I think that we should wait 1 or 2 additional days. If nothing comes up, we can pass to phase 3… What do you think @ludovico ?

1 Like

I agree with that, lets proceed

1 Like

Now I see that the Snapshot poll for Phase-2 wasn’t prefixed with [Signalling] as HIP5 states:

In addition to these fields, Phase 2 proposals must also include a link to a 3-day long signalling poll on PoH Snapshot page about the proposal outcome (that contains the proposal text as well as a link to the HIP post on the PoH Forum), and it must include the option Make no changes. The Phase 2 proposal poll on Snapshot should be prefixed by [Signalling] to differentiate them from binding Phase 3 proposal votes*.

We could re-publish phase 2 just to be sure that the implementation in the governor don’t get a challenge, right? Also, We can reach the MBM but I think that a phase2 re-publish will be faster

Up to you! Here’s the list of all titles on HIPs posted in snapshot. Most of them did not have the [Signalling] tag, mostly because [Phase-2] tag is the exact equivalent:

[Fase 3] HIP: 71: Elección de moderadores
[Phase 3] HIP-72: Grant to fund a PoH airdrop solution
[Phase-2] HIP-58 - Removal of vouchallengers
HIP 73 - Removal of Clement Lesaege as mission board member
[Fase 2] HIP: 71: Elección de moderadores
[Phase 2] HIP-72: Grant to fund a PoH airdrop solution
[Phase 3] HIP 61: 15 Word Verbal Confirmation
[Phase 3] HIP 55: Explicit Sybil Resistance
[Phase 2] HIP-69 The Proof of Humanity Constitution
[Phase-3] HIP-63 Quadratic Delegations on the DAO Snapshot
[Phase 2] HIP-55: Explicit Sybil Resistance
[Phase-2][Signalling] HIP-63 Quadratic Delegations on the DAO Snapshot
[Phase 2] HIP 61: 15 Word Verbal Confirmation
[Phase 3] HIP-28: Update submissionBaseDeposit
Mission Board Election #2
[Phase 2] HIP-54: Airdrop to Democratic Heroes
[Phase 3] HIP-56 - Length of stay of the Mission Board Members
[Phase 2] HIP-28: Update submissionBaseDeposit
[Phase 2] HIP-56 - Length of stay of the Mission Board Members
[Phase 2] HIP-46: Abolish HIP-16
[Phase 3] HIP-50 Clarify which Telegram group and Twitter accounts belong to PoH DAO
[Phase 2] HIP-49: Change of Arbitrator
[Phase 3] [Binding] HIP 45: PDF → Markdown
[Phase 2] HIP-50 Clarify which Telegram group and Twitter accounts belong to PoH DAO
[Phase 2] HIP 48 - Removal of Clement Lesaege as mission board member
[Phase-2] [Signalling] HIP-45: Rewrite Policy in Markdown instead of PDF
[Phase 3] [Binding] HIP-42: Allow Spanish Phrase
[Phase 2] [Signaling] HIP-42: Allow Spanish phrase
[Phase 3] [Binding] HIP-41: Allow verbal confirmation for registrating users
[Phase-3] [Binding] HIP-40: Clarification of image rules
[Signaling][Phase 2]: HIP-41: Allow verbal confirmation for registrating users
[Phase 2][Signaling] HIP-40 Clarification of image rules
[Phase 3][Binding]: HIP-39: Election rules for elected officials
[Signalling, Phase-2] HIP-39: Election rules for elected officials
[Phase 3][Binding] HIP-38: Election of Proposers
[Phase3][Binding]HIP-36: Registration Validity Extension and Change of Renewal Period
[Phase 2][Signaling] HIP-38: Election of Proposers
[Phase-3][Binding] HIP-37 Set EPNS as a delegate for PoH notification channel
[Phase-2] [Signalling] HIP-37 Set EPNS as a delegate for PoH notification channel
[Phase2][Signalling] HIP-36: Registration Validity Extension and Change of Renewal Period
[Phase 3] [Binding] - HIP 27: Allow 1-character mistakes in displayed addresses
[Binding] [Phase-3] HIP-34 Snapshot Proposers
[Signalling] [Phase-2] HIP-34 Snapshot Proposers
[Binding][Phase-3] Clarification on UBI DAO rules
[Binding][Phase-3] HIP-30: Update PoH Governor Deposit Cost
[Phase-2] [Signalling] HIP-27: Allow 1-character mistakes in displayed addresses
[Signaling][Phase-2] HIP-30: Update PoH Governor Deposit Cost
[Signalling][Phase-2] HIP-32: Define text to be read for profile renewal
[Signalling][Phase 2] HIP-31 Clarification on UBI DAO rules
[Signalling][Phase 2] HIP-23 Snapshot Administration
[Signalling][Phase 2] HIP-23 Snapshot Administration
[Signalling][Phase 2] HIP 27: Allow 1-character mistakes in displayed addresses
[Phase-3][Binding] HIP-29: Deposit funds of the DAO to the UBI Burning Vaults
[Phase-2][Signalling] HIP-29: Deposit funds of the DAO to the UBI Burning Vaults
[Electing] Confirm Justin as the 5th board member?
[Phase-3][Binding] HIP-22: Creation of the UBI DAO
[Binding][Phase-3] HIP-17: Reduce Number of Kleros Jurors Drawn in First Rounds of POH Cases to One
[Signalling][Phase 2] HIP-22: Creation of the UBI DAO
[Signalling][Phase-2] HIP-17: Reduce Number of Kleros Jurors Drawn in First Rounds of POH Cases to One
[Binding][Phase-3] HIP-21: Amend the rules of the “Mission Board”
[Signalling][Phase-2] HIP-21: Amend the rules of the “Mission Board”
[Signalling] HIP-20: Add Proof Of Humanity login mode to cryptoauth.io
[Signalling] HIP-20: Add Proof Of Humanity login mode to cryptoauth.io
[Binding] HIP-16 HIP-16: Make admin roles of communication platforms eligible
[Binding] HIP-19: Code of Conduct for PoH Telegram channels
[Signalling] HIP-18 Communication roles
[Signalling] HIP-19: Code of Conduct for PoH Telegram channels
Add extra challenge type
[Signalling] HIP-16 HIP-16: Make admin roles of communication platforms eligible
[Binding] HIP-7: Institute a “Mission Board”
[Signalling] HIP-14: Lock the 1 $UBI/hour/person issuance rate
[Binding, Locking] HIP-10: Create a decision locking mechanism
[Signaling, Phase-2] HIP-13: Adopt a management onboarding procedure
[Signaling] HIP-7: Institute a “Mission Board”
[signalling] allow for teams to apply under the PM opening
[Signaling]HIP-10: Create a decision locking mechanism
[Binding] HIP-8: Accept 352 pixels as minimum dimension in video submissions
Can we close for new submissions to the PM position?
Let people say the phrase in their own language
[Signalling] [Phase-2]: Accept 352 as width in vertical video submissions
[Binding] HIP-5: Adopt a proper PoH DAO Governance process to ensure HIP quality
Should we institute a “Mission Board”?
The principle of transparency
The principle of humanity
Let users decide to “Accept” vouches when your profile is in vouching phase
The principle of allowing parents and carers to support submission
Do you want to create a UBI CHAIN?
HIP-4 Sell UBI to finance the DAO
HIP-3 Recruitment of workers for the DAO
HIP-2 Recruitment Procedures and worker relations
HIP-1: UBI Accrual Rate based on Vouching Activity.

The poll for this proposal at phase 2 was republished just to stay hip-5 complaint Snapshot

1 Like