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.

Sign up for GitHub

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

Update guardians page #1265

Merged
merged 3 commits into from
Jan 30, 2025
Merged

Update guardians page #1265

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e1a257f
Updated Guardinas page
TinaKT Jan 30, 2025
c5e84dc
Updated note and pre-setup section
TinaKT Jan 30, 2025
d824a89
Merge branch 'main' into Update-Guardians-page
TinaKT Jan 30, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions source/mainnet/docs/voting/guardians.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,18 +5,18 @@
Guardians
=========

The :term:`guardian` (via the guardian application) participates in all three phases of the election: the :term:`setup phase` before the election, they may cast votes during the :term:`election phase`, and the :term:`tally phase` at the end of the election.
The :term:`guardian` participates (via the guardian application) in all three phases of the election: the :term:`setup phase` before the election, the :term:`election phase` during which they may cast votes, and the :term:`tally phase` at the end of the election.

The setup phase ensures that the election tallying is decentralized. A number of guardians as defined by the election parameters in the smart contract register their public keys in the smart contract to say that they will :term:`tally` election votes. After the election closes, the guardians :term:`decrypt their share of the votes<decryption share>` and send the decrypted tally back to the smart contract. In this way, no one party tallies the votes for the election, ensuring privacy of the votes. Correctness of the result follows from the zero-knowledge proofs generated by the guardians to prove that they performed all steps correctly.
In the setup phase, a distributed encryption key is generated. This ensures the secrecy of ballots. A number of guardians, as defined by the election parameters in the smart contract, register their public keys in the smart contract to say that they will :term:`tally` election votes. After the election closes, the guardians :term:`decrypt their share of the votes<decryption share>` and send the decrypted tally back to the smart contract. In this way, no one party tallies the votes for the election, ensuring privacy of the votes. Correctness of the result follows from the zero-knowledge proofs generated by the guardians and voters to prove that they performed their parts correctly.

.. note::

Guardians cannot use the Desktop wallet or |mw-gen1| because these wallets cannot export account keys.
Guardians need to use the |bw| or the |cryptox| as these wallets have the ability to export account keys.

Pre-setup
=========

The guardians must give account addresses to the organizer of the election. If you need to know how to find your account address, see :ref:`share-address-mw`
The guardians must give their account addresses to the organizer of the election. If you need to know how to find your account address, see :ref:`share-address-mw`.

Guardians must download and install the Guardian desktop application that is created by the election coordinator.

Expand Down