fs-dkr
fs-dkr copied to clipboard
ZenGo-X
FS-DKR: One Round Distributed Key Rotation
Hi, I want to modify the test_add_party test to change n, t and the number of people who are willing to do a resharing. For example, I have an error...
What happens if we don't verify that $A_{0}^{(a)} = tpk_{(a)}^{old}$ in step 2 of the FS-DKR protocol? Also why does $tpk$, the group public key stay the same from FS-DKG...
This adds an assertion of the assumption that `t
This utilizes the PDL With Slack ZK proof from GG18/20 (https://github.com/ZenGo-X/multi-party-ecdsa/tree/master/src/utilities/zk_pdl_with_slack) and uses range-proofs from https://github.com/ZenGo-X/multi-party-ecdsa/pull/145 to validate it. Also added a check for the moduli size to make sure...
Currently we follow multi-party-ecdsa logic of two dlog proofs see here: https://github.com/ZenGo-X/fs-dkr/pull/17/files#diff-386a609f746d74ecbc3e04d7ae0e82e2e7a58a72a16908d2fbbb955b9d355971R73 There is a bug in this logic, as can be explained and fixed here: https://github.com/ZenGo-X/multi-party-ecdsa/pull/145#issuecomment-953734674 please apply the...
Each new party should validate if there is a party_index collision.
Zeroize secrets when a party is excluded/a new party joins. The following scenarios can be observed: 1) party x is in new group but not in old group - receive...
Existing parties should submit their dlog proof as well (currently it's a bit cumbersome, as the LocalKey does not save the proofs and the secret is not available anymore later).
Our dynamic model relies on the fact the DKR is non-interactive therefore we have clear separation between the secret distribution and old committee and secret receiving by new committee :...