At phase1, signer tries to send p2p messages to every party holding a share regardless whether this party appear in list of signers. In other words, at phase1 party sends n messages, but should send t+1 messages.
Here's the code that causes this behaviour:
Phase1::start generates list of messages. Messages are sent to every party listed in the map in phase1.mta_a
ING has no intention of resolving this, nor on maintaining this further, and hence, this repo will be archived. Its usage is no longer recommended, see the updated README.
At phase1, signer tries to send p2p messages to every party holding a share regardless whether this party appear in list of signers. In other words, at phase1 party sends
n
messages, but should sendt+1
messages.Here's the code that causes this behaviour:
Phase1::start
generates list of messages. Messages are sent to every party listed in themap
inphase1.mta_a
map
is constructed inPhase1::new
, note that every party from keygen is included, regardless whether this party appears insigners
listSuggested solution: filter out parties that are not listed in
signers
list from the map inPhase1::start