I spun up zuul.free2z.cash:9067 and it’s working fine with ywallet on my bigger wallet. I’m sending and receiving funds again! No guarantees; but, at the moment mainnet.lightwalletd.com:9067 is not working and zuul.free2z.cash:9067 is. So, at least it’s maybe another option.
Three cheers for YWallet, @hanh and @skyl! I just synced a wallet I have been using since December 2020 over a spotty airport-style WiFi and with Ywallet + zuul.free2z.cash server it took a Pixel 4a (a 2020 phone) just under 19 minutes (I got distracted and did not note the exact time ).
It was a very pleasant experience and I can only offer the following three as improvement suggestions:
Ywallet could add an option to enter wallet birthday height rather than a date (both Nighthawk and ZecWallet provide those so that’s most likely what users have saved). Also maybe a small note saying that default start date is Zcash Sapling activation date (otherwise it seems a bit arbitrary);
my rescan was initially interrupted by me closing the app; after I reopened the rescan it started from the very beginning. If the engineering complexity is not too high, maybe it can start rescan from previous stopping point? (Also one could click “rescan” text but actually had to go in the menu to activate it. Maybe make it not clickable or launch the rescan on click?)
during the rescan the Messages/Notes/History tabs are empty even though the balance is shown. Maybe there could be a note there saying that these will be available after rescan is finished.
I love the UX and am especially pleased to see the multi-send feature: it is always hard to onboard people at the dinner because you need to do manual zUTXO management beforehand, lest you send one person some ZEC and then need to wait minutes until your change zUTXO confirms.
@hanh just hopped on the bandwagon and downloaded YWallet. It’s pretty nice. I like that little tilt/accelerometer thing you do to toggle the visibility for the balance.
Not a diss on YCash, but I always thought it was a YCash only wallet, which is why I never used it until now. I think this will be my new default.
Our short-term focus for the SDKs is full NU5 support (UAs, Orchard). We are prioritizing a faster syncing option as well as general SDK hardening (improved error handling, etc) next in the roadmap.
Internally, YWallet uses height but I think it’s harder to remember than an approximate date. This still could be added in the future though.
That’s a bug. It should be clickable. The block height on the account page is clickable and initiates a sync/catch-up. It is triggered by a timer too.
You could also create a bunch of small notes beforehand with the “Max amount per note” feature.
But indeed, multi-pay is designed for your type of scenario.
Wanted to add to this thread a new issue with ZEC UX. For the past 4 days I have been trying to access my ZEC on my Ledger wallet but am unable to send or swap, giving me the following error:
Now I know that I ought to reach out to Ledger support, someone else already did and was told that it was being worked on, however I wanted to explicitly post this here as well. I’m not concerned as I am confident that it will be accessible at some point in time AND simultaneously I am losing confidence if this is to drive real world adoption at scale.
Just imagine the countless first time users that have no clue about what to expect only to find that their funds are unaccessible due to some unexplainable reason. Unacceptable.
In the past 4 days there where multiple occasions where I wanted to use my ZEC to make purchases and or swap. Not being able to do so feels like a huge let down and results in me losing the freedom to seize opportunities.
Hopefully my concerns are registered by those responsible for driving mass adoption. Despite this being a Ledger issue it is ultimately ZEC that is unaccessible.
@brocktakeshi, I can confirm Ledger ZEC spends are working at least as of yesterday. Is there an update to the Zcash app under Ledger manager?
But I agree with the sentiment. It seems ecosystem partners need a lot more hand-holding during network upgrades. For instance, SideShift.ai has had all ZEC trades disabled since NU5. Are they being worked with to get up and running again?
All the wallets are broken. Even ywallet doesnt sync now for me, lightwalletd is broken… Is anyone from ECC or ZF doing anything about it? Cough… cough… dev fund… Are there any devs??? Hello?
We (ECC core team) have spent the past three weeks (including over most of the holiday weekend last week) working almost exclusively on the performance problems. Here are all the places you can see what we’ve been doing:
I think I saw a message from @joshs somewhere recently mentioning that for him to get it working he had to ensure he had the latest firmware and then uninstall and reinstall both the Bitcoin and Zcash apps on the Ledger. Might be worth a try…
Question about mobile wallets: https://github.com/zcash/zcash/pull/6069 should improve sync performance on full nodes. @hanh I wonder if a similar improvement could be implemented in Warp sync? @adityapk00 Blaze sync probably doesn’t need this as this does scanning in the reverse order?
I wanted to quickly point out some things that are causing performance issues specifically with Zecwallet, and our current plan to fix these.
My expectation was that Zcash blocks will full up slowly over time, allowing us enough time to adapt to growing blocks and design better algorithms. However, Zcash blocks have suddenly become full, and we’ve been caught offside
For Zecwallet, specifically:
LightwalletD now has to serve several 100s of GB of data everyday.
This is because blocks are full, and each lightclient downloads ~80 bytes per output, causing a 100x increase in bandwidth used by LightwalletD. Additionally, each mobile client has to download ~1GB of data everyday, which can be difficult if you’re over a cell connection
Memory usage.
Zecwallet caches a lot of stuff in memory to improve latency, and while this was fine up until now, with the full blocks, memory requirements have suddenly 10x’ed, which is causing low-end phones to run out of memory and crash. We need to tune some of our sync strategy here to deal with persistently large blocks that may use lots of memory
Updating witnesses and verifying blocks
Zecwallet verifies everything LightwalletD sends, so it calculates the state roots for every block. With these large transactions that have 1000s of outputs, this is slow. Additionally, this has to be done serially (single threaded) which is making it very slow.
To be sure, all these issues are somewhat fixable, but they’ll take some time for us to work through. We plan to address them in upcoming releases.
Would you ever consider merging your efforts with another wallet (e.g. @hanh’s YWallet)? Obviously that would imply both sides are open to doing such a thing.
Feels like a lot of the wallet devs are just solving the same issues independently. If ECC and ZFND can centralize their efforts, why can’t the dev community?
Starting from version 1.2.9, it also implements checkpoints (per your suggestion) to allow resuming the sync if you close the app.
And variable block chunk length to handle the surge of transaction outputs better.
No guarantees; but, at the moment 
).
