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

FEATURE: L1 votes fallback (with or without on-chain encryption) #492

Open
matiwinnetou opened this issue Oct 29, 2023 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@matiwinnetou
Copy link
Contributor

In voting systems with off-chain vote storage, where casting a vote is typically free, some users may still refrain from trusting such a system.

For such users can one can implement ability to cast votes way to a L1 (Cardano).

If event is configured not to reveal results while voting is taking place, cast votes can be encrypted on L1, e.g. private and public encryption keys would be generated when event is created by vote-admin-tool and public key attached to the event registered on chain. Once event finishes, a private key could be revealed. That in turn would allow for any external parties to tally the votes from L1 submitted transaction data.

There is a trade off for this design. An implementation would simply cast 1 vote = 1 encrypted L1 transaction, in this case it wouldn't be possible to know which proposal is leading in which category but it would be possible to know via writing an L1 indexer how many votes in total have been cast using L1. Such a limitation / design trade-off maybe ok for some voting events, perhaps not for others.

Suggestion: whether votes should be encrypted on L1 should depend on event's configuration related to leaderboard / results showing / on and off while voting.

@matiwinnetou matiwinnetou added the enhancement New feature or request label Oct 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant