Skip to content
This repository has been archived by the owner on Jun 17, 2020. It is now read-only.

O> Checkmating multiple accounts by coop members #409

Closed
5 tasks
Keaycee opened this issue Feb 23, 2018 · 5 comments
Closed
5 tasks

O> Checkmating multiple accounts by coop members #409

Keaycee opened this issue Feb 23, 2018 · 5 comments
Assignees
Labels
Security zz-Operations NEEDS SPONSOR guides: @TrenchFloat, @jimscarver @Tonyprisca13

Comments

@Keaycee
Copy link
Contributor

Keaycee commented Feb 23, 2018

There have been dialogues about coop members having multiple membership account to enable their malicious act other than a helpful contribution to RChain cooperative. I think we can come up with an effective measures to combat double membership account by coop members.

How do we checkmate accounts?

TIPS

  • Reviewing all coop members accounts that signed up

  • Reviewing each accounts and it's means of identification (I.D cards)

  • Verification of coop members every month before getting a reward. Members can be group batch after batch for a video verification with a corresponding means of identification (I.D cards)

  • Checking accounts with same Eth addresses

  • KYC form.

The above tips is only a suggestion, perhaps there maybe a better ideas.

Time: Monthly

@Keaycee Keaycee added zz-Operations NEEDS SPONSOR guides: @TrenchFloat, @jimscarver @Tonyprisca13 Security labels Feb 23, 2018
@BelovedAquila
Copy link

BelovedAquila commented Feb 23, 2018

@Keaycee that's a nice suggestive tactics to check mate bad actors of multiple accounts and I think it would go a long way in achieving this #391 more effectively
I suggest the use of passport photographs to on vital membership forms, so as to always verify if the individual on the video verification is same individual on the form.

@dckc dckc added the needs-SMART-objective Specific; Measurable; Assignable; Realistic; Time-related label Feb 23, 2018
@dckc
Copy link
Contributor

dckc commented Feb 23, 2018

If you start doing this and have any experience to share, @Keaycee , please do.

It's interesting to think through these scenarios, but I doubt the suggested process is cost-effective. If you think through a budget for this, you may well agree.

I chatted with @kennyrowe about KYC and learned that the requirement is not 100% prevention of fraud, but just a reasonable due-diligence, sufficient to keep fraud from being cost effective.

I don't think it's important to prevent multiple github accounts for the same person. I do think it's important to prevent multiple coop memberships for the same person. I believe that's in the membership agreement, so the courts would back us if necessary. Meanwhile, discord OAuth seems a cost-effective solution (see #279, #260).

@BelovedAquila BelovedAquila changed the title O> checkmating multiple accounts on github O> Checkmating multiple accounts on Github Feb 24, 2018
@rchain rchain deleted a comment from YingsenP Feb 28, 2018
@rchain rchain deleted a comment from kaka56 Feb 28, 2018
@dckc
Copy link
Contributor

dckc commented Mar 2, 2018

With no movement toward a SMART objective in a week, I'm closing this.

@dckc dckc closed this as completed Mar 2, 2018
@dckc dckc added the wontfix label Mar 2, 2018
@Keaycee Keaycee changed the title O> Checkmating multiple accounts on Github O> Checkmating multiple accounts by coop members Mar 6, 2018
@Keaycee Keaycee reopened this Mar 6, 2018
@Keaycee Keaycee added Members Data and removed needs-SMART-objective Specific; Measurable; Assignable; Realistic; Time-related wontfix labels Mar 6, 2018
@Keaycee
Copy link
Contributor Author

Keaycee commented Mar 6, 2018

@dckc The objective of this thread is not preventing multi account on github, but preventing multi coop membership.

Why was the comments of @Biseny and @kaka56 deleted?? @dckc

@dckc
Copy link
Contributor

dckc commented Mar 6, 2018

I still see no movement toward a Measurable, Achievable, Realistic, Timely objective.

Again, feel free to re-open this issue if you have experience to share.

As I already explained, the comments were deleted because they were not relevant to this issue; they were discussion of getting access to the repo and the google drive folder.

@dckc dckc closed this as completed Mar 6, 2018
@Keaycee Keaycee reopened this Mar 6, 2018
@dckc dckc closed this as completed Mar 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Security zz-Operations NEEDS SPONSOR guides: @TrenchFloat, @jimscarver @Tonyprisca13
Projects
None yet
Development

No branches or pull requests

4 participants