It's Here: Zashi-Keystone Hardware Wallet Integration for Shielded ZEC

for new users it can be very confusing

1 Like

Thanks for the response!

I also see a couple things that contribute to confusion as well as a new user of Keystone Wallet that is testing recovery with Zashi, because of behavior in Zashi I didn’t expect .

Because the UAs derived from the same seed were different on Zashi and Keystone, I had decided to try testing what happens if I send some Zcash from Zashi to the UA shown by Keystone of the same seed. So I was sending Zcash from and to itself so to speak.

This lead to more confusion because in Zashi it temporarily showed the amount that was being sent before later only showing the fee paid. Meanwhile, if I then reset the Zashi app and instead connected to the Keystone Wallet to the same seed I see a receive transaction but not the send transaction - furthermore the amount received was different than what I would of expected as it was more than the amount I entered to send (I’m assuming something to do with being change or something).

Also the Keystone Wallet connected doesn’t have the same transaction history in general, it only seems to show the confusing looking transactions I sent to myself the last couple days but not the older history of transactions and balance. So the total balance is different. I assume the reason the total balance is different is that the linked Keystone Wallet is automatically only using a recent birthday height…since it didn’t ask me to choose one? Is there a way to choose an older birthday height for the Keystone so that it shows the accurate total balance? Seems like a bit of a usability problem if I get a new phone and try to link my Keystone Wallet with a new install of Zashi and it doesn’t show the full history/balance

Oh yes, this is going to create some greatly confusing history. The useful thing that Zashi (or any wallet) could do here is detect when the user is asking to send funds to themselves (for which there may be a legitimate reason!) and show this fact in the UI (e.g. on the confirmation screen).

The specific problem here is that you, as the user, are asking the wallet to create a send-to-self transfer as a wallet-external action rather than via a wallet-internal action (like the shielding button), so you hit two different parts of the UI logic simultaneously. Not a whole lot of good answers here, other than the aforementioned making it clear that this is a send-to-self.

This is a known current limitation that we are tracking (iOS, Android).

3 Likes

Awesome, thanks for all the answers!

In case anyone runs into this, Zcash is now only in the “Cypherpunk” version of the Keystone firmware:

3 Likes

Update: Keystone hardware wallet does support passphrases now for Zcash!

Source: https://x.com/KeystoneWallet/status/1954890560449499428

7 Likes

Now to really put a bow on it and take advantage of all the utility and benefits that hardware wallet passphrases provide we just need the ability in Zashi to set the birthday height for Keystone Wallets (most important) and have the ability to delink and relink Zashi to Keystone Wallets

8 Likes

Any idea if this is permanent? Or will they add it to Multi-Coin at some point as well?

Also is there any info on how exactly zcash is derived from the seed. The deriviation path etc.

In case the wallet dies and you want to export the raw key into zcashd…etc. Is there a tool available for this, like we have the bip39 tool for most other coins…

1 Like

I have no idea :man_shrugging: