idea: getkeypools ? about hwi

[instagibbs]

As a non keypool import option?

…

On Mon, May 13, 2019, 8:08 PM William Casarin ***@***.***> wrote: related: #57 <#57> #135 <#135> It would be nice to just type getkeypools 0 1000, which would dump all the relevant paths (including change) for that device. in the case of trezor, it needs: legacy: bip44 p2sh-p2wpkh: bip49 p2wpkh: bip84 would save a lot of headache for wallet devs looking to integrate hwi — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#172?email_source=notifications&email_token=ABMAFUYVYTIQLWJLPTJ5DM3PVH7JFA5CNFSM4HMUL2DKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GTRTZYQ>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABMAFU3WMH26NVCPQFA5BKTPVH7JFANCNFSM4HMUL2DA> .

[jb55]

I guess this is similar to #137 but I was thinking it would have the same output format as getkeypool

[jb55]

@instagibbs oh I just realized that would be tricky... you would need a non-keypool import for already used keys wouldn't you. and there may be no way to know which ones have been used ahead of time... hmm

[jb55]

I realize now that #137 will be better once we have native descriptor wallets...