-
We currently have a 2-round DKG, where we perform re-attempts as necessary.
https://eprint.iacr.org/2024/397 proposes a 1-round DKG. Since we don't vary our threshold upon re-attempt, we can do the…
-
https://eprint.iacr.org/2022/1389.pdf details a DKG which they claim runs in O(n) without faults, yet in O(n log n) with arbitrary faults.
The existing DKG operates in O(n^2), and moving to O(n) is…
-
Add test vectors for
- [ ] correct DKG protocol runs
- [ ] incorrect contributions covering all edge cases
-
Our CI is currently too flaky.
Tests needs to be fixed / improved to avoid flakiness.
-
See: https://github.com/stacks-network/stacks-core/blob/5d2cbdd1ab6bd6cfde8f4528eb5fae5777037af5/stacks-signer/src/signer.rs#L1372
If signers see that a threshold has been reached and no approved k…
-
Some stuff that needs to be clear in order to implement t of n threshold signing
## 1. DKG protocol sessions
Doing DKG to get `ThresholdKeyShare`s involves an initial DKG with only `t` particip…
-
I remember when we were discussing the new DKG/UI system, the core goal (in my mind at least) was better UX and chance of success of setting up Federation by verifying critical parts of the config **b…
-
The stacks signer needs logic to trigger another DKG round if a certain amount of time passes and we still have no confirmed DKG vote (maybe a certain number of blocks combined with last message recei…
-
As we determine whether Alice pays on a usage model, a subscription model, or both - ie:
https://github.com/nucypher/nucypher/issues/3057
...we also need to define how Enrico has standing to adh…
-
Currently signers just assume that if a threshold weight of responses have not been received for a DKG vote round that they will eventually show up. This could not be the case and they should have som…