@@ -34,8 +34,9 @@ in parallel!
3434
3535As an alternative to using echo-broadcast, other mechanisms are possible
3636depending on the application. For example, posting commitments (round 1
37- packages) to an authenticated centralized server that is trusted to provide a
38- single view to all participants (also known as 'public bulletin board')
37+ packages) to an authenticated centralized server. This server needs to be
38+ trusted to provide a single view to all participants (also known as "public
39+ bulletin board").
3940
4041### _ Identifier_
4142
@@ -53,17 +54,28 @@ This allows deriving identifiers from usernames or emails, for example.
5354
5455### _ Peer to peer channel_
5556
56- Peer-to-peer channels might need to be authenticated (DKG messages, and FROST
57- signing messages if cheater detection is required), meaning there is assurance
58- on who is the sender of a message, and might be confidential (DKG messages, and
59- FROST signing messages if the messages being signed are confidential), meaning
60- no other party listening to the communication can have access to the message.
57+ Peer-to-peer channels are required to send data back and forth between
58+ participants (during DKG) and between coordinator and participants (during
59+ signing) in order to use FROST. These channels have different requirements
60+ in different scenarios:
61+
62+ - They need to be authenticated when sending DKG messages, and when sending
63+ signing messages if cheater detection is required. In this context,
64+ "authenticated" means that the recipient must have assurance on who is the
65+ sender of a message, using e.g. digital signatures.
66+ - They need to be confidential when sending DKG messages, and when sending
67+ signing messages if the messages being signed are confidential. In this
68+ context, "confidential" means that no other party listening to the
69+ communication can have access to the contents, using e.g. encryption.
70+
71+ In practice there are multiple possible deployment options to achieve
72+ authentication and confidentiality:
6173
62- In practice there are multiple possible deployment options:
6374- Mutually authenticated TLS
6475- Noise protocol
6576- Wireguard
6677
78+
6779### _ Threshold secret sharing_
6880
6981Threshold secret sharing does not require a broadcast channel because the dealer is fully trusted.
0 commit comments