@maci-protocol/website 0.0.0-ci.185b643

package/versioned_docs/version-v2.x/supported-networks/supported-networks.md

@@ -0,0 +1,47 @@
+---
+title: Supported Networks
+description: Supported Networks
+sidebar_label: Supported Networks
+sidebar_position: 1
+---
+
+MACI has been tested on the following EVM networks:
+
+- Optimism
+- Optimism Sepolia
+- Arbitrum
+- Arbitrum Sepolia
+- Base
+- Base Sepolia
+- Gnosis
+- Gnosis Chiado
+- Polygon
+- Polygon Amoy
+
+We recommend using either Optimism, Arbitrum or Base. Please open an issue/PR if you intend to use other EVM networks and would like to contribute to this record of deployed and verified contracts as well as benchmarks, that would be greatly appreciated.
+
+## Limitations
+
+For better UX, MACI clients should be sending votes (messages) in batches. Depending on the number of vote options available, larger batch might be sent. Below you can find the largest batch you can send for each network and how much gas it consumes:
+
+| Network          | Max Batch Size | Gas used | Price (based on Ether price at the time ~$2595) |
+| ---------------- | -------------- | -------- | ----------------------------------------------- |
+| Optimism         | 89             | 28167603 | 0.000036061732019822 ETH ($0.09)                |
+| Optimism Sepolia | 89             | 28163331 | 0.005651520470449442 ETH ($10.46)               |
+| Arbitrum         | 98             | 31017545 | 0.00031017545 ETH ($0.80)                       |
+| Arbitrum Sepolia | 98             | 31115404 | 0.0031115404 ETH ($8.06)                        |
+| Base             | 89             | 28165467 | 0.000591851649982612 ETH ($1.54)                |
+| Base Sepolia     | 89             | 28190232 | 0.002072926785842714 ETH ($5.18)                |
+| Gnosis           | 50             | 15921153 | 0.0000124615 ETH ($0.03)                        |
+| Gnosis Chiado    | 50             | 15921753 | 0.0000188313 ETH ($0.05)                        |
+| Polygon          | 85             | 26915773 | 0.0002193417259598 ETH ($0.54)                  |
+| Polygon Amoy     | 89             | 28192368 | 0.00017069180975304 ETH ($0.43)                 |
+
+## Test yourself
+
+To test MACI on a network, whether it's one of the ones listed above, or a new one, you can use the `benchmark` hardhat task:
+
+1. Ensure you have copied `.env.example` to `.env` and set the correct values for the network you want to test on.
+2. Configure your `deploy-config.json` - ensure `messageTreeDepth` is set to at least 3 (supporting 5 \*\* 3 votes)
+3. Ensure you have copied the `default-deployed-contracts.json` to `deployed-contracts.json` to avoid deploying unnecessary contracts again.
+4. Run the `benchmark` task: `pnpm benchmark:$NETWORK`

package/versioned_docs/version-v2.x/technical-references/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "Technical References",
+  "position": 5
+}

package/versioned_docs/version-v2.x/technical-references/smart-contracts/AccQueue.md

@@ -0,0 +1,21 @@
+---
+title: AccQueue Smart Contract
+description: AccQueue smart contract
+sidebar_label: AccQueue
+sidebar_position: 1
+---
+
+:::info
+Code location: [AccQueue.sol](https://github.com/privacy-scaling-explorations/maci/blob/dev/contracts/contracts/trees/AccQueue.sol)
+:::
+
+The AccQueue contract represents a Merkle Tree where each leaf insertion only updates a subtree. To obtain the main tree root, the subtrees must be merged together by the contract owner. This requires at least two operations, a `mergeSubRoots` and a `merge`.
+
+The contract can be initialized to work as a traditional Merkle Tree (2 leaves per node) or a Quinary Tree (5 leaves per node). This can be achieved by passing either two or five as parameter to the constructor (`_hashLength`). Any other values should not be accepted.
+
+Below are presented the most important functions of the smart contract:
+
+- `enqueue` - Allows to add a leaf to the queue for the current subtree. Only one parameter is accepted and that is the leaf to insert.
+- `insertSubTree` - Admin only function which allows to insert a full subtree (batch enqueue)
+- `mergeSubRoots` - Allows the contract owner to merge all of the subtrees to form the shortest possible tree. The argument `_numSrQueueOps` can be used to perform the operation in multiple transactions (as this might trigger the block gas limit).
+- `merge` - Allows the contract admin to form a main tree with the desired depth. The depth must fit all of the leaves.

package/versioned_docs/version-v2.x/technical-references/smart-contracts/Gatekeepers.md

@@ -0,0 +1,40 @@
+---
+title: Gatekeepers Smart Contract
+description: Gatekeepers smart contract
+sidebar_label: Gatekeepers
+sidebar_position: 6
+---
+
+:::info
+Code location: [Gatekeepers](https://github.com/privacy-scaling-explorations/maci/blob/v2.5.0/packages/contracts/contracts/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/technical-references/smart-contracts/MACI).
+
+MACI uses a "gatekeeper" contract, which is used to configure and enforce the eligibility criteria of voters who can participate in MACI polls. In other words, it is a way to whitelist signups to the system. Operators of MACI can use the gatekeeper contract to configure signup eligibility and to protect against sybil attacks in their polls.
+
+The MACI repository comes with several out-of-the-box options:
+
+- `FreeForAllGatekeeper` - This allows anyone to signup on MACI.
+- `SignUpTokenGatekeeper` - This restricts signups only to holders of a specific ERC721 token.
+- `EASGatekeeper` - This restricts signups only to users who have received an attestation of a specific schema from a trusted attester.
+- `HatsGatekeeper` - This allows gatekeeping signups to only users who have a specific [Hat](https://www.hatsprotocol.xyz/).
+- `GitcoinPassportGatekeeper` - This allows gatekeeping signups to only users who have a specific [Gitcoin Passport](https://passport.gitcoin.co/) score.
+- `ZupassGatekeeper` - This allows gatekeeping signups only to users who have a valid [Zupass PCD ticket](https://github.com/proofcarryingdata/zupass).
+- `SemaphoreGatekeeper` - This allows gatekeeping signups only to users who can prove they are part of a [Semaphore](https://semaphore.pse.dev/) group.
+
+You can find all of our latest gatekeeper contracts here:
+https://github.com/privacy-scaling-explorations/maci/blob/v2.5.0/packages/contracts/contracts/gatekeepers
+
+Developers are also welcome to implement a custom gatekeeper contract as long as it conforms to the `SignUpGatekeeper` - an abstract contract to inherit from with two function signatures:
+
+```ts
+abstract contract SignUpGatekeeper {
+    function setMaciInstance(MACI _maci) public virtual {}
+    function register(address _user, bytes memory _data) public virtual {}
+}
+```
+
+Whenever a user signs up (via the `MACI.signUp` function), this triggers the MACI contract to call the `SignUpGatekeeper.register` function. Please note that this function should throw if the user is not eligible to sign up, rather than returning true or false.
+
+If you'd like to create a gatekeeper contract for your project, or if there's specific gatekeeper functionality you'd like to see MACI support, we'd be happy to help! Please [create a GitHub issue](https://github.com/privacy-scaling-explorations/maci/issues/new/choose).

package/versioned_docs/version-v2.x/technical-references/smart-contracts/MACI.md

@@ -0,0 +1,152 @@
+---
+title: MACI Smart Contract
+description: MACI main smart contract
+sidebar_label: MACI
+sidebar_position: 1
+---
+
+:::info
+Code location: [MACI.sol](https://github.com/privacy-scaling-explorations/maci/blob/dev/contracts/contracts/MACI.sol)
+:::
+
+`MACI.sol` is the core contract of the project, as it provides the base layer for user signups and Polls to be created.
+
+The constructor shown below accepts several arguments:
+
+- `PollFactory` address
+- `MessageProcessorFactory` address
+- `TallyFactory` address
+- `SignUpGatekeeper` address
+- `InitialVoiceCreditProxy` address
+- The depth of the state tree
+
+```javascript
+constructor(
+    IPollFactory _pollFactory,
+    IMessageProcessorFactory _messageProcessorFactory,
+    ITallyFactory _tallyFactory,
+    SignUpGatekeeper _signUpGatekeeper,
+    InitialVoiceCreditProxy _initialVoiceCreditProxy,
+    uint8 _stateTreeDepth
+) payable {
+    // initialize and insert the blank leaf
+    InternalLazyIMT._init(lazyIMTData, _stateTreeDepth);
+    InternalLazyIMT._insert(lazyIMTData, BLANK_STATE_LEAF_HASH);
+
+    pollFactory = _pollFactory;
+    messageProcessorFactory = _messageProcessorFactory;
+    tallyFactory = _tallyFactory;
+    signUpGatekeeper = _signUpGatekeeper;
+    initialVoiceCreditProxy = _initialVoiceCreditProxy;
+    stateTreeDepth = _stateTreeDepth;
+
+    // Verify linked poseidon libraries
+    if (hash2([uint256(1), uint256(1)]) == 0) revert PoseidonHashLibrariesNotLinked();
+}
+
+```
+
+Upon deployment, the contract will initialize the state tree, and insert the blank leaf hash.
+
+After this, all of the parameters will be stored to state, and then the contract will perform a simple sanity check to ensure that the Poseidon hash libraries were linked successfully.
+
+## SignUp
+
+Next, we have the `signUp` function, which allows users to `signUp`, as long as they pass the conditions set in the `SignUpGatekeeper` contract. This contract can use any mean necessary to gatekeep access to MACI's polls. For instance, only wallets with a specific ERC721 token can be allowed to sign up.
+
+This function does the following:
+
+- checks that the maximum number of signups has not been reached. Given a tree depth of 10, this will be $2 ** 10 - 1$.
+- checks that the provided public key is a valid baby-jubjub point
+- registers the user using the sign up gatekeeper contract. It is important that whichever gatekeeper is used, this reverts if a user tries to sign up twice or the conditions are not met (i.e returning false is not enough)
+- calls the voice credit proxy to retrieve the number of allocated voice credits allocated to this voter
+- hashes the voice credits alongside the user's MACI public key and the current time
+- insert this hashed data into the state tree.
+
+```javascript
+function signUp(
+    PubKey memory _pubKey,
+    bytes memory _signUpGatekeeperData,
+    bytes memory _initialVoiceCreditProxyData
+) public virtual {
+    // ensure we do not have more signups than what the circuits support
+    if (lazyIMTData.numberOfLeaves >= maxSignups) revert TooManySignups();
+
+    // ensure that the public key is on the baby jubjub curve
+    if (!CurveBabyJubJub.isOnCurve(_pubKey.x, _pubKey.y)) {
+      revert InvalidPubKey();
+    }
+
+    // Register the user via the sign-up gatekeeper. This function should
+    // throw if the user has already registered or if ineligible to do so.
+    signUpGatekeeper.register(msg.sender, _signUpGatekeeperData);
+
+    // Get the user's voice credit balance.
+    uint256 voiceCreditBalance = initialVoiceCreditProxy.getVoiceCredits(msg.sender, _initialVoiceCreditProxyData);
+
+    uint256 timestamp = block.timestamp;
+
+    // Create a state leaf and insert it into the tree.
+    uint256 stateLeaf = hashStateLeaf(StateLeaf(_pubKey, voiceCreditBalance, timestamp));
+    InternalLazyIMT._insert(lazyIMTData, stateLeaf);
+
+    emit SignUp(lazyIMTData.numberOfLeaves - 1, _pubKey.x, _pubKey.y, voiceCreditBalance, timestamp);
+}
+```
+
+## DeployPoll
+
+Once everything has been setup, polls can be deployed using the `deployPoll` function. Polls can be deployed concurrently, as each deployment has its own separate set of contracts and state.
+
+```javascript
+function deployPoll(
+    uint256 _duration,
+    TreeDepths memory _treeDepths,
+    PubKey memory _coordinatorPubKey,
+    address _verifier,
+    address _vkRegistry,
+    Mode _mode
+  ) public virtual returns (PollContracts memory pollAddr) {
+    // cache the poll to a local variable so we can increment it
+    uint256 pollId = nextPollId;
+
+    // Increment the poll ID for the next poll
+    // 2 ** 256 polls available
+    unchecked {
+      nextPollId++;
+    }
+
+    // check coordinator key is a valid point on the curve
+    if (!CurveBabyJubJub.isOnCurve(_coordinatorPubKey.x, _coordinatorPubKey.y)) {
+      revert InvalidPubKey();
+    }
+
+    // the owner of the message processor and tally contract will be the msg.sender
+    address _msgSender = msg.sender;
+
+    address p = pollFactory.deploy(_duration, _treeDepths, _coordinatorPubKey, address(this));
+
+    address mp = messageProcessorFactory.deploy(_verifier, _vkRegistry, p, _msgSender, _mode);
+    address tally = tallyFactory.deploy(_verifier, _vkRegistry, p, mp, _msgSender, _mode);
+
+    polls[pollId] = p;
+
+    // store the addresses in a struct so they can be returned
+    pollAddr = PollContracts({ poll: p, messageProcessor: mp, tally: tally });
+
+    emit DeployPoll(pollId, _coordinatorPubKey.x, _coordinatorPubKey.y, pollAddr);
+  }
+```
+
+Polls require the following information:
+
+- `duration`: the duration of the poll
+- `treeDepths`: the depth of the state tree, message tree, and vote option tree
+- `coordinatorPubKey`: the public key of the poll's coordinator
+- `verifier`: the address of the zk-SNARK verifier contract
+- `vkRegistry`: the address of the vk registry contract
+- `mode`: the mode of the poll, to set whether it supports quadratic voting or non quadratic voting
+
+:::info
+Please be advised that the number of signups in the MACI contract (number of leaves in the merkle tree holding MACI's state) considers the initial zero leaf as one signup. For this reason, when accounting for the real users signed up to MACI, you should subtract one from the value returned from the `numSignUps` function.
+:::

package/versioned_docs/version-v2.x/technical-references/smart-contracts/MessageProcessor.md

@@ -0,0 +1,13 @@
+---
+title: MessageProcessor Smart Contract
+description: MessageProcessor smart contract
+sidebar_label: MessageProcessor
+sidebar_position: 4
+---
+
+:::info
+Code location: [MessageProcessor.sol](https://github.com/privacy-scaling-explorations/maci/blob/dev/contracts/contracts/MessageProcessor.sol)
+:::
+
+This contract is used to prepare parameters for the zk-SNARK circuits as well as for verifying proofs. It should be deployed alongside a `Poll` and ownership assigned to the coordinator.
+It will process messages in batches, and after all batches have been processed, the `sbCommitment` can then be used for the `Tally` contract verification steps.

package/versioned_docs/version-v2.x/technical-references/smart-contracts/Params.md

@@ -0,0 +1,32 @@
+---
+title: Params Smart Contract
+description: Params smart contract
+sidebar_label: Params
+sidebar_position: 9
+---
+
+:::info
+Code location: [Params.sol](https://github.com/privacy-scaling-explorations/maci/blob/dev/contracts/contracts/utils/Params.sol)
+:::
+
+A contract holding three structs:
+
+```c
+/// @notice A struct holding the depths of the merkle trees
+struct TreeDepths {
+  uint8 intStateTreeDepth;
+  uint8 messageTreeSubDepth;
+  uint8 messageTreeDepth;
+  uint8 voteOptionTreeDepth;
+}
+
+/// @notice A struct holding the external contracts
+/// that are to be passed to a Poll contract on
+/// deployment
+struct ExtContracts {
+  IMACI maci;
+  AccQueue messageAq;
+}
+```
+
+Struct parameters are used to avoid stack too deep errors in the other contracts.

package/versioned_docs/version-v2.x/technical-references/smart-contracts/Poll.md

@@ -0,0 +1,104 @@
+---
+title: Poll Smart Contract
+description: MACI Poll Contract
+sidebar_label: Poll
+sidebar_position: 2
+---
+
+:::info
+Code location: [Poll.sol](https://github.com/privacy-scaling-explorations/maci/blob/dev/contracts/contracts/Poll.sol)
+:::
+
+This contract allows users to submit their votes.
+
+The main functions of the contract are as follows:
+
+- `publishMessage` - This function allows anyone to publish a message, and it accepts the message object as well as an ephemeral public key. This key together with the coordinator public key will be used to generate a shared ECDH key that will encrypt the message.
+  Before saving the message, the function will check that the voting deadline has not passed, as well as the max number of messages was not reached.
+- `publisMessageBatch` - This function allows to submit a batch of messages, and it accepts an array of messages with their corresponding public keys used in the encryption step. It will call the `publishMessage` function for each message in the array.
+
+## PublishMessage
+
+The `publishMessage` function looks as follows:
+
+```js
+function publishMessage(Message memory _message, PubKey calldata _encPubKey) public virtual isWithinVotingDeadline {
+    // we check that we do not exceed the max number of messages
+    if (numMessages >= maxMessages) revert TooManyMessages();
+
+    // check if the public key is on the curve
+    if (!CurveBabyJubJub.isOnCurve(_encPubKey.x, _encPubKey.y)) {
+        revert InvalidPubKey();
+    }
+
+    // cannot realistically overflow
+    unchecked {
+        numMessages++;
+    }
+
+    uint256 messageLeaf = hashMessageAndEncPubKey(_message, _encPubKey);
+    extContracts.messageAq.enqueue(messageLeaf);
+
+    emit PublishMessage(_message, _encPubKey);
+}
+```
+
+## MergeMaciState
+
+After a Poll's voting period ends, the coordinator's job is to store the main state root, as well as some more information on the Poll contract using `mergeMaciState`:
+
+```js
+function mergeMaciState() public isAfterVotingDeadline {
+    // This function can only be called once per Poll after the voting
+    // deadline
+    if (stateMerged) revert StateAlreadyMerged();
+
+    // set merged to true so it cannot be called again
+    stateMerged = true;
+
+    mergedStateRoot = extContracts.maci.getStateTreeRoot();
+
+    // Set currentSbCommitment
+    uint256[3] memory sb;
+    sb[0] = mergedStateRoot;
+    sb[1] = emptyBallotRoots[treeDepths.voteOptionTreeDepth - 1];
+    sb[2] = uint256(0);
+
+    currentSbCommitment = hash3(sb);
+
+    // get number of signups and cache in a var for later use
+    uint256 _numSignups = extContracts.maci.numSignUps();
+    numSignups = _numSignups;
+
+    // dynamically determine the actual depth of the state tree
+    uint8 depth = 1;
+    while (uint40(1 << depth) < numberOfLeaves) {
+      depth++;
+    }
+
+    actualStateTreeDepth = depth;
+
+    emit MergeMaciState(mergedStateRoot, numSignups);
+  }
+```
+
+The function will store the state root from the MACI contract, create a commitment by hashing this merkle root, an empty ballot root stored in the `emptyBallotRoots` mapping, and a zero as salt. The commitment will be stored in the `currentSbCommitment` variable. Finally, it will store the total number of signups, and calculate the actual depth of the state tree. This information will be used when processing messages and tally to ensure proof validity.
+
+The `emptyBallotRoots` mapping is used to store the empty ballot roots for each vote option tree depth. For instance, if the vote option tree depth is 5, a build script will generate the following values (this assumes that the state tree depth is 10):
+
+```javascript
+emptyBallotRoots[0] = uint256(16015576667038038422103932363190100635991292382181099511410843174865570503661);
+emptyBallotRoots[1] = uint256(166510078825589460025300915201657086611944528317298994959376081297530246971);
+emptyBallotRoots[2] = uint256(10057734083972610459557695472359628128485394923403014377687504571662791937025);
+emptyBallotRoots[3] = uint256(4904828619307091008204672239231377290495002626534171783829482835985709082773);
+emptyBallotRoots[4] = uint256(18694062287284245784028624966421731916526814537891066525886866373016385890569);
+```
+
+At the same time, the coordinator can merge the message accumulator queue and generate its merkle root. This is achieved by calling the following functions:
+
+- `mergeMessageAqSubRoots` - merges the Poll's messages tree subroot
+- `mergeMessageAq` - merges the Poll's messages tree
+
+:::info
+Please be advised that the number of signups in this case includes the zero leaf. For this reason, when accounting for the real users signed up to the Poll, you should subtract one from the value stored in the Poll contract.
+:::

package/versioned_docs/version-v2.x/technical-references/smart-contracts/PollFactory.md

@@ -0,0 +1,43 @@
+---
+title: Poll Factory Smart Contract
+description: Poll Factory smart contract
+sidebar_label: PollFactory
+sidebar_position: 3
+---
+
+:::info
+Code location: [PollFactory.sol](https://github.com/privacy-scaling-explorations/maci/blob/dev/contracts/contracts/PollFactory.sol)
+:::
+
+`PollFactory` is a smart contract that is used to deploy new Polls. This is used by MACI inside the `deployPoll` function.
+
+```ts
+function deploy(
+    _duration,
+    TreeDepths calldata _treeDepths,
+    PubKey calldata _coordinatorPubKey,
+    address _maci
+) public virtual returns (address pollAddr) {
+    /// @notice deploy a new AccQueue contract to store messages
+    AccQueue messageAq = new AccQueueQuinaryMaci(_treeDepths.messageTreeSubDepth);
+
+    /// @notice the smart contracts that a Poll would interact with
+    ExtContracts memory extContracts = ExtContracts({ maci: IMACI(_maci), messageAq: messageAq });
+
+    // deploy the poll
+    Poll poll = new Poll(_duration, _treeDepths, _coordinatorPubKey, extContracts);
+
+    // Make the Poll contract own the messageAq contract, so only it can
+    // run enqueue/merge
+    messageAq.transferOwnership(address(poll));
+
+    // init Poll
+    poll.init();
+
+    pollAddr = address(poll);
+  }
+```
+
+Upon deployment, the following will happen:
+
+- ownership of the `messageAq` contract is transferred to the deployed poll contract

package/versioned_docs/version-v2.x/technical-references/smart-contracts/Tally.md

@@ -0,0 +1,45 @@
+---
+title: Tally Smart Contract
+description: Tally smart contract
+sidebar_label: Tally
+sidebar_position: 5
+---
+
+:::info
+Code location: [Tally.sol](https://github.com/privacy-scaling-explorations/maci/blob/dev/contracts/contracts/Tally.sol)
+:::
+
+The `Tally` contract is used by the coordinator to submit commitments to the tally results via the `tallyVotes` function. This is done in batches and the final commitment can be used by the users to verify the validity of the results.
+
+This contract should be deployed alongside a `Poll` and ownership assigned to the coordinator.
+
+The constructor accepts the following parameters:
+
+```ts
+  constructor(
+    address _verifier,
+    address _vkRegistry,
+    address _poll,
+    address _mp,
+    address _tallyOwner,
+    Mode _mode
+  ) payable Ownable(_tallyOwner) {
+    verifier = IVerifier(_verifier);
+    vkRegistry = IVkRegistry(_vkRegistry);
+    poll = IPoll(_poll);
+    messageProcessor = IMessageProcessor(_mp);
+    mode = _mode;
+  }
+```
+
+- `verifier` - The address of the verifier contract
+- `vkRegistry` - The address of the vkRegistry contract
+- `poll` - The address of the poll contract
+- `messageProcessor` - The address of the messageProcessor contract
+- `mode` - The mode of the tally contract - depending on this, the commitments will be processed differently, and it must equal the Poll mode (quadratic vs non quadratic voting)
+
+Users can use the verification functions to verify the Tally results. These are as follows:
+
+- `verifySpentVoiceCredits` - Verifies the spent voice credits
+- `verifyPerVOSpentVoiceCredits` - Verifies the spent voice credits per vote option
+- `verifyTallyResult` - Verifies the tally result

package/versioned_docs/version-v2.x/technical-references/smart-contracts/VkRegistry.md

@@ -0,0 +1,57 @@
+---
+title: VkRegistry Smart Contract
+description: VkRegistry smart contract
+sidebar_label: VkRegistry
+sidebar_position: 8
+---
+
+:::info
+Code location: [VkRegistry.sol](https://github.com/privacy-scaling-explorations/maci/blob/dev/contracts/contracts/VkRegistry.sol)
+:::
+
+The VkRegistry is a contract that holds the verifying keys for the zk-SNARK circuits. It holds two different sets of keys:
+
+- `processVks` - The keys for the processMessages circuit
+- `tallyVks` - The keys for the tallyVotes circuit
+
+Each circuit will have a signature which is its compile-time constants represented as a uint256.
+
+Please note that each Verifying Key should be set with the corresponding mode. Available modes are quadratic voting and non quadratic voting.
+
+The contract owner can set them using the `setVerifyingKeysBatch` function:
+
+```ts
+  function setVerifyingKeysBatch(
+    uint256 _stateTreeDepth,
+    uint256 _intStateTreeDepth,
+    uint256 _messageTreeDepth,
+    uint256 _voteOptionTreeDepth,
+    uint256 _messageBatchSize,
+    Mode[] calldata _modes,
+    VerifyingKey[] calldata _processVks,
+    VerifyingKey[] calldata _tallyVks
+  ) public onlyOwner {
+    if (_modes.length != _processVks.length || _modes.length != _tallyVks.length) {
+      revert InvalidKeysParams();
+    }
+
+    uint256 length = _modes.length;
+
+    for (uint256 index = 0; index < length; ) {
+      setVerifyingKeys(
+        _stateTreeDepth,
+        _intStateTreeDepth,
+        _messageTreeDepth,
+        _voteOptionTreeDepth,
+        _messageBatchSize,
+        _modes[index],
+        _processVks[index],
+        _tallyVks[index]
+      );
+
+      unchecked {
+        index++;
+      }
+    }
+  }
+```

package/versioned_docs/version-v2.x/technical-references/smart-contracts/VoiceCreditProxy.md

@@ -0,0 +1,18 @@
+---
+title: Voice Credits Proxy Smart Contract
+description: Voice Credits Proxy smart contract
+sidebar_label: VoiceCreditsProxy
+sidebar_position: 7
+---
+
+:::info
+Code location: [InitialVoiceCreditProxy](https://github.com/privacy-scaling-explorations/maci/tree/dev/contracts/contracts/initialVoiceCreditProxy)
+:::
+
+The VoiceCreditProxy contract is used to assign voice credits to users. Whichever implementation should the MACI deployers use, this must implement a view function that returns the balance for a user, such as the one below:
+
+```javascript
+function getVoiceCredits(address _user, bytes memory _data) public virtual view returns (uint256) {}
+```
+
+The repository comes with a simple implementation called `ConstantInitialVoiceCreditProxy` which assigns a fixed amount of voice credits to each user.

package/versioned_docs/version-v2.x/technical-references/smart-contracts/_category_.json

@@ -0,0 +1,8 @@
+{
+  "label": "Smart Contracts",
+  "position": 1,
+  "link": {
+    "type": "generated-index",
+    "description": "MACI is composed of multiple smart contracts, which together with the zk-SNARK circuits, can be used to carry out on-chain voting. The main contracts are presented and explained below. Please also find autogenerated solidity documentation with solidity-docs."
+  }
+}

package/versioned_docs/version-v2.x/technical-references/technical-references.md

@@ -0,0 +1,47 @@
+---
+title: MACI Codebase
+description: High-level overview of the MACI codebase
+sidebar_label: Technical References
+sidebar_position: 1
+---
+
+# MACI Overview
+
+The MACI codebase consists of three subsystems in different programming languages:
+
+1. Solidity smart contracts
+2. TypeScript libraries
+3. Circom circuits
+
+## Smart contracts
+
+The MACI smart contracts handle the on-chain aspects - both the functionality and the storage - of the voting system. They provide the functionality to deploy polls, register voters, and accept votes. They also store and manage the on-chain data from transactions, such as the encrypted votes of a poll. Finally, they verify proofs of the zk-SNARK circuits, so that everyone can validate the voting results.
+
+The MACI smart contracts are written in [Solidity](https://soliditylang.org/).
+
+Contracts are released through the [`@maci-contracts`](https://www.npmjs.com/package/maci-contracts) NPM package.
+
+[Learn more about MACI contracts](/docs/category/smart-contracts)
+
+## TypeScript libraries
+
+The TypeScript libraries manage the business logic between the smart contracts and the circuit code. They provide a variety of functionality, such as encryption tools, utilities, and a CLI for interacting with MACI (for actions like signing up, voting, tallying votes & generating proofs).
+
+The MACI [TypeScript](https://www.typescriptlang.org/) libraries are released through the following NPM packages:
+
+- [`@maci-cli`](https://www.npmjs.com/package/maci-cli)
+- [`@maci-core`](https://www.npmjs.com/package/maci-core)
+- [`@maci-crypto`](https://www.npmjs.com/package/maci-crypto)
+- [`@maci-domainobjs`](https://www.npmjs.com/package/maci-domainobjs)
+- [`@maci-integrationtests`](https://www.npmjs.com/package/maci-integrationtests)
+
+## Circuits
+
+MACI has multiple circuits that ensure all off-chain computation is completed correctly. The circuits are used to generate zero-knowledge proofs (zk-SNARKs) that the votes were counted correctly. Specifically, they enforce that message processing and vote tallying were correctly executed by the coordinator. The proofs can then be verified through a verifier smart contract on-chain.
+
+The circuits for these zero-knowledge proofs are written
+in [Circom](https://iden3.io/circom).
+
+The MACI circuits are released through the [`@maci-circuits`](https://www.npmjs.com/package/maci-circuits) NPM package.
+
+[Learn more about MACI circuits](/docs/technical-references/zk-snark-circuits/introduction)

package/versioned_docs/version-v2.x/technical-references/typescript-code/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "Typescript Code",
+  "position": 2
+}