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

Potential poll exclusion via ( (poll length) >(cpid & stake).age ) #219

Closed
grctest opened this issue Mar 3, 2017 · 6 comments
Closed

Potential poll exclusion via ( (poll length) >(cpid & stake).age ) #219

grctest opened this issue Mar 3, 2017 · 6 comments

Comments

@grctest
Copy link
Contributor

grctest commented Mar 3, 2017

image

If you set a large poll duration, then more users will be unable to participate in the poll. We've been creating longer duration polls recently (2 1 year polls, several technical polls which last months).

On one hand, this prevents users who have been inactive (cold storage) from suddenly participating (somewhat encouraging these individuals to actively stake), on the other hand we exclude new users from polls with a large poll duration.

Perhaps this is causing low vote weight participation?

Thoughts?

@grctest grctest changed the title Potential poll exclusion via ( (poll length) >(cpid|stake).age ) Potential poll exclusion via ( (poll length) >(cpid & stake).age ) Mar 3, 2017
@startailcoon
Copy link

I have received this as well on the 1 year polls. Anyone joining in after a poll is created will be unable to join a poll. Maybe we should modify it so that anyone, even those joining in after the creation of the poll, can vote during the last days?

What is the meaning of this limitation?

@skcin
Copy link
Contributor

skcin commented Mar 8, 2017

The idea behind this might be that you cannot vote twice with your coins. This prevents you from voting, transfer your coins to a new address and vote again.

@grctest
Copy link
Contributor Author

grctest commented Mar 8, 2017

@skcin A better option for preventing double spending: #131 ?

@startailcoon
Copy link

Can't see the reason for this since you can vote and then move your coins to another address. What prevents me from doing that when I can vote later on, after I cast my vote?

@grctest
Copy link
Contributor Author

grctest commented Mar 19, 2017

A quick modification of the Gridcoin client code (and a self-compile) can result in this check being entirely eliminated, there are no checks performed against cast votes - it's all client side.

@jamescowens
Copy link
Member

Closed by #1809.

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

4 participants