You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 22, 2023. It is now read-only.
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 client node command that:
— Reads a mapping from the old communication keys to the new communication keys;
— Replaces old communication keys with the new ones inside the FSM;
— Prepares an Operation with the old DKG messages.
The text was updated successfully, but these errors were encountered:
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 client node command that:
— Reads a mapping from the old communication keys to the new communication keys;
— Replaces old communication keys with the new ones inside the FSM;
— Prepares an Operation with the old DKG messages.
The text was updated successfully, but these errors were encountered: