DKG Key Refreshing via Proactive secret sharing

[cygnusv]

Related issue: #78

[cygnusv]

See anoma#18

[theref]

What would trigger this? PRE nodes currently have an idea of the fleet state. Would it just be a case of monitoring that equivalent state and triggering whenever a node leaves that was part of a DKG ceremony that I participated in?

[piotr-roslaniec]

During our code review we put forward a few ideas on how we could alter Ferveo to better fit our needs, specifically:

• Remove weighting from nodes - each node gets an equal amount of key shares
• Further, we set a limit of one share per node

With these changes in mind, it seems like the key refresh described in the original issue (anoma#18) could be simplified to "running the same DKG again with final key 0".

This is not exactly the kind of solution we want (Proactive secret sharing). In our approach, we would need DKG participants to construct random polynomials and use them to update their key shares.

I suspect this work may be blocked by the alternations we've made during our code review.