From e08d3022006f6f0f913e9bce8c495aa9ea2c676c Mon Sep 17 00:00:00 2001 From: Denis Varlakov Date: Tue, 16 Jul 2024 08:54:51 +0200 Subject: [PATCH] Update README Signed-off-by: Denis Varlakov --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 0dde73d..5b60591 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ signers to commit nonces ahead of time), and identifiable abort. This crate provides: * Distributed Key Generation (DKG) \ FROST does not define DKG protocol to be used. We simply re-export DKG based on [CGGMP21] implementation - when `cggmp21-keygen` feature is enabled, which is a fairly reasonalbe choice as it's proven to be UC-secure. + when `cggmp21-keygen` feature is enabled, which is a fairly reasonable choice as it's proven to be UC-secure. Alternatively, you can use any other UC-secure DKG protocol. * FROST Signing \ We provide API for both manual signing execution (for better flexibility and efficiency) and interactive protocol @@ -23,7 +23,7 @@ The crate is wasm and no_std friendly. ### Distributed Key Generation (DKG) First of all, you need to generate a key. For that purpose, you can use any secure -(preferrably, UC-secure) DKG protocol. FROST IETF Draft does not define any DKG +(preferably, UC-secure) DKG protocol. FROST IETF Draft does not define any DKG protocol or requirements it needs to meet, so the choice is up to you. This library re-exports CGGMP21 DKG from `cggmp21-keygen` crate when `cggmp21-keygen` feature is enabled which is proven to be UC-secure and should be a reasonable default. @@ -39,7 +39,7 @@ let outgoing: impl Sink>; where: * `Msg` is a protocol message (e.g., `keygen::msg::threshold::Msg`) -* `round_based::Incoming` and `round_based::Outgoing` wrap `Msg` and provide additional data (e.g., sender/recepient) +* `round_based::Incoming` and `round_based::Outgoing` wrap `Msg` and provide additional data (e.g., sender/recipient) * `futures::Stream` and `futures::Sink` are well-known async primitives.