Voting history: storage of votes from sns neurons, where did it go?

I’m gonna tag @cryptoschindler and @lara here.

At one time, ballots (cast votes) were stored for nns and sns proposals. This seems to be no more. Are votes stored and cached somewhere?

If not, can this be implemented? It seems integral to store the voting history of neurons.

1 Like

// Ballots are used to determine two things:
// 1. (obviously and primarily) whether to execute the proposal.
// 2. rewards
// At this point, we no longer need ballots for either of these
// things, and since they take up a fair amount of space, we take
// this opportunity to jettison them.
p.ballots.clear();

Can we start to store these again? This is imperative.

1 Like

It’s pretty crazy if this were to be true to remove votes from proposals and / or neurons.

I do understand that space will become an issue, but there are other ways to solve that.

Do hope this is incorrect @aterga

2 Likes

Both NNS and SNS neuron activity needs to stay private by default, otherwise devs/whales having controlling voting power could threaten to punish smaller neurons that don’t dance to their tune.

This doesn’t make any sense.

How can you weight voting history if there are no stored votes?

Your hypothetical is so far removed from how a “on chain governance model” should work.

Ideally, one would be able to check the index of who voted and with what vp for as long as possible.

I would even take an optional sns parameter to store such things. The cost is negligible.

1 Like

It’s quite simple, the final result of the vote including total number of Accept/Reject votes is stored but not individual ballots. That way, smaller neurons are protected from possible abuse as previously mentioned.

But the ballots are in the clear before they settle. They are not secret. They are just deleted.

Some DAOs will want votes to be public. Some will want votes to be private. All kinds of daos.

giphy

Strongly disagree, the moment a DAO chooses to make all ballots public it ceases to be a DAO since it only benefits whales. There’s a reason election voting is anonymous.

Again. It isn’t anonymous. You can call a function for a few hours right up until the maturity is calculated and get it free and clear. Say your philosophy is correct…we must not have any DAOs. There is nothing secret about them. The data just gets deleted. Someone can snap it and keep it public for ever.

1 Like

This is a blockchain.
Certain sns may have a usecase for storing voting history weighted for vp.

It’s is not an absurdity to require such data. I hope there’s a way for this to be implemented, considered it DID exist for some time, as we have around 126 proposals which DO store ballots and then around 120 which do not.

1 Like

Ooh now this is an idea, snapshot of votes before closing. This would take some engineering. It would have to what,

Read proposals
Capture the end date, and like. Take snapshots on a beat up until the vote ends.

I said election voting is anonymous, obviously the SNS/NNS system is currently not. My point remains, keeping voting history will only result in killing any existing semblance to a DAO from NNS/SNS.

So how exactly does being able to query voting history kill a doa?

Hi all,

please note the answer here that might already clarify a few points.

Note that:

  • In both the SNS and the NNS the idea was always that the ballots are removed from the proposal when they are not needed anymore to establish the proposal results and proposal settlement
  • In the NNS, ballots are additionally stored in the neuron (under recent_ballots), but this also only contains the last 100 ballots of a neuron and is regularly rewritten as the neuron votes on new things.
  • Proposals are garbage collected after there are 100 proposals from the same topic
  • So there was never a notion of keeping ballots / proposals forever.
  • In the SNS there was a bug that didn’t bring proposals without reward to the final state. Due to this, for a while in SNSs without rewards ballots were not removed. But this was rather an artifact to the proposal not being properly processed until the end state (which lead to other problems) than a design choice.
  • We have on the future roadmap to look into how the proposal history can be stored permanently, but this is further out.
3 Likes