Redundant Output Descriptor Backups (Shamir style)

Would it be possible to create a shamir secret sharing standard for backing up your output descriptor. So for example with a 2/3 quorum you could store one part with each seed backup and if one location were to be compromised your privacy would still be intact.

In order for you to reconstruct your output descriptor you would need 2 of the 3 secrets from each location.

Giving the same redundancy of a multisig whilst maintaining privacy.

Does this make sense?

Like this?

Essentially yes, but in a standardised way. Not focusing on encoding as efficiently as possible (as with the seedhammer) but focusing on recoverability.

I don’t see why that wouldn’t be possible.

Can foundation look into making it happen?

Potentially next year once we get our upcoming product launch out of the way. We are a small team that has to remain focused on a) our product roadmap and b) what most customers are requesting.

If you’d like, I can move this topic to the feedback category so others can see it and register their interest?

Sure!

1 Like