Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Poll: Can projects with country or institutional based IP restrictions be whitelisted? #267

Open
Weber462 opened this issue Jun 10, 2024 · 7 comments

Comments

@Weber462
Copy link

Weber462 commented Jun 10, 2024

These could change at any time. I feel that the whitelist should be independent of the whims of Government and/or entities that are out of the control of the projects and the gridcoin community. The Gridcoin Whitelist Vote should be the final say.

@CyberTailor
Copy link

CyberTailor commented Jun 10, 2024

When project admins themselves block certain countries from participating for no justified reason, acting contrary to the spirit of openness and cooperation, such project should not be whitelisted.

However, this never happened as far as I know. All existing geo-restrictions are imposed by third parties and project admins can't do anything with it. So I'm voting Yes.

@PostApocalypse-Git
Copy link

I'm from Russia. It's easy to guess which vote I'll choose.

@rilian
Copy link

rilian commented Jun 10, 2024

as i understand if vote Yes, this means DENIS@home will be whitelisted. They have weird university network security

but if vote No, then by result of this poll SiDock must be blacklisted, cause it is banned for Ukrainian crunchers (as well as Rakesearch, Gerasim, SPT which are not whitelisted at this moment)

i'm voting Yes

@HeyMerlin
Copy link

What is the current policy of Gridcoin? In other words, currently is "IP restrictions" used in the determination as to whether a project is whitelisted or not?

@Weber462
Copy link
Author

What is the current policy of Gridcoin? In other words, currently is "IP restrictions" used in the determination as to whether a project is whitelisted or not?

Project Work Availability Score (WAS) is green
    Means that the seven day median new credit / the 40 day median credit is greater than 0.1
        Checks that there isn’t a low amount of credit recently given out compared to its past

Number of Zero Credit Days (ZCD) is less than or equal to 7 out of the last 20 days
    Means that there can’t be more than 7 days out of the last 20 that the project didn’t give out credits

The project has a clear description of the what it does and the project work is as described

The project allows new user registration

Project complies with the BOINC terms of service

**All crunchers that comply with the terms of service of both BOINC and the project have equal access to work units**

@Weber462
Copy link
Author

Weber462 commented Jun 10, 2024

as i understand if vote Yes, this means DENIS@home will be whitelisted. They have weird university network security

but if vote No, then by result of this poll SiDock must be blacklisted, cause it is banned for Ukrainian crunchers (as well as Rakesearch, Gerasim, SPT which are not whitelisted at this moment)

i'm voting Yes

I would think a yes would mean that both would be able to be whitelisted. I think the the final say should be the Vote. Its hard to rationalize not whitelisting a project because 0.001% of crunchers cannot access.

@Weber462
Copy link
Author

Weber462 commented Jun 10, 2024

I would argue that a good chuck crunchers have at least 1 project that they are not eligible to due to hardware/software limitations. Much more then location limitations.
I would like to omit or rephrase "project have equal access to work units" in whitelisting criteria. Again, making the vote the final say. If a project starts maliciously restricting IPs for any reason, they are always eligible to be voted off whitelist. Maybe a clearer path for "blacklisting" needs to be published.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants