It’s too bad it can’t receive in a taddr. Users of Trezor have to transfer to a hot wallet before they can put into Orchard.
This is false. Keystone can receive to a t-addr (there’s a t-addr in the UA generated by Zashi, as well as the t-addr displayed on its own for legacy applications that still haven’t added support for parsing UAs).
What Zashi does not support with Keystone is spending from transparent, because Zashi is a shielded-storage wallet. You have to shield any funds you receive on the Keystone’s transparent address before you can spend them (using the “Shield and consolidate funds” button on the Balances tab), which requires interaction with the Keystone to authorize the shielding transaction (just as it would for authorizing a regular spend).
4 Likes
Well - what is it then? Can I use the KS as a replacement for the Trezor if I don’t want the Orchard feature?
You’re replying in a thread about the Zashi-Keystone Hardware Wallet Integration.
For the Zashi-Keystone Hardware Wallet Integration, the Keystone device is used in a way that means the Keystone always stores funds as shielded, like the online Zashi wallet. And in the same way, it can receive to a t-addr, and send to external t-addrs.
If you want to use a Keystone for purely transparent usage, you won’t be able to do so with Zashi. But the Keystone firmware is open source, and you’re welcome to check there whether it supports creating fully-transparent transactions.
5 Likes
Something changed recently that caused this integration to stop working.
Possibly the latest zashi update?
Keystone throws OOM when reading the transaction QR from zashi, and is very slow when reading it.
Did Zashi change the way it generates the QR? Add integ tests in your CD pipeline please!
2 Likes
i tested also. for me its working fine - no error.
keystone is 1.8.2 (havent updated to latest yet)
zashi is 1.3.3 on iOS
1 Like
im also zashi 1.3.3(7), keystone firmware 1.8.2
it was working fine for me until recently. but something changed.
The QR scan is taking forever - it used to be done in seconds (10% → 20% → 70% … done in 3 seconds)
Now it reads 1% per second, and OOM after ~70%.
The rate of change in the QR image seems is much faster (idk how the QR comm works - but thats a visually noticable diff). It used to change slower.
For now, I moved the seed phrase into a connected wallet to be able to move the zec around. Gonna be annoying to re-do the metal-sheet seed phrase again in the future lol.
1 Like
I remember @tim_ukrainian had an issue with QR code and different screen brightnesses or night color shift.
Have you tried tweaking those to see if it speeds things up?
1 Like
Yeah tried all brightness variations. It was working until like 1 week ago.
Anyway, I moved my zec over to soft wallet. Just wanted to raise the flag.
If no one else is seeing this then I guess its just something off on my end lol ill try again in broad daylight to further test the brightness theory. Maybe the lighting in my room is off, or my hands shook too much,
ir could be because your transaction has many inputs. Is it a wallet that receives your mining awards maybe?
1 Like
In my case, on the contrary, it started working much better. Automatic brightness increase and full width QR magnification on a small screen started working fine. I had problems with QR occasionally, now they are gone. But keep in mind that dynamic QR is very sensitive to any interference on the screen. Protective glass or dust - any little thing can distort the data communication.
Another technical point to consider is that your KeyStone must be fully charged. I had a problem reading QRs after being without charge for a long time. I tried charging it lightly, but it seemed to freeze every time until I fully charged it.
3 Likes
Yes,
Brightness, night shift and touch assist (this semi transparent button that you can move around the screen) could be the elements slowing down qr code reading.
No issues with syncing since then.
3 Likes
I did not pay too much attention to inputs. I did move a decent chunk of zec (1k+), maybe I had too many notes or something.
Ok just tested with 0.01 zec, and it works. 15% -> 40% -> 75% ->done in less than 3 seconds.
I’m not sure what went wrong last time. Maybe the input was too large as mentioned by hanh? The lighting is the same in my room
1 Like
out of memory issues are most likely caused by too many inputs. If it happens, you can try breaking your tx into smaller amounts to try to use fewer notes.
New Firmware
2 Likes