From 55c10e0081112bf22d5a4d2c34c75be4b911493b Mon Sep 17 00:00:00 2001 From: Sam Richards Date: Wed, 8 May 2024 19:52:34 -0300 Subject: [PATCH] docs: update gatekeeper summary [Fixes #1382] --- .../versioned_docs/version-v1.3_alpha/contracts/gatekeepers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/versioned_docs/version-v1.3_alpha/contracts/gatekeepers.md b/website/versioned_docs/version-v1.3_alpha/contracts/gatekeepers.md index 137386ab00..5d591d64d8 100644 --- a/website/versioned_docs/version-v1.3_alpha/contracts/gatekeepers.md +++ b/website/versioned_docs/version-v1.3_alpha/contracts/gatekeepers.md @@ -8,7 +8,7 @@ sidebar_label: Gatekeepers MACI is composed of multiple smart contracts, which together with the zk-SNARK circuits, can be used to carry out on-chain voting. Start with an [overview of our smart contracts here](/docs/contracts). -MACI uses a "gatekeeper" contract, which is used to configure and enforce the eligibility criteria of voters who can participate in MACI polls. It is up to MACI's deployer how they wish configure signup eligibility and to protect agaisnt sybil attacks. +MACI uses a "gatekeeper" contract, which is used to configure and enforce the eligibility criteria of voters who can participate in MACI polls. Operators of MACI can use the gatekeeper contract to configure signup eligibility and to protect agaisnt sybil attacks in their polls. The MACI repository comes with several out-of-the-box options: