Look, I’m a regular dude that doesn’t program, not even a microwave, so most of this is over my head but here’s my experience.
Slow synching with ZWL recently, and always slow synching with Nighthawk led me to get Ywallet a couple of days ago. It synced fast the first time, then slow, now back to normal. I moved 1 ZEC from exchange to T address, and it shows in the balance but doesn’t show in history. Also wouldn’t let me send any Zec yesterday, but showing I can today. What I really need to know is how to shield what is in my T address, it doesn’t separate the balance when I try to send, so I can’t send from T to Z.
I think these wallets need a detailed instructional video on YouTube for us laypeople.
2 Likes
If you tap the barcode in Ywallet it should toggle between your Z and T address, when showing your T address there should be a button there to shield the transparent funds, this worked fine for me when I did it yesterday, do you see that option?
1 Like
Yes. I figured it out a few minutes ago. Apparently I have to be in the Advanced Wallet not the simple wallet. I would have thought that being that is one of the most important features it would have been showing up in the simple wallet. I am showing a transaction for the shielding in my history now, but I’m still not showing a transaction for when I moved my zcash from the exchange. Weird.
Thanks for your help, I’ll keep playing around with this. I wish these things came with an instruction manual, they all have different features.
1 Like
You can spend your transparent funds and your shielded funds when you are on the trp side.
Only transactions that involve your shielded address will be shown in the history.
The manual is at https://ywallet.app
It can be directly accessed from the wallet by the help menu.
5 Likes
Thank you! Everything is working well today. Thanks for letting me know the T activity won’t be showing up. I found that curious. There’s a lot of features to learn about, I’m impressed. Now I just need to fill it. 
If my house was on fire, I wouldn’t care who the fireman was and what kind of truck he was driving.
Seems like they’re not concerned with the fire @hanh. Admitting there’s a fire is always a problem. It’s best to just quietly put it out and write it off as a temporary glitch, which hopefully will be the case. I see they have been committing changes, so that’s encouraging.
I can see that my wallets aren’t syncing and I will need to migrate them. I will consider Ywallet! Thanks,
I have a Galaxy S21 5G that I consider to be pretty new and high-endish and it crashes. Not sure if it memory related. But, the wallet has about 30 notes which I assume is related to why it’s crashing.
This is concerning. Right now the two official servers are not functional. The free2z lightwalletd is running fine but I assume if a lot of people move to it that it will suffer from the same problems
⚡ grpcurl lwdv3.zecwallet.co:443 cash.z.wallet.sdk.rpc.CompactTxStreamer/GetLatestBlock
Error invoking method "cash.z.wallet.sdk.rpc.CompactTxStreamer/GetLatestBlock": rpc error: code = Unavailable desc = failed to query for service descriptor "cash.z.wallet.sdk.rpc.CompactTxStreamer": unexpected HTTP status code received from server: 502 (Bad Gateway); transport: received unexpected content-type "text/html"
⚡ grpcurl mainnet.lightwalletd.com:9067 cash.z.wallet.sdk.rpc.CompactTxStreamer/GetLatestBlock
{
"height": "1712154",
"hash": "1+QVsQAmS0qYVIs3ayxd5WR5VaoLUGYUPg5LAQAAAAA="
}
⚡ grpcurl zuul.free2z.cash:9067 cash.z.wallet.sdk.rpc.CompactTxStreamer/GetLatestBlock
{
"height": "1736471",
"hash": "/hQteqRSArnWFfcAsiM9dpm933j3cwXk8fYxAAAAAAA="
}
zecwallet.co is returning 502. lightwalletd.com is behind (almost caught up again tho). zuul.free2z is working but I can tell that the traffic is not extremely high because it’s not using all that much bandwidth.
All wallets should allow users to change servers. Empirically blaze sync doesn’t work for me with the big blocks and old wallet, warp sync does. Are there any theoretical reasons why blaze sync would be preferred?
After 6 days I decided to reach out to Ledger Support. Very kind and helpfull. However the solution according to them would be to buy a different brand of hardware wallet 
On another note, the CEO of Ledger shared on twitter spaces, Zooko was present, that if the Zcash Community wants to have shielded ZEC on ledger it is possible that a third party can build this and integrate it with their platform.
2 Likes
This statenent triggers me!
3 Likes
For real. WTF is he out of the loop on the current grant?
1 Like
We completed the app long time ago.
Unfortunately, it was never integrated in a web or desktop wallet. Without that, it was not possible to submit to Ledger because it was not possible to use the app. We tried to coordinate and get support to get this used in zecwallet although it was not under our engagement.
More recently, we decided to move forward with integrating ourselves into Zecwallet so there is finally some application that uses the Ledger app we developed. As part of that effort, we have upgraded the app, added support for new devices, improve the code base and we are finalizing the integration. Our team is really looking forward to seeing this being use on a daily basis…
8 Likes
That’s actually pretty good to hear that.
A shame it couldn’t get that integration (seems Trezor will win that race), but glad to hear Zecwallet benefits. Maybe it can also find its way into YWallet as well.
If the app cannot be loaded on a device because it is too large, I don’t understand how it is finished. You don’t plan to support the nano S?
Nano S was originally supported (within the timeline of our development).
Since the time we completed the project (long ago), Ledger kept increase SDK sizes, etc.
Due to the device limitations, Ledger decided to discontinue Ledger Nano S in June:
The recommended and available devices at the moment are Nano X and S+
1 Like
Understood. Is it possible to use the S+ in dev mode or is a special unit required like the X?
Thanks for @ing me. We are absolutely actively working on it. I will post our progress during the last couple of months in the original post soon. 
2 Likes
There’s no special unit requirement for S+ so you can sideload the app without any issue (except a few annoying prompts about app not genuine etc etc).
As a matter of fact, you’ll be seeing such setup at ZCon3 soon 
6 Likes
Congratulations. I am looking forward to using your app on my nano X.
2 Likes
There’s a new Zecwallet Lite (Desktop) release that should address most of the sync issues and make it reliable again. It features:
- Dynamic batch sizes to adjust for empty/full blocks
- Save sync progress so we don’t have to restart if we crash
- Parallelism improvements
- Improve connectivity and handle server connection failures gracefully
- Tweak sync parameters to use as many threads as possible.
- Show much more detailed sync progress and stats
Additionally, Zecwallet’s new LightwalletD server is much bigger, able to serve 10x the bandwidth as before. This should make syncing more reliable.
Thank you everyone for your patience. These improvements will make their way to the mobile apps soon.
14 Likes