From b496504cfc407ae55b0d8c05f7e40135a05c99a4 Mon Sep 17 00:00:00 2001 From: King Date: Mon, 3 Feb 2025 18:54:07 +0100 Subject: [PATCH] Fix typos in setup-mpc-client/README.md --- setup-mpc-client/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/setup-mpc-client/README.md b/setup-mpc-client/README.md index e6416e4..f8f0fd0 100644 --- a/setup-mpc-client/README.md +++ b/setup-mpc-client/README.md @@ -9,7 +9,7 @@ Participants in the AZTEC trusted setup multi party computation fall into three 1. **Institutional participants** - These participants are known up front and have been formally accepted into the computation by AZTEC. They have top priority during the ceremony. 2. **Early bird individuals** - Participants that have signed up for the ceremony prior to the _selection date_. They have secondary priority during the ceremony. -3. **Individuals** - Participants that have signed up for the ceremony after the _selection date_, or who were not choosen during selection. They have tertiary priority during the ceremony. +3. **Individuals** - Participants that have signed up for the ceremony after the _selection date_, or who were not chosen during selection. They have tertiary priority during the ceremony. The _selection date_ is goverened by a predetermined Ethereum block height. The block hash of the block is used as a seed to a pseudo random number generator which first selects a number of participants from tier 2, and is then used to randomise the priority order of participants in both tier 1 and tier 2. Unselected participants and participants in tier 3 are ordered on a first come first served basis.