GitLab

Currently NO must manually perform make backup for TSS keyshares, which change every churn. In a disaster scenario, NO's may not be able to reconstruct keyshares due to not enough backups.

In order to capture 2/3+ key share backups every churn (for emergency purposes, and to protect NO from infra fails), suggest making backup automatic for all make status commands.

1. Remove the 'Are you sure? Confirm [y/n]' prompt for make backup (it's non-destructive ... just do it immediately).
2. Auto-backup for every make status run.

Security discussion: The user will have a backup/ folder created with key shares and private keys on the machine they are running, possibly without them knowing. This can be mitigated with public awareness notice posted in Discord. The NO's machine (laptop, etc) used to run node-launcher folder with kubectl should already be secure and is already integral part of trusted zone, so storing backup/ folder automatically should be fine. This is a good trade-off to secure TC against existential threats.