Ivo Kubjas

> @ivokub replacing FS-DKR with aux info & key refresh from CGGMP paper. Makes sense. But what do you think about keeping the resharing strategy of FS-DKR compared to CGGMP?...

> Looks great, my only point to add would be to not replace things if possible since we at Webb are still using GG20. If we could just add the...

Thank you @davidsemakula for the review. The approach completely makes sense and also seems very intuitive. I think it would beneficial to consider the same security assumptions for different protocols.

Hi @luca992, yes the tests are now taking longer as we are now sampling safe primes as according to the paper. Additionally, https://github.com/webb-tools/cggmp-threshold-ecdsa/pull/44 introduces additonal overhead as we fix the...

Yup, in CGGMP the assumption is that the channels are authenticated between parties and broadcasts are reliable. Our approach is to use Noise protocol on a higher level which provides...

Hmm, I think the check is done transitively in FS-DKR. [Here](https://github.com/webb-tools/cggmp-threshold-ecdsa/blob/main/fs-dkr/src/refresh_message.rs#L126C14-L126C14) we create `NiCorrectKeyProof` which seems to be implementing https://eprint.iacr.org/2018/057.pdf. CGGMP paper defines PI-mod to be a simplification of 2018/057.

Another approach is to have a generic `FieldHasher[T ElementType]` interface as tracked in https://github.com/Consensys/gnark-crypto/issues/448, but we haven't figured out a nice way to implement. If we want to have a...

> > an interesting idea to have a separate interfaces where hash.Hash works as expected > > If you go this way, please be sure to break existing consumers of...

Thanks for the PR. I'm trying to have a look at it this week to give feedback. As of why we yet haven't added the constraining of the values always,...

Hi, indeed setting up the GPU support is a bit cumbersome and depends on the ICICLE library being set up correctly. Have a look at https://github.com/ingonyama-zk/icicle/tree/main/wrappers/golang on how to build...