Some feature adds to consider—some of this may already be in the protocol (my fault if I overlooked):
- Vote creation option: show/hide list of voters. All is on chain anyway, so there's no real anonymous voting but varying levels of access to the voting records could have QOL usecases.
- Search records: show a user’s voting history, vote creation history
- Schedule votes (allow for time delay before voting can occur, e.g. status: upcoming)
- Ad-hoc analyses (could be tricky / API heavy?) E.g. Show representation of community (x% of wallets w/ more than Y stake participated). Express vote results as if they were, say, Hive Power votes to compare your selected Layer2 token results to other weightings. All sorts of fun data things one could add on for fun haha.
Various kinds of analysis are definitely planned.
Showing and hiding things will definitely be possible. Those who want to can dive into more detail.
Hmm, haven't thought of this. How do you think it could be useful? Let's see if more people will be interested in something like it.
Possibly in a case where I want to work on building hype for a poll, but I don't want a trickle of early votes to sway anyone. Set a time and time limit to vote, so that it all happens within a controlled time frame.
I doubt this is a massive in-demand use case though—agree with gauging demand from people first :)