< gwillen>
I am importing a descriptor that looks like "tprvXXX/blah/blah/blah/*"
< gwillen>
and Core tells me that it does not have private keys and cannot sign
< gwillen>
I assume this is a "we didn't implement that yet"
< gwillen>
(actually just to make this simpler: I just tried one with only hardened deriv and only a single key, no star at the end, and it still does not love me)
< gwillen>
also just to give the endgame here: I eventually want derived-multisig-signing support for PSBT use
< gwillen>
but I figure that starting with derived-single-key is better ;-)
< sipa>
yeah, not implemented; achow101's native descriptor wallet includes code to implement that
< gwillen>
actuall hmm, it does it even for e.g. sh(wpkh(tprvXXX)) with no derivation path
< sipa>
gwillen: you mean for importmulti?
< achow101>
gwillen: currently private keys aren't derived
< gwillen>
yeah
< gwillen>
I am using importmulti
< sipa>
you need to specify the private keys separately from the descriptors
< achow101>
gwillen: the base private key (i.e. the one provided in the descriptor itself) will be extracted. derived private keys in the range will not be
< sipa>
achow101: no
< sipa>
the private key in the descriptor is used to derive pubkeys (for hardened paths), but not imported itself
< gwillen>
sadness
< gwillen>
where do I find achow101's native descriptor wallet
< gwillen>
this sounds like the Promised Future
< achow101>
gwillen: it's my latest PR
< achow101>
also #15024 may be of interest to you. I borrowed a commit from there for the private key stuff