A legacy bitcoin core pockets on testnet was created and acquired bitcoin to addresses on derivation paths like: m/0'/0'/0', m/0'/0'/1' and m/0'/0'/2'
Now with a purpose to create unsigned transactions (PSBT) in a much less error inclined and tedious means an try was made to import the legacy bitcoin core pockets watch-only into sparrow and bitcoin secure.
Firstly the pockets was migrated with bitcoin-cli migratewallet "my_wallet" (as legacy wallets will now not be supported going ahead)
Thereafter the descriptors had been exported with out personal keys:
bitcoin-cli listdescriptors false
This output 11 totally different descriptors.
One of many descriptors appeared like this:
combo(tpubD6NzVbkrY...wWgAYi5D/0h/0h/*h)#leqp7cnz
Guessing that these are the legacy deriv paths talked about above.
When importing this output descriptor…bitcoin secure doesn’t import it and sparrow says:
Non-standard little one derivation detected – Sparrow doesn't help non-BIP32 wallets with out commonplace obtain and alter chains after which says it’s an invalid output descriptor.
Eradicating combo and setting it as wpkh labored on bitcoin secure however then raised an Error whereas parsing xkey.
Why is that this descriptor unimportable?
Additionally why do different descriptors begin with the deriv path like this:
wpkh([9c5bc3d1/84h/1h/0h]tpubDDXhjmNvux...AVPyjwv/0/*)#96c85rys
