diff --git a/README.md b/README.md index 3f3934ce..54e6ffc5 100644 --- a/README.md +++ b/README.md @@ -19,7 +19,7 @@ For instructions on how to ensure that the ceremony is executed properly, refer 1. A coordinator generates an accumulator 1. Participant downloads the latest accumulator -1. Participant contributes their randomness to the accumulator (randomness is permantently deleted after this step) +1. Participant contributes their randomness to the accumulator (randomness is permanently deleted after this step) 1. Participant uploads the accumulator back to the coordinator 1. Coordinator verifies the accumulator was transformed correctly and produces a new challenge diff --git a/RECOMMENDATIONS.md b/RECOMMENDATIONS.md index 78251535..9f52cf7e 100644 --- a/RECOMMENDATIONS.md +++ b/RECOMMENDATIONS.md @@ -15,7 +15,7 @@ Participants of the ceremony sample some randomness, perform a computation, and * using an unusual Rust toolchain or [alternate rust compiler](https://github.com/thepowersgang/mrustc) * lots of other ideas we can't think of -It is totally up to the participants. In general, participants should beware of side-channel attacks and assume that remnants of the randomness will be in RAM after the computation has finished. +It is totally up to the participants. In general, participants should be aware of side-channel attacks and assume that remnants of the randomness will be in RAM after the computation has finished. (the above section is taken from the [original powersoftau](https://github.com/ebfull/powersoftau) repository) @@ -23,4 +23,4 @@ It is totally up to the participants. In general, participants should beware of When contributing, Powers of Tau outputs the accumulator's hash to your terminal. This should be made available to the next contributor separately, as a checksum so that they can verify the file they have received is not tampered with. -As a final step, a randomness beacon is applied to the ceremony by the coordinator. This can be verified by running [this software](https://github.com/plutomonkey/verify-beacon/). \ No newline at end of file +As a final step, a randomness beacon is applied to the ceremony by the coordinator. This can be verified by running [this software](https://github.com/plutomonkey/verify-beacon/). diff --git a/phase1-cli/README.md b/phase1-cli/README.md index e7c4dc68..5542b16f 100644 --- a/phase1-cli/README.md +++ b/phase1-cli/README.md @@ -30,8 +30,8 @@ Optional arguments: Available commands: new creates a new challenge for the ceremony - contribute contribute to ceremony by producing a response to a challenge (or create a new challenge if this is the first contribution) - beacon contribute randomness via a random beacon (e.g. a bitcoin block header hash) + contribute contribute to the ceremony by producing a response to a challenge (or create a new challenge if this is the first contribution) + beacon contributes randomness via a random beacon (e.g. a bitcoin block header hash) verify-and-transform verify the contributions so far and generate a new challenge ``` diff --git a/phase1-cli/src/transform_pok_and_correctness.rs b/phase1-cli/src/transform_pok_and_correctness.rs index 9a707c39..75c9510b 100644 --- a/phase1-cli/src/transform_pok_and_correctness.rs +++ b/phase1-cli/src/transform_pok_and_correctness.rs @@ -23,7 +23,7 @@ pub fn transform_pok_and_correctness( parameters.total_size_in_log2 ); - // Try to load challenge file from disk. + // Try to load the challenge file from disk. let challenge_reader = OpenOptions::new() .read(true) .open(challenge_filename) diff --git a/phase1-cli/src/transform_ratios.rs b/phase1-cli/src/transform_ratios.rs index 7296c8a7..4788faee 100644 --- a/phase1-cli/src/transform_ratios.rs +++ b/phase1-cli/src/transform_ratios.rs @@ -12,7 +12,7 @@ pub fn transform_ratios(response_filename: &str, parameters: & parameters.total_size_in_log2 ); - // Try to load response file from disk. + // Try to load the response file from disk. let response_reader = OpenOptions::new() .read(true) .open(response_filename) diff --git a/phase1-coordinator/README.md b/phase1-coordinator/README.md index 1d94926a..7b39d44c 100644 --- a/phase1-coordinator/README.md +++ b/phase1-coordinator/README.md @@ -28,7 +28,7 @@ the coordinator commits to the next round and the ceremony advances by one round the commit is rolled back to the current round and all participants assigned to the next round are returned to the queue. See the documentation in [lib.rs](./src/lib.rs) as an entry point to a more -detailed explaination of how this library works. +detailed explanation of how this library works. ## Build Guide diff --git a/phase1/README.md b/phase1/README.md index ba5c2af2..6a458ca3 100644 --- a/phase1/README.md +++ b/phase1/README.md @@ -2,7 +2,7 @@ Distributed generation of powers of tau for Phase 1 of [BGM17](https://eprint.iacr.org/2017/1050). -Also contains a binary which converts the Powers of Tau to Lagrange coefficients and allows Phase 2 to produce efficient A, B and L queries for the Groth16 SNARK. +Also contains a binary that converts the Powers of Tau to Lagrange coefficients and allows Phase 2 to produce efficient A, B and L queries for the Groth16 SNARK. - Utilizes [Zexe's algebra crate](https://github.com/scipr-lab/zexe), meaning we support all available curves: - BLS12-377 diff --git a/setup1-shared/README.md b/setup1-shared/README.md index 6afff6b0..d75eeb90 100644 --- a/setup1-shared/README.md +++ b/setup1-shared/README.md @@ -16,5 +16,5 @@ Must be used with compatible versions of **serde** and **serde_json**. ## Error types -Right now the errors in encode/decode functions are the same as returned +Right now the errors in encode/decode functions are the same as those returned by **serde_json**