BitcoinDesign
Descriptors for printable backup template community file
I would like to consider adding an output descriptor to the printable template community file, but want to make sure it's done accurately.
Benefit: a descriptor could be a scannable QR code to store important info for restoring the wallet. This would make this data usable without asking a user to type in complicated strings. To my understanding, this may be necessary for P2TR wallets.
However, such a descriptor should not include any private key data as we wouldn't want that passing through a printer. So we should first explore what kinds of descriptors are most appropriate for this situation. Seeking developer consult on this.
Great idea, something else to think about is how would importing this descriptor in a recovery situation look like in-app?
Alright, here's a mockup of a descriptor added to a print template. Thanks to @notmandatory for helping me with the correct descriptor formatting.
I'd like to add this to the manual backup section of the daily spending wallet. Upon closer inspection of the community file for the printable template, I'm not sure it's the right place. The reason is because when I read the text (such as "Write down the following information if it is provided. It is not absolutely necessary, but may simplify the wallet recovery process.") it makes me think the community file is meant to be used as a resource external to the software. Meaning, the printable file was provided by someone other than the wallet developer.
This descriptor QR is something that would be generated by the wallet software itself, and is unique to each wallet. So it's a related but slightly different use case.
Also note that per BIP 86 some (most?) wallets will need to record two descriptors, one for external addresses tr(.../0/*) and one for internal (change) addresses tr(.../1/*). @achow101 has a BIP 389 proposal that could combine these two into one descriptor, not sure if/when this will make it's way into any wallet projects.
