Reshare

[JesseAbram]

Reshare will be added in multiple steps over PRs so this is to track that progress

• Add Reshare cryptography to crypto
• Add next_peers to bulletin
• Add Reshare to dkg coordinator
• Add Reshare to PSS trigger
• Have Bulletin be able to manage setting next peers (this is a lot and it is ok to skip this and pull it to own issue)
• Have Bulletin be able to accept an update on the bulletin if a threshold is met
• Have nodes do a threhsold sig after reshare
• Have Node call back in after a reshare with a threshold signature to swap old peers with new peers
• Integration test

[JesseAbram]

Have Bulletin be able to manage setting next peers

To elaborate on this. There should be two ways this can happen

• one where we let the bulletin itself make changes, think a public chain is the bulletin and as validators rotate it updates the peers to be validators (can also be an internal dao to govern it or a multisig)
• Two ACP and ACP logic gating this

ACP logic gate

• Requires beefier logic driven ACP here for example maybe you can pre set some peers and it be allow these ppl to pick from certain peers, idk just throwing out ideas

[JesseAbram]

This also notes that the bulletin must change to help match this. As now it is appeand only but I need to be able to have changes made and keep the V0 post_id