@hanh at the most recent meeting, the @ZcashGrants Committee voted to approve this proposal.
The nodes are still running: https://status.zcash-infra.com/
Hanh what is your timeline for updating Zebra? Hosh: Light Wallet Server Status
Hi Hanh - these servers have been offline for a few days. When can the community expect them to return? Thanks.
lwd1.zcash-infra.com:9067
lwd2.zcash-infra.com:9067
lwd3.zcash-infra.com:9067
lwd4.zcash-infra.com:9067
lwd5.zcash-infra.com:9067
lwd6.zcash-infra.com:9067
lwd7.zcash-infra.com:9067
lwd8.zcash-infra.com:9067
Zebra keeps crashing on
Apr 12 23:47:38 zebra2.zcash-infra.com zebrad[1239577]: The application panicked (crashed).
Apr 12 23:47:38 zebra2.zcash-infra.com zebrad[1239577]: Message: response json should have an id
Apr 12 23:47:38 zebra2.zcash-infra.com zebrad[1239577]: Location: zebra-rpc/src/server/rpc_call_compatibility.r>
Apr 12 23:47:38 zebra2.zcash-infra.com zebrad[1239577]: Metadata:
Apr 12 23:47:38 zebra2.zcash-infra.com zebrad[1239577]: version: 2.2.0
Apr 12 23:47:38 zebra2.zcash-infra.com zebrad[1239577]: Zcash network: Mainnet
Apr 12 23:47:38 zebra2.zcash-infra.com zebrad[1239577]: running state version: 26.0.0
Apr 12 23:47:38 zebra2.zcash-infra.com zebrad[1239577]: initial disk state version: 26.0.0
Apr 12 23:47:38 zebra2.zcash-infra.com zebrad[1239577]: features: default,getblocktemplate_rpcs,howudoin,indica>
Apr 12 23:47:38 zebra2.zcash-infra.com zebrad[1239577]: branch: HEAD
Apr 12 23:47:38 zebra2.zcash-infra.com zebrad[1239577]: git commit: 6d01f05
Apr 12 23:47:38 zebra2.zcash-infra.com zebrad[1239577]: commit timestamp: 2025-02-04T16:50:10.000000000Z
Apr 12 23:47:38 zebra2.zcash-infra.com zebrad[1239577]: target triple: x86_64-unknown-linux-gnu
Apr 12 23:47:38 zebra2.zcash-infra.com zebrad[1239577]: rust compiler: 1.82.0
Apr 12 23:47:38 zebra2.zcash-infra.com zebrad[1239577]: rust release date: 2024-10-15
Apr 12 23:47:38 zebra2.zcash-infra.com zebrad[1239577]: optimization level: 3
Apr 12 23:47:38 zebra2.zcash-infra.com zebrad[1239577]: debug checks: false
It’s a known issue and is fixed in main.
I’ll wait for the next official release.
I am aware of the issue. I am who reported it. All of the Zec.rocks servers have maintained uptime despite the issue.
Can you please bring your servers back online? The community paid for them, it’s extremely unprofessional to keep them offline while waiting for a release.
Zcash light wallet users (I’d say 99% of users) have been 100% centralized on Zec.rocks servers for over 2 weeks due to you not being willing to even try to fix your servers. Please fix the problem like we did. For us it was a matter of re-syncing the blockchain if I recall. Or at least run Zaino if LWD is crashing.
Anything is better than downtime. This is extremely unprofessional.
I literally do this for free (just pay for the hosting at 6 000 USD per year), with the explicit condition that support is provided to the best of my time.
Your grant is 45 000 USD, isn’t it?
This reminds me that I won’t renew.
It was, that was for one year of hosting and to write infrastructure code which anyone can use, it completed months ago. We currently run the servers because we love Zcash.
Great to hear! We need team players.
dont worry. there is talks with a new player taking over hanh’s servers.
Zebra 2.3.0 is now out. Perhaps that will make a difference?
it should fix the bug. lets hope @hanh updates soon
Yes, hopefully the latest Zebra release should fix it.
BTW this is why I insisted on a continuity plan
Yup, I only have the domain for 2 years.
If you’re not going to renew then please transfer the domain to someone interested (I guess probably @emersonian ) 
I think anyone can just buy it after (or if someone wants it, I’ll transfer through the registrar).
Yes, I think there should be a condition on @ZCG that if a developer uses a domain to fulfill that grant and later decides to discontinue for whatever reason then the domain should be transferred to the Zcash Foundation for future use.
This could eliminate confusion with someone else taking the project over, or allow redirects to better resources for discontinued projects (such as ZecWallet).
I disagree. That would concentrate more power towards ZF; avoid power concentrations at all costs. Wallets should get better at detecting RPC that are down and handle them appropriately.
I would gladly run one of those lightwalled for free, and I believe many more people would do the same, on a best effort basis. It would be much cheaper and would give us more resilience, and it will be obvious in retrospect once we start doing it.
That aside, I’d like to explore hosting one on Tor. Anyone doing this?
It may not be a big deal in this case because it’s just backend services for wallets, but in the case of ZecWallet, Nighthawk, etc… would it be better for the developer who left to hang onto the domain and let it rot, eventually expire and allow some squatter take it over only to a upload a malicious version of the wallet to steal user funds?
Google still likes those old domains due to hundreds of links. We need a better plan for what happens to them when the project completes, if not ZF then ZecHub, FPF.
If no one else steps up I’d like to take them. It’s tricky to buy it after it expires because the exact time expired domains become buyable again is not clear and someone else (possibly malicious) might beat us to it.