Skip to content
This repository has been archived by the owner on Jun 22, 2023. It is now read-only.

Process the replay-dkg-messages operation on the Airgapped machine #136

Open
zavgorodnii opened this issue May 27, 2021 · 0 comments
Open
Assignees

Comments

@zavgorodnii
Copy link
Contributor

zavgorodnii commented May 27, 2021

THE PROBLEM (BACKGROUND)

If someone successfully went through the DKG and lost his communication keys and airgapped state, but still has his private bip39 mnemonic, they can not sign any data.

THE SOLUTION (BACKGROUND)

We can scan the topic data for messages from the finished DKG round, provide a mapping from the old communication keys to the new communication keys, build a new Operation for the airgapped machine with both the old messages and the new communication keys — and then process that operation inside the airgapped machine.

THE TASK
— Add a processor for the Replay Operation (generated by the Client, see #135) that replays all operations for a finished DKG round and prepares the Airgapped machine to sign data.
— Write airgapped tests & flow tests.

@pr0n00gler pr0n00gler self-assigned this Jun 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants