diff --git a/apps/website/versioned_docs/version-v2.x/contributing/contributing.md b/apps/website/versioned_docs/version-v2.x/contributing/contributing.md index 424a57d31..db1f66ce8 100644 --- a/apps/website/versioned_docs/version-v2.x/contributing/contributing.md +++ b/apps/website/versioned_docs/version-v2.x/contributing/contributing.md @@ -57,7 +57,7 @@ Pull requests are great if you want to add a feature or fix a bug. Here's a quic 7. Make the test pass. -8. Commit your changes. Please make sure your forked `dev` branch is synched 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: +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)) diff --git a/apps/website/versioned_docs/version-v2.x/core-concepts/maci-keys.md b/apps/website/versioned_docs/version-v2.x/core-concepts/maci-keys.md index 57384689b..2cdfb0dc5 100644 --- a/apps/website/versioned_docs/version-v2.x/core-concepts/maci-keys.md +++ b/apps/website/versioned_docs/version-v2.x/core-concepts/maci-keys.md @@ -72,3 +72,13 @@ For instance, given a seed of `2751400778105288503616280864801989336281162831694 ``` Serialized, these will look like **macipk.0e5194a54562ea4d440ac6a0049a41d4b600e3eb0bf54486e7a5f7e27521f6ba** and **macisk.3cd46064ea59936f82efb384059dd4f5b6b8e5c7546614caf7c1c3be0daea00f**. + +## Generate MACI Keys + +After successfully [installing](../getting-started.md#installation) MACI, you can easily generate your MACI key pair by running: + +```bash +pnpm run genMaciKeyPair +``` + +This command will create the necessary public and private keys required for running various MACI operations.