Skip to content

Conversation

@3rdIteration
Copy link
Contributor

What is this PR for?

Provide additional information when wallet descriptor import fails

Initial work in progress and proof of concept, will test on hardware with some existing test wallets and see if additional refinements are required. (And share some examples with screenshots)

Changes made to:

  • Code
  • Tests
  • Docs
  • CHANGELOG

Did you build the code and tested on device?

  • Yes
  • Pending

What is the purpose of this pull request?

  • Bug fix
  • New feature
  • Docs update
  • Other

@tadeubas
Copy link
Member

tadeubas commented May 6, 2025

Tested one case:

Wallet is 669dce62 with 84h/0h/0h, the descriptor loaded is for e0c595c5 with 84h/1h/0h, but same XPUB:
image

Loaded descriptor (note the fingerprint and derivation path differs):

{
  "descriptor": "wpkh([e0c595c5/84h/1h/0h]xpub6Cygb51hbAxuxKQ4hwVV5z6YvhauXbhDexEuA7EoAq9DkejbuF2najEM3YdY2BvC39XYa9nHE3R9QWr2yYgTU58LTNQ7ipFQoj4TszqYVeS/0/*)#h4srsagr"
}

The XPUB exported by Krux after loading the descriptor above (other fingerprint and derivation):

[669dce62/84h/0h/0h]xpub6Cygb51hbAxuxKQ4hwVV5z6YvhauXbhDexEuA7EoAq9DkejbuF2najEM3YdY2BvC39XYa9nHE3R9QWr2yYgTU58LTNQ7ipFQoj4TszqYVeS

Krux loaded the descriptor without errors or warnings, it appears to not check fingerprint and derivation... I know this was already the behavior before this PR, but I am wondering, is this correct? 🤔

@tadeubas
Copy link
Member

tadeubas commented May 6, 2025

Regarding the PR changes, giving more details in the error msg will help users really understand (as we don't translate error messages)? For example, to me, the msg below is difficult to understand:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants