Reprovision existing key (zero backups) off of existing shard file #56

New Issue

Closed

opened 2024-12-11 17:56:55 +00:00 by ryan · 1 comment

ryan commented

2024-12-11 17:56:55 +00:00

Owner

This would require n-1 operators to determine without any possible ambiguity what key is missing. This should only be performed in the event an operator has lost every backup of their key.

ryan added this to the Custody Framework project 2024-12-11 17:56:55 +00:00

ryan commented

2025-02-25 04:56:36 +00:00

Author

Owner

Changing requirements: We will assume we know which operator is missing. Therefore, bus factor can be more than 2.

This is implemented now as keyfork provision shard.

Changing requirements: We will assume we know which operator is missing. Therefore, bus factor can be more than 2. This is implemented now as `keyfork provision shard`.

ryan closed this issue

2025-02-25 04:56:36 +00:00

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: public/keyfork#56

No description provided.