Shlomtz

can be done is a similar fashion to the two-party protocols [benchmarks](https://github.com/KZen-networks/multi-party-ecdsa/tree/master/benches/two_party_ecdsa) A good comparison might be to https://gitlab.com/thorchain/tss/go-tss/-/merge_requests/160

https://github.com/binance-chain/tss-lib implements GG18. We would like to add benchmarks and comparison to tss-lib key generation and signing run locally between different `t` and `n` parameters. Benchmark code for this library...

Identifiable Abort in Threshold Signatures (IATS) - problem statement Informally, IATS is a way for honest parties to either output a valid signature or to agree on the set of...

In the multi-party ECDSA case, in `mta.rs`, in `impl MessageA` the range proofs are not included for Alice, and in `impl MessageB`, instead it is only computing a proof of...

Can't run both CCLST keygen and sign test at the same time

8

While running `protocols::two_party_ecdsa::cclst_2019::test::tests::test_two_party_sign` or `protocols::two_party_ecdsa::cclst_2019::test::tests::test_full_key_gen` is always working and passing. Trying to just `cargo test --features=cclst` returns a PARI error. Each time a different one: It can sometimes work, while...

Consumers of the app probably want to use a single protocol. They should be able to choose which one and build only for him. Currently there's a single feature to...

example: https://github.com/KZen-networks/multi-party-ecdsa/blob/master/src/protocols/multi_party_ecdsa/gg_2018/party_i.rs#L202 Should be replaced with an `Err` returned to the caller

Add support for {2,3} threshold signing

1

Lindell's Key Generation [1] protocol could be adapted to support {2,3}-threshold Signing if we implement the functionality _F_rand_ from [2] for generating shares of random values non-interactively. 1) each party...