Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jade issues with Specter signing #128

Closed
Dyor69 opened this issue Apr 3, 2024 · 8 comments
Closed

Jade issues with Specter signing #128

Dyor69 opened this issue Apr 3, 2024 · 8 comments

Comments

@Dyor69
Copy link

Dyor69 commented Apr 3, 2024

When I try to send a transaction with Specter Desktop I get get a message that ' device does not have matching signing key'
Also wont let me verfiy addresses
Not sure where the issue is as I have sent transaction without any issues in the past.
Any advice is greatly appreciated .

@JamieDriver
Copy link
Collaborator

That error must be coming from Specter - not one of ours.
So difficult to diagnose at this point as not sure how that error message arises.
Is it related to the version of the jade fw you are using, the version of the Specter install, or is it specific to a particular transaction ?
Any additional info would be very useful - thanks.

@JamieDriver
Copy link
Collaborator

JamieDriver commented Apr 3, 2024

From what I can gather, it looks like the seed Specter is expecting to see on the hw wallet is not the seed that is currently on there.
ie. Specter is expecting the root xpub/fingerprint to be xxx, but when it requests that from the hw, it gets yyy.

( fyi: when unlocked, Jade should display the wallet fingerprint in hex in the bottom-right of the screen. The fingerprint is a deterministically calculated short id for the mnemonic phrase / seed of the wallet plus any passphrase. )

@Dyor69
Copy link
Author

Dyor69 commented Apr 4, 2024

Thanks for you response Jamie.
Looks like its a fingerprint issue
Here's the message I get to verifiy receiving address
Screenshot 2024-04-04 at 11 05 27 am
And the send one
Screenshot 2024-04-04 at 11 08 58 am
This is the version of Specter
Version: v2.0.2rc8.dev0+g23ad1197.d20230921 UID: 1bf3305caf91e16b
JAde Firmware
1.0.29
Would you like me to paste the Jade xpub key here?

Thanks
Campbell

@Dyor69 Dyor69 closed this as completed Apr 4, 2024
@Dyor69 Dyor69 reopened this Apr 4, 2024
@JamieDriver
Copy link
Collaborator

I don't think there's anything I can do - this isn't an issue with Jade firmware - unless you're telling me (for example) it works with v1.0.27 but doesn't work with v1.0.29.
It looks like the Specter wallet was set up (with Jade?) with a particular seed/mnemonic, and now that Jade has a different seed/mnemonic (or is a different Jade?).

These messages appear to be saying, 'you've plugged the wrong hw unit' ?

@Dyor69
Copy link
Author

Dyor69 commented Apr 4, 2024 via email

@JamieDriver
Copy link
Collaborator

JamieDriver commented Apr 4, 2024

I assume you know what your 'recovery phrase words' are. [**DO NOT post them here (or anywhere!) ].
The 'fingerprint' you see in the bottom right is a short 'summary' (if you like) of that phrase (plus any bip39 passphrase). ie. a short id of the wallet. [ If you are using a bip39 passphrase you must be very careful to enter the exact same phrase each time. ]
Jot down that fingerprint (8 hex chars).

With Jade in 'locked' state, go 'Options->Temporary Signer' and enter the 'recovery phrase' words and any bip39 passphrase.
Connect to Specter and the Jade should unlock - it will show you the 'fingerprint' of the wallet you have just entered.
It should be the same as the one you recorded earlier above.

Yes, if the bip39 passphrase was entered even slightly differently, it will lead you to a different wallet, different fingerprint/xpubs, etc. If you've used this passphrase, I guess you could try slightly different variations of phrase, or spelling, capitalisation, etc. ...

Unfortunately with this stuff there is no way to go backwads eg. from fingerprint or xpub to recovery phrase or bip39 passphrase etc.

@Dyor69
Copy link
Author

Dyor69 commented Apr 6, 2024

Thanks Jamie
I new it was my error, so thanks for helping me narrow it down.
All sorted out now, it was the slightest difference in the passphrase. So sorry to waster your time.
It goes to show how careful you have to be to record everything accurately.

@JamieDriver
Copy link
Collaborator

Glad it all worked out for you! (and doubly glad it wasn't a bug in Jade fw! 🤣)
Nice one 👍

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

No branches or pull requests

2 participants