Because workflow of exportpubkey would must to be securely closed verifying addresses obtained on wallet software (Sparrow, for instance), issue reported #621 is conceptual consistent.
This pull request is categorized as a:
[X] New feature
[ ] Bug fix
[ ] Code refactor
[ ] Documentation
[X] Other (export XPUB address from seed and verify addresses workflow)
Checklist
[X] I’ve run pytest and made sure all unit tests pass before sumbitting the PR. They was updated, too.
If you modified or added functionality/workflow, did you add new unit tests?
[ ] No, I’m a fool
[ ] Yes
[X] N/A
I have tested this PR on the following platforms/os:
[X] Other (enteropositivo emulator), new workflow was probed with sparrow wallet for segwit, nested and legacy scripts (taproot was not implemented)
Note: Keep your changes limited in scope; if you uncover other issues or improvements along the way, ideally submit those as a separate PR. The more complicated the PR the harder to review, test, and merge.
Description
Because workflow of exportpubkey would must to be securely closed verifying addresses obtained on wallet software (Sparrow, for instance), issue reported #621 is conceptual consistent.
This pull request is categorized as a:
Checklist
pytestand made sure all unit tests pass before sumbitting the PR. They was updated, too.If you modified or added functionality/workflow, did you add new unit tests?
I have tested this PR on the following platforms/os:
Note: Keep your changes limited in scope; if you uncover other issues or improvements along the way, ideally submit those as a separate PR. The more complicated the PR the harder to review, test, and merge.