@maci-protocol/website 0.0.0-ci.26f28d6

package/versioned_docs/version-v3.x/contributing/code-of-conduct.md

@@ -0,0 +1,92 @@
+---
+title: MACI Contributor Code of Conduct
+description: The Contributor Covenant Code of Conduct for MACI
+sidebar_label: Code of Conduct
+sidebar_position: 2
+---
+
+# Contributor Covenant Code of Conduct
+
+Please see our guide on [contributing to MACI](/docs/contributing).
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 2.0, [available here](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html).
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+For answers to common questions about this code of conduct, see [the FAQ](https://www.contributor-covenant.org/faq). [Translations are available here](https://www.contributor-covenant.org/translations).

package/versioned_docs/version-v3.x/contributing/contributing.md

@@ -0,0 +1,149 @@
+---
+title: Contributing to MACI
+description: Instructions on how to contribute to MACI
+sidebar_label: Contributing
+sidebar_position: 1
+---
+
+# Contributing
+
+🎉 Thank you for being interested in contributing to MACI! 🎉
+
+Feel welcome and read the following sections in order to know how to ask questions and how to work on something.
+
+All members of our community are expected to follow our [Code of Conduct](/docs/contributing/code-of-conduct). Please make sure you are welcoming and friendly in all of our spaces.
+
+We're really glad you're reading this, because we need volunteer developers to help this project come to fruition. There is a lot we want to achieve, and this can only be made possible thanks to your support. 👏
+
+**Disclaimer**: We do not accept minor grammatical fixes (e.g., correcting typos, rewording sentences) unless they significantly improve clarity in technical documentation. These contributions, while appreciated, are not a priority for merging. If there is a grammatical error feel free to message the team [here](https://discord.gg/akDcCB69).
+
+## How You Can Contribute
+
+1. **Report Bugs**: Identify and describe issues.
+2. **Suggest Features**: Share your ideas for improvements.
+3. **Code Contributions**: Fix bugs, add features, or refactor existing code.
+4. **Improve Documentation**: Help us keep the docs clear and up to date.
+5. **Engage with the Community**: Help answer questions or participate in discussions.
+
+## Issues
+
+The best way to contribute to our projects is by opening a [new issue](https://github.com/privacy-scaling-explorations/maci/issues) or tackling one of the issues listed [here](https://github.com/privacy-scaling-explorations/maci/contribute).
+
+Before submitting an issue:
+
+- Search existing issues to avoid duplicates
+- Check documentation/FAQ
+- Test with the latest version
+
+:::info
+If you pick up an issue and are assigned to it by the maintaining team, please be advised that from time to time the team will reach out to check on the progress of the work. If you are working on the issue you are assigned but need more time or help, please let us know and we will be happy to assist you. We understand that contributors have other commitments too, and we appreciate every contribution, no matter the pace. If you fail to respond after 2 weeks, we will gently remind you to provide an update. If there is still no activity after that, we may reassign the issue to ensure project momentum, but we also welcome you to reengage with the project at any time when you are more available.
+:::
+
+## Pull Requests
+
+Pull requests are great if you want to add a feature or fix a bug. Here's a quick guide:
+
+1. Ensure there is an issue tracking your work.
+
+2. Fork the repo.
+
+3. Run the tests. We only take pull requests with passing tests.
+
+4. Add a test for your change. Only refactoring and documentation changes require no new tests.
+
+5. Make sure to check out the [Style Guide](#style-guide) and ensure that your code complies with the rules.
+
+6. Make sure you read our [GitHub processes](https://github.com/privacy-scaling-explorations/maci/discussions/847) documentation.
+
+7. Make the test pass.
+
+8. Commit your changes. Please make sure your forked `dev` branch is synced as well feature/fix branch and there are no "temp" commits (like wip, fix typo/lint/types and etc). We recommend to squash the feature/fix branch commits before creating PR. You can use this command for it:
+
+```bash
+git reset $(git merge-base dev $(git rev-parse --abbrev-ref HEAD))
+```
+
+9. Push to your fork and submit a pull request on our `dev` branch. Please provide us with some explanation of why you made the changes you made. For new features make sure to explain a standard use case to us.
+
+10. Link any issues that the PR is addressing as described in our processes documentation.
+
+## CI (Github Actions) Tests
+
+We use GitHub Actions to test each PR before it is merged.
+
+When you submit your PR (or later change that code), a CI build will automatically be kicked off. A note will be added to the PR, and will indicate the current status of the build.
+
+Please refer to our [testing guide](/docs/guides/testing/testing-introduction) for more details on how we run tests across the monorepo.
+
+## Style Guide
+
+### Code rules
+
+We always use ESLint and Prettier. To check that your code follows the rules, simply run the pnpm script `pnpm run lint` and `pnpm run prettier`. When committing, `eslint` is run automatically, so you will be required to fix any error before being able to push a commit. We highly recommend to tackle warnings as well.
+
+### Commits rules
+
+For commits it is recommended to use [Conventional Commits](https://www.conventionalcommits.org). You may install the [commitizen](https://commitizen-tools.github.io/commitizen/) tool to help you with this.
+
+Each commit message consists of a **header**, a **body** and a **footer**. The **header** has a special format that includes a **type**, a **scope** and a **subject**:
+
+```
+    <type>(<scope>): <subject>
+    <BLANK LINE>
+    <body>
+    <BLANK LINE>
+    <footer>
+```
+
+The **header** is mandatory and the **scope** of the header must contain the name of the component you are working on.
+
+#### Type
+
+The type must be one of the following:
+
+- feat: A new feature
+- fix: A bug fix
+- docs: Documentation only changes
+- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
+- refactor: A code change that neither fixes a bug nor adds a feature (improvements of the code structure)
+- perf: A code change that improves the performance
+- test: Adding missing or correcting existing tests
+- build: Changes that affect the build system or external dependencies (example scopes: gulp, npm)
+- ci: Changes to CI configuration files and scripts (example scopes: travis, circle)
+- chore: Other changes that don't modify src or test files
+- revert: Reverts a previous commit
+
+#### Scope
+
+The scope should be the name of the feature or package modified (as perceived by the person reading the changelog generated from commit messages).
+
+#### Subject
+
+The subject contains a succinct description of the change:
+
+- Use the imperative, present tense: "change" not "changed" nor "changes"
+- Don't capitalize the first letter
+- No dot (.) at the end
+
+#### Body
+
+Just as in the subject, use the imperative, present tense: "change" not "changed" nor "changes". The body should include the motivation for the change and contrast this with previous behavior.
+
+### Branch rules
+
+- Branches should generally be created off of the base branch (`dev` )
+- Avoid long descriptive names for long-lived branches
+- Use kebab-case (no CamelCase)
+- Use grouping tokens (words) at the beginning of your branch names (in a similar way to the `type` of commit)
+- Define and use short lead tokens to differentiate branches in a way that is meaningful to your workflow
+- Use slashes to separate parts of your branch names
+- Remove branch after merge if it is not important
+
+Examples:
+
+```bash
+git branch -b docs/readme
+git branch -b test/a-feature
+git branch -b feat/sidebar
+git branch -b fix/b-feature
+```

package/versioned_docs/version-v3.x/contributing/project-ideas.md

@@ -0,0 +1,78 @@
+---
+title: MACI Project Ideas
+description: Community-sourced ideas of projects you could build with MACI
+sidebar_label: MACI Project ideas
+sidebar_position: 3
+---
+
+# Project Ideas
+
+### 1. Decentralized Governance Platform
+
+**Idea:** Create a decentralized governance platform for DAOs (Decentralized Autonomous Organizations) using the Scaffold ETH 2 + MACI Voting Template. Enable DAO members to propose and vote on governance decisions securely and anonymously.
+
+**Features:**
+
+- Proposal creation and submission
+- Secure, anonymous voting using MACI
+- Transparent results display
+- Integration with existing DAO frameworks
+
+### 2. Secure Polling System for Communities
+
+**Idea:** Develop a secure and private polling system for online communities, such as social media groups, forums, or local organizations. This system can be used for decision-making, surveys, or feedback collection.
+
+**Features:**
+
+- User-friendly poll creation and management interface
+- Anonymized vote submission
+- Real-time poll results visualization
+- Admin dashboard for poll oversight
+
+### 3. Private Election System for Institutions
+
+**Idea:** Build a private and secure election system for educational institutions, corporate boards, or non-profits. Ensure that election processes are transparent, fair, and resistant to manipulation.
+
+**Features:**
+
+- Secure voter registration process
+- Anonymous and tamper-proof voting
+- Detailed results analytics
+- Audit logs and election certification
+
+### 4. Anonymous Feedback System
+
+**Idea:** Implement an anonymous feedback system for companies or organizations to collect honest feedback from employees or customers. Guarantee the privacy of the respondents to encourage open and honest communication.
+
+**Features:**
+
+- Anonymous feedback submission
+- Secure handling of sensitive information
+- Aggregated feedback reports
+- Admin tools for feedback analysis
+
+### 5. Decentralized Survey Platform
+
+**Idea:** Create a decentralized survey platform for academic research or market analysis. Utilize MACI's privacy features to ensure respondent confidentiality and data integrity.
+
+**Features:**
+
+- Customizable survey creation
+- Anonymized responses
+- Secure data storage and processing
+- Results aggregation and visualization
+
+### 6. Blockchain-based Voting for Public Elections
+
+**Idea:** Develop a blockchain-based voting system for municipal or state-level public elections. Focus on enhancing transparency, security, and voter anonymity.
+
+**Features:**
+
+- Robust voter registration and verification
+- Anonymous vote casting and tallying
+- Transparent and verifiable election results
+- Compliance with electoral regulations
+
+## Join the conversation
+
+The MACI core team maintains a wishlist of community-sourced ideas to build with/for/on MACI. Check out our ["Project ideas to build with MACI" GitHub Discussion](https://github.com/privacy-scaling-explorations/maci/discussions/1136) for the up-to-date list! We encourage you to find inspiration here and comment in the discussion to suggest ideas of your own.

package/versioned_docs/version-v3.x/core-concepts/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "Core Concepts",
+  "position": 5
+}

package/versioned_docs/version-v3.x/core-concepts/ballot.md

@@ -0,0 +1,19 @@
+---
+title: Ballot
+description: A short introduction of the main primitives used by MACI
+sidebar_label: Ballot
+sidebar_position: 4
+---
+
+A Ballot represents a particular user's votes in a poll, as well as their next valid nonce. It is akin to a voting slip, which belongs to only one voter and contains a list of their choices.
+
+| Symbol    | Name                       | Comments                                                                   |
+| --------- | -------------------------- | -------------------------------------------------------------------------- |
+| $blt_{v}$ | An array of vote weights   | $blt_{v[i]}$ refers to the vote weights assigned to vote option $i$        |
+| $blt_n$   | The current nonce          | Starts from 0 and increments, so the first valid command must have nonce 1 |
+| $blt_d$   | The vote option tree depth | The depth of the vote option tree                                          |
+
+The hash $blt$ is computed as such:
+
+1. Compute the Merkle root of $blt_v$, arity 5, of a tree of depth $blt_d$; let this value be $blt_r$
+2. Compute $poseidon_2([blt_n, blt_r])$

package/versioned_docs/version-v3.x/core-concepts/coordinator-processing.md

@@ -0,0 +1,46 @@
+---
+title: Coordinator local processing
+description: How does the coordinator process and tally messages locally
+sidebar_label: Coordinator local processing
+sidebar_position: 7
+---
+
+# Coordinator local processing
+
+The coordinator is responsible for processing and tallying messages locally, before generating proofs that this was done correctly using the zk-SNARK circuits.
+
+To summarize, the coordinator's goal here is to process all of the messages that were submitted by MACI's voters, then tally the votes based on the valid vote messages. Furthermore, each batch processed should be able to be verified by a zk-SNARK proof.
+
+## Which MACI's components are involved
+
+The following diagram, shows which components are involved and at which step of the way
+
+![components involved](/img/coordinatorComponents.svg)
+
+## What does the process look like?
+
+![processing](/img/offlineProcessing.svg)
+
+Zooming in.
+
+**Message processing**
+
+![message processing](/img/messageProcessingLocal.svg)
+
+**Vote tallying**
+
+![vote tallying](/img/voteTallyingLocal.svg)
+
+## What does the process look like when including the zk-SNARK proofs
+
+**Process of completing a Poll**
+
+![processing with proofs](/img/completingAPoll.svg)
+
+**Process of generating proofs**
+
+![generating proofs](/img/generateProofs.svg)
+
+**Tally commitments**
+
+![tally commitments](/img/tallyCommitments.svg)

package/versioned_docs/version-v3.x/core-concepts/hashing-and-encryption.md

@@ -0,0 +1,45 @@
+---
+title: Hashing and Encryption
+description: A short introduction of the main primitives used by MACI
+sidebar_label: Hashing and Encryption
+sidebar_position: 3
+---
+
+### Hash Functions
+
+MACI uses the Poseidon hash function, which is proven to be very efficient in ZK applications. Poseidon accepts $n$ inputs and produces 1 output:
+
+$y = poseidon_n([x_1, x_2, ..., x_n])$
+
+Also, SHA256 is used to compress public inputs to a circuit into a single field element in the finite field $F$ mod $p$.
+
+### Message Encryption
+
+In order to encrypt messages, MACI uses Poseidon in DuplexSponge [mode](https://dusk.network/uploads/Encryption-with-Poseidon.pdf). This provides an encryption function and a decryption function:
+
+- $C$ as $poseidonEncrypt(k_s[0], k_s[1], N, l, t[])$
+- $poseidonDecrypt(k_s[0], k_s[1], N, l, C)$
+
+In more details,
+
+- $k_s$ is the shared key, a point on the Baby Jubjub curve
+- $N$ is the nonce, which we hardcode to 0
+- $l$ is the length of the plaintext $t[]$
+
+The implementation can be found [here](https://github.com/privacy-scaling-explorations/zk-kit/tree/main/packages/poseidon-cipher).
+
+### Shared Key Generation
+
+The ECDH algorithm is used to generate a shared key, which is then used to encrypt each message. This allows to create messages which are only decryptable by the coordinator and the person sending the message.
+
+In more details:
+
+- The coordinator's public key $cPk$ is known to all. Their private key $cSk$ is secret.
+
+- When the user publishes a message (i.e. casts a vote), they generate an ephemeral keypair with private key $eSk$ and public key $ePk$.
+
+- The user generates the shared key $k$ using the coordinator's public key $cPk$ and the user's ephemeral private key $eSk$.
+
+- The user encrypts the command and signature with $k$ to form a message.
+
+- The user sends their ephemeral public key $ePk$ along with the ciphertext. The coordinator can recover the same shared key using their private key $cSk$ and the given ephemeral public key $ePk$.

package/versioned_docs/version-v3.x/core-concepts/key-change.md

@@ -0,0 +1,179 @@
+---
+title: Key change
+description: How key change messages work
+sidebar_label: Key change
+sidebar_position: 8
+---
+
+MACI's voters are identified by their MACI public key. Together with their private key, they can sign and submit messages to live Polls.
+
+As MACI's main property is to provide collusion resistance in digital voting applications, it is important to have a mechanism for a user to change their voting key, should this become compromised, or they wish to revoke past actions.
+
+## How MACI messages are processed
+
+In order to understand how key changing currently works in MACI, we need to understand how messages are processed.
+
+After a poll ends, the coordinator processes messages off chain in reverse order. To improve efficiency, messages are processed in batches, and correctness is proved for each batch using a zk-SNARK circuit.
+
+Due to messages being processed in reverse order, key change messages would work a bit differently than if they were processed in the same order as they were submitted.
+
+## Why are messages processed in reverse order?
+
+Reverse processing was introduced to prevent a type of attack where a briber would collude with a voter to sign up, and then submit a message to change their key to a key that the briber controls. This way the briber would have assurance that they could submit the vote they want.
+
+Let's take as an example the following:
+
+1. Alice signs up with pub key $pub1$
+2. Bob (Briber) bribes Alice and asks her to submit a key change message to $pub2$ (owned by Bob)
+3. Bob submits a vote with $pub2$
+4. Alice submits a vote with $pub1$
+
+If messages were processed in the same order as they were submitted, Alice's vote would not be valid, due to it being signed with a private key $priv1$ - which now would not be valid.
+
+On the other hand, due to messages being processed in reverse order, Alice's last message would be counted as valid as the key change would have not been processed yet. Then, Bob's vote would not be counted as valid as the current key for Alice would be $pub1$.
+
+> Note that a key change message should have the nonce set to 1 in order for it to be valid. We'll see a code example in the next sections.
+
+## Then how can a voter change their key and submit a new vote?
+
+A user, can submit a key change message, by simply sending a new message signed with their signup key, and setting the nonce to 1. This is because the code checks that the first message to be processed has the nonce set to 1.
+
+Let's take a look into a code example:
+
+> We have two users, and three keypairs
+
+- Create three keypairs
+
+```ts
+const user1Keypair = new Keypair();
+const user2Keypair = new Keypair();
+const secondKeyPair = new Keypair();
+```
+
+- Votes will be
+
+```ts
+// user1 votes for project 0
+const user1VoteOptionIndex = BigInt(0);
+// user2 votes for project 1
+const user2VoteOptionIndex = BigInt(1);
+// user1 votes 9 for the first vote
+const user1VoteWeight = BigInt(9);
+// user2 votes 3
+const user2VoteWeight = BigInt(3);
+// user1 will change their vote to 5
+const user1NewVoteWeight = BigInt(5);
+```
+
+- What do we expect as result
+
+```
+project 0 = 5 * 5 -> 25
+project 1 = 3 * 3 -> 9
+```
+
+As seen above, we expect the first vote weight 9 to not be counted, but instead the second vote weight 5 to be counted.
+
+- Deploy a MaciState locally and sign up
+
+```ts
+const maciState: MaciState = new MaciState(STATE_TREE_DEPTH);
+// Sign up
+user1StateIndex = maciState.signUp(user1Keypair.pubKey, voiceCreditBalance, BigInt(Math.floor(Date.now() / 1000)));
+user2StateIndex = maciState.signUp(user2Keypair.pubKey, voiceCreditBalance, BigInt(Math.floor(Date.now() / 1000)));
+// deploy a poll
+pollId = maciState.deployPoll(
+  duration,
+  BigInt(Math.floor(Date.now() / 1000) + duration),
+  treeDepths,
+  messageBatchSize,
+  coordinatorKeypair,
+);
+```
+
+- User1 and user2 submit their first votes
+
+```ts
+const poll = maciState.polls[pollId];
+const command1 = new PCommand(
+  BigInt(user1StateIndex),
+  user1Keypair.pubKey,
+  user1VoteOptionIndex,
+  user1VoteWeight,
+  BigInt(1),
+  BigInt(pollId),
+);
+
+const signature1 = command1.sign(user1Keypair.privKey);
+
+const ecdhKeypair1 = new Keypair();
+const sharedKey1 = Keypair.genEcdhSharedKey(ecdhKeypair1.privKey, coordinatorKeypair.pubKey);
+
+const message1 = command1.encrypt(signature1, sharedKey1);
+poll.publishMessage(message1, ecdhKeypair1.pubKey);
+
+const command2 = new PCommand(
+  BigInt(user2StateIndex),
+  user2Keypair.pubKey,
+  user2VoteOptionIndex,
+  user2VoteWeight,
+  BigInt(1),
+  BigInt(pollId),
+);
+
+const signature2 = command2.sign(user2Keypair.privKey);
+
+const ecdhKeypair2 = new Keypair();
+const sharedKey2 = Keypair.genEcdhSharedKey(ecdhKeypair2.privKey, coordinatorKeypair.pubKey);
+
+const message2 = command2.encrypt(signature2, sharedKey2);
+poll.publishMessage(message2, ecdhKeypair2.pubKey);
+```
+
+- User1 submits a key change message with the new vote
+
+```ts
+const poll = maciState.polls[pollId];
+const command = new PCommand(
+  BigInt(user1StateIndex),
+  secondKeyPair.pubKey,
+  user1VoteOptionIndex,
+  user1NewVoteWeight,
+  BigInt(1),
+  BigInt(pollId),
+);
+
+const signature = command.sign(user1Keypair.privKey);
+
+const ecdhKeypair = new Keypair();
+const sharedKey = Keypair.genEcdhSharedKey(ecdhKeypair.privKey, coordinatorKeypair.pubKey);
+
+const message = command.encrypt(signature, sharedKey);
+poll.publishMessage(message, ecdhKeypair.pubKey);
+```
+
+- We process the votes and check that the result is as expected (`user1NewVoteWeight` was 5 and `user2VoteWeight` 3)
+
+```ts
+const poll = maciState.polls[pollId];
+poll.processMessages(pollId);
+poll.tallyVotes();
+expect(poll.perVOSpentVoiceCredits[0].toString()).to.eq((user1NewVoteWeight * user1NewVoteWeight).toString());
+expect(poll.perVOSpentVoiceCredits[1].toString()).to.eq((user2VoteWeight * user2VoteWeight).toString());
+```
+
+- Finally confirm that the keypair was changed for the user1
+
+```ts
+const poll = maciState.polls[pollId];
+const stateLeaf1 = poll.stateLeaves[user1StateIndex];
+const stateLeaf2 = poll.stateLeaves[user2StateIndex];
+expect(stateLeaf1.pubKey.equals(user1SecondKeypair.pubKey)).to.eq(true);
+expect(stateLeaf2.pubKey.equals(user2Keypair.pubKey)).to.eq(true);
+```
+
+We see that is important that we set the final message (the one with the new vote) with nonce 1, as this vote would be counted as the first vote.
+
+:::info
+Tests related to key changes have been added to the [core package](https://github.com/privacy-scaling-explorations/maci/blob/dev/core/ts/__tests__/) and to the [cli package](https://github.com/privacy-scaling-explorations/maci/blob/dev/cli/tests/).
+:::