Add Ranges to to Output Descriptors #21199

1. 
   prusnak commented at 3:57 pm on February 16, 2021: contributor

   Output Descriptors do not contain support for ranges.

   BIP44/49/84 account uses two chains (for receiving addresses and for change addresses).

   Having possibility to express ranges would allow us to capture the essence of BIP44/49/84 accounts in one Output Descriptor, e.g.

   0pkh([d34db33f/44'/0'/0']xpub6ERApfZwUNrhLCkDtcHTcxd75RbzS1ed54G1LkBUHQVHQKqhMkhgbmJbZRkrgZw4koxb5JaHWkY4ALHY2grBGRjaDMzQLcgJvLJuZZvRcEL/[0-1]/*)
   

   (note the [0-1]/* at the end).

2. prusnak added the label Feature on Feb 16, 2021
3. 
   Rspigler commented at 6:41 pm on February 17, 2021: contributor

   Concept ACK. Would fix https://github.com/bitcoin/bitcoin/issues/17190
4. 
   sipa commented at 6:51 pm on February 17, 2021: member

   Conceptually, descriptors describe a list of scriptPubKey (along with information for spending from it). If you write xpub/[0-1]/*, do you mean:

   • The list xpub/0/0, xpub/1/0, xpub/0/1, xpub/1/1, xpub/0/2, xpub/1/2, … (just interleaving the lists)
   • Changing descriptors to effectively be a description of multiple lists?
   • A way of writing two descriptors; perhaps one which is implicitly imbued with the meaning “payment addresses” and a second with meaning “change addresses” (this is often suggested to avoid the redundancy, but I feel this belongs in a different layer)?

   The first, if there is a use case for it, would be fairly simple and fit will in the current design. The others are more invasively, and probably not desirable in all places were descriptors are used.

5. 
   prusnak commented at 7:17 pm on February 17, 2021: contributor

   Ah, I didn’t know about #17190 - closing as duplicate of https://github.com/bitcoin/bitcoin/issues/17190
6. prusnak closed this on Feb 17, 2021

   ---

7. DrahtBot locked this on Aug 18, 2022

Contributors
prusnak Rspigler sipa

Labels
Feature