Salvatore Ingala

Solved for the python client (all address types) in #227.

Hi @0xSaksham, Thanks for your interest, you're very welcome to make a PR to suggest improvements, although this issue is more a reminder for me to fix things at some...

> @bigspider first of all, thanks for this issue, really waiting for this possibility to be opened Regarding taproot trees - won’t it be possible to pass the whole taproot...

> @bigspider thanks a lot for your reply, now it's clear One question in this case appears We're using taproot leaf scripts (told above), but not using an internal public...

@fess-v could you describe the kind of descriptors and/or signing flow that such extension wallets are using? I'm not familiar so it's hard to give an informed reply.

Not sure I understand; if you're not willing to reveal the descriptor, likewise you're not willing to reveal the wallet policy. If the limitation is because some systems are designed...

Since version 2.1.2, #133 is merged, which allows using a non-zero `p1` byte (currently ignored). Therefore, we could reserve (for example) the two lowest-significant digits of `p1` for the preferred...

As per the discussion in #153, there are some use cases that don't quite fit the "wallet policy" model (at least in the current version), yet it would be useful...

Thanks @harshit0verma, please let me know if you have any question. It would be interesting to do this on both the python and the Rust client libraries, but it should...

> what are "hardened" symbols ? You can read about it in [BIP-32](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki) and applications like [BIP-44](https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki). There are two common notations for the symbol; for example, the same valid...