From a4d49078673b716242f303ff95681dd33a4f28a7 Mon Sep 17 00:00:00 2001 From: Alfredo Garcia Date: Sun, 9 May 2021 08:48:56 -0300 Subject: [PATCH] change other considerations section to not included --- rfcs/0001-messages.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/rfcs/0001-messages.md b/rfcs/0001-messages.md index 452b064..e702874 100644 --- a/rfcs/0001-messages.md +++ b/rfcs/0001-messages.md @@ -297,10 +297,13 @@ Bytes | Field name | Data type ------|------------------|----------- 64 | final_signature | FinalSignature -## Other considerations +## Not included + +The following are a few things this RFC is not considering: - After the dealer sends the initial `MsgDealerBroadcast` to all the participants, the aggregator must wait for signers to send the second message `MsgCommitments`. There is no timeout for this but only after the aggregator received all the commitments the process can continue. These restrictions and event waiting are not detailed in this RFC. -- This implementation considers not only communications between computer devices in the internet but allows the process to be done by other channels, the lack of timers can result in participants waiting forever for a message. It is the participants business to deal with this and it will not be detailed in this RFC. +- This implementation considers not only communications between computer devices in the internet but allows the process to be done by other channels, the lack of timers can result in participants waiting forever for a message. It is the participants business to deal with this and other similars. +- The RFC does not describe a Service but just message structure and serialization. ## Testing plan