Importing testnet key asks for xpub, actually wants tpub / upub
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.6k
- Forks
- 3.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 61
Description
When importing a public key for a wallet on testnet, the GUI asks you to enter the xpub. But if you paste an xpub, the "next" button remains greyed out. It's not possible to proceed unless you paste in an extended public key with the expected version bytes; this message should probably be conditionalized, or perhaps it should display an "unexpected version" error if the wrong version bytes are detected.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the GUI flow for importing a public key into a testnet wallet and trace the validation behind the disabled “next” button. Confirm how xpub, tpub, and upub version bytes are handled, then verify that the prompt or validation error matches the accepted key format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100