I use vpGeek to track my votes. I noticed since last week it is showing that I haven’t voted at all when I’ve voted in every single ICP proposal. Found the voting history section in the NNS and it shows I’ve voted on the proposals that vpGeek says “not voted”. So it’s gotta be a vpGeek problem.
Anyone else having this problem?
vpGeek might have been using the public neuron ballots to display your neuron’s votes, and a recent proposal 130832 elected to make neurons private by default, so the ballots are no longer publicly visible.
Also see these threads:
https://forum.dfinity.org/t/request-for-comment-public-private-nns-neurons/31597?u=ori
and
https://forum.dfinity.org/t/request-for-comments-api-changes-for-public-private-neurons/33360?u=ori
Appreciate the explanation, Ori.
Just realized I missed voting on proposals that were set to “immediate majority decision”. The obvious reason for that is that these proposals were decided and executed within 1-2 minutes of their creation. There’s no way I would have time to vote on them.
Examples:
I hope dfinity does away with these types of proposals.
There is this perspective to explain why these types of proposals are needed…
I can agree with that just as long as there is a negligible impact on the staking rewards that I get for voting.
Take a look at the examples you provided and scroll down to the vote trend. Notice that the trend goes on for 4 days. This is because the voting period does not end just because the proposal was adopted and executed within 1-2 minutes. Everyone still gets to vote all the way to the end of the voting period, which is a minimum of 4 days.
In your case, I’m not sure who you follow, but most of the known neurons did vote. Hence it’s hard to explain why your neurons didn’t vote. However, it probably isn’t because the vote was executed in 1-2 minutes.
I checked the voting stats for known neurons on vpGeek. 38 out of 73 known neurons participated in the proposals that I brought up earlier. Technically that is more than half (~52%), which is a majority, but that’s by a tiny percentage. 47% (35 out of 73) of known neurons did not vote, including Dfinity. That’s a huge lack of participation, i.e. “not voting”.
Edit to add clarification… my stats from vpGeek was clarified by wpb and Dylan. Refer to their posts, here and here.
This is a bit frustrating to me because I worked hard to ensure that I participated in every vote.
I think the problem comes up because of my filter settings for voting. I had the “proposal status” to only show “open” proposals. But it seems that would leave out proposals that are “executed” but still open for voting. It’s just strange that those proposals also didn’t even show up under the “actionable proposals” section. So I’m thinking one way to fix that is to have my proposal status filter set to show “open” AND “executed” (or just show everything), which is going to be difficult because I’ll be seeing so many proposals.
Later on, I’m going to start another thread on this issue.
VPGeek lists both Known Neurons and what they call Public neurons. The Public neurons are mostly current or past voting members for Synapse and CodeGov. There are 42 Known Neurons that exist, which means there are 31 neurons that VPGeek is calling Public neurons. However, the private/public feature for neurons has been now been implemented and all neurons that are not Known Neurons are now private neurons by default. That means VPGeek cannot see how any of the formerly Public neurons voted. Hence, it looks like they didn’t vote until either VPGeek changes which neurons are listed or the neuron owners switch their neuron configuration from private to public (which just became available in the NNS dApp today).
If you go to the dashboard and look at a proposal, it will show only Known Neurons. The vast majority of them voted on the proposals that you provided as examples above.
There are 42 official known neurons, not 72.
In the link you posted, vpGeek is displaying neurons in the “Known Neuron Voting Participation (73)” section that aren’t known neurons. Since all such neurons recently became private by default, their voting history is no longer available, and presumably that’s why vpGeek has them listed as “Not Voted”. I’m sure vpGeek has plans to update their dapp to support private neurons properly.
The DFINITY known neuron (27) did vote.
Okay, @wpb types faster than me.
Thanks for the additional details and I’ll add a note to that post pointing to your posts.
But, still a problem here and not sure the best way to resolve.
Why wasn’t I able to see a proposal that was executed but still open for voting? I had my proposal status filter set to “open”. And those proposals i’m referring to didn’t even show up under “actionable proposals”. How can I view these types of proposals that are still open for voting? Hopefully an easier way to do that than just not having any filters.
Any proposal you can vote on should show up under Actionable Proposals, which doesn’t support any additional filtering. If there are proposals that a neuron can still vote on that aren’t in the list, that would be a bug.
All Proposals, on the other hand, does support filters. If you filter on only Open proposals, then it’s true that you won’t see non-Open proposals that you can still vote on.
Appreciate you explaining.
My 100% voter participation is gone now 
If it drops below 99.5%, I will seek therapy and send the bill to Dfinity 
Wait, are you judging you participation rate based on what VPGeek is telling you? VPGeek cannot see your votes since your neuron is now a private neuron. There is a high probability that you did actually vote. The fact that you don’t see those proposals in your Actionable Proposals list in the NNS dApp is further evidence that you actually voted.
If you want to use VPGeek to view your proposal voting history, then you can change your neuron to public in the NNS dApp. That functionality became available today. If you change it to public, then VPGeek will be able to see your votes again.