From 4296f6732e09f4f56eeb0aa95ea04a6246998b12 Mon Sep 17 00:00:00 2001 From: linchizhen Date: Mon, 23 Dec 2024 20:25:42 +0800 Subject: [PATCH] chore: fix 404 status URL Signed-off-by: linchizhen --- apps/website/versioned_docs/version-v1.2/workflow.md | 2 +- .../versioned_docs/version-v2.x/core-concepts/workflow.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/apps/website/versioned_docs/version-v1.2/workflow.md b/apps/website/versioned_docs/version-v1.2/workflow.md index 50c583a46d..a3ea18cf4b 100644 --- a/apps/website/versioned_docs/version-v1.2/workflow.md +++ b/apps/website/versioned_docs/version-v1.2/workflow.md @@ -99,7 +99,7 @@ During this stage, users can sign up and vote. Before a user can cast a vote, they must sign up by generating a MACI keypair and then sending the public key they wish to use to cast their vote to the MACI smart contract. This MACI public key (distinct from their Ethereum account public key) acts as their identity when voting. Users can vote from any Ethereum address, but their message must contain a signature from that MACI public key. -This registration process is necessary to fortify MACI against Sybil attacks. The particular criteria used to allow user signups is customizable, and can be configured using any [SignUpGatekeeper contract](https://github.com/privacy-scaling-explorations/maci/blob/dev/contracts/contracts/gatekeepers/SignUpGatekeeper.sol). This contract dictates the criteria a user must pass in order to participate in a poll. For example, a user might need to prove ownership of a certain NFT, or that they've received some attestation on EAS, or prove that they have passed some sort of proof-of-personhood verification. Note that MACI presumes an identity system where each legitimate member +This registration process is necessary to fortify MACI against Sybil attacks. The particular criteria used to allow user signups is customizable, and can be configured using any [SignUpGatekeeper contract](https://github.com/privacy-scaling-explorations/maci/blob/dev/packages/contracts/contracts/gatekeepers/SignUpGatekeeper.sol). This contract dictates the criteria a user must pass in order to participate in a poll. For example, a user might need to prove ownership of a certain NFT, or that they've received some attestation on EAS, or prove that they have passed some sort of proof-of-personhood verification. Note that MACI presumes an identity system where each legitimate member controls a unique private key - MACI does not specifically solve for this, but allows for customization on how this is configured. #### Vote diff --git a/apps/website/versioned_docs/version-v2.x/core-concepts/workflow.md b/apps/website/versioned_docs/version-v2.x/core-concepts/workflow.md index c118452d23..7c87b919d2 100644 --- a/apps/website/versioned_docs/version-v2.x/core-concepts/workflow.md +++ b/apps/website/versioned_docs/version-v2.x/core-concepts/workflow.md @@ -99,7 +99,7 @@ During this stage, users can sign up and vote. Before a user can cast a vote, they must sign up by generating a MACI keypair and then sending the public key they wish to use to cast their vote to the MACI smart contract. This MACI public key (distinct from their Ethereum account public key) acts as their identity when voting. Users can vote from any Ethereum address, but their message must contain a signature from that MACI public key. -This registration process is necessary to fortify MACI against Sybil attacks. The particular criteria used to allow user signups is customizable, and can be configured using any [SignUpGatekeeper contract](https://github.com/privacy-scaling-explorations/maci/blob/dev/contracts/contracts/gatekeepers/SignUpGatekeeper.sol). This contract dictates the criteria a user must pass in order to participate in a poll. For example, a user might need to prove ownership of a certain NFT, or that they've received some attestation on EAS, or prove that they have passed some sort of proof-of-personhood verification. Note that MACI presumes an identity system where each legitimate member +This registration process is necessary to fortify MACI against Sybil attacks. The particular criteria used to allow user signups is customizable, and can be configured using any [SignUpGatekeeper contract](https://github.com/privacy-scaling-explorations/maci/blob/dev/packages/contracts/contracts/gatekeepers/SignUpGatekeeper.sol). This contract dictates the criteria a user must pass in order to participate in a poll. For example, a user might need to prove ownership of a certain NFT, or that they've received some attestation on EAS, or prove that they have passed some sort of proof-of-personhood verification. Note that MACI presumes an identity system where each legitimate member controls a unique private key - MACI does not specifically solve for this, but allows for customization on how this is configured. #### Vote