Even though I’m not eligible for the rewards of this months because I’ve started my node less than a month ago, I would like to thank you for this opportunity and hope I’ll take care of my node and hope to get my reward next month 
1 Like
I want to know if the latest versions that the node should have also include the RC versions, since these versions are unstable for node production.
-
So, the most recent software is Zaino. Do we have to migrate, or can we continue using lighwalletd according to each participant’s preferences?
-
If there are cases like the one we are seeing, where people have not received payment because they are within the range of those selected, how can they be sure that they have received the corresponding payment?
Hello everyone, first of all, thanks to my dear @Blakiat for the support and guidance with the configuration. I wanted to announce that the node is now running at zec.topacio.trade:443. I would like to support and be part of the event. I also had a question: is there currently any portal like UptimeRobot to monitor the availability of the nodes?
3 Likes
Hi, Happy because we were able to install the first node.manyrz.xyz:443. Looking forward to registering three more friends to contribute to the network. Keep it up, and thanks for making privacy normal!. Thanks
3 Likes
are you using ywallet ? you gotta rescan from block 3170000
Good day, I have just configured my Zcash node (znodo.edgarlenon.xyz:443)
I am happy to announce it and there by contribute to the security of such a noble network.
4 Likes
Hey is this still going on?
How do i run one?
Seems that my Raspberry Pi died last night, I believe the SSD ended up corrupted or something that the OS does not boot anymore. It actually did way better than I initially expected, and ran as a Zcash full node for a few months, so happy that it died doing what matters to the world
This was a great initiative and I’m happy to be one of the early ones here. Seeing the number of community nodes now (comparing to 20 when we started) I think my work here is done and I can rest easy knowing that people are running the nodes on much better machines than my tiny raspberry pi from home.
Thanks for everyone making this happen and hope to see you soon <3
2 Likes
Curious of your setup 
, that is not normal behavior my pi’s have been running for years with both zcashd/zebrad. ( can DM if you want )
1 Like
I have a Raspberry Pi 5 with 500 GB microSSD. There were a few power outages in my building last week, my guess is that something went wrong there (gotta get that UPS one day).
Currently I’m traveling and cannot SSH into the machine, even after asking my family to do a few power cycles. I can check next month when I have physical access to see what is going on there.
Update: Server seems to be back up currently, still no SSH access but I can see my Zcash node running
1 Like
We’ve updated how 30-day uptime is calculated on the Hosh monitoring dashboard. This change provides a fairer representation of server reliability while accounting for how long each server has been tracked.
What Changed
Previous calculation:
- Uptime was calculated as
successful checks / max checks across all servers - This compared every server against whichever server had the most checks in the 30-day period
- Servers that were offline or unreachable for periods received fewer total checks, which may have penalized them twice: once for the failed checks, and again for having fewer checks than the most-active server
New calculation:
- Uptime is now calculated as
(successful checks / server's own total checks) × (days announced / 30) - The “days announced” factor is capped at 30 days
What This Means
The new formula has two components:
- Success rate - What percentage of checks succeeded out of the checks performed against this specific server
- Time factor - How much of the 30-day window the server has been known to the monitoring system
| Server Age | Maximum Possible Uptime |
|---|---|
| 1 day | 3.33% |
| 7 days | 23.33% |
| 15 days | 50% |
| 30+ days | 100% |
The new approach:
- Evaluates each server independently based on its own check history
- Prevents newly announced servers from immediately achieving high uptime scores
- Rewards consistent, long-term availability
Impact on Existing Servers
- Servers tracked for 30+ days with high success rates may see their uptime scores increase (no longer penalized by comparison to other servers)
- Newer servers will see lower uptime percentages until they reach the 30-day threshold
- ZEC and BTC now use identical uptime calculations
Thank you for participating and we hope you have a great holiday week.
5 Likes
Hi, some days ago I setup my nodes (the zebra node is the same for both):
-
z.ombie.cash:443(zebra+zaino) -
l.ombie.cash:443(zebra+lightwalletd)
Here is my donation address: https://zcash.me/zombiecash
I’ve already opened a MR: feat: add zombiecash nodes by jenkin · Pull Request #65 · zecrocks/hosh · GitHub
Thanks for the documentation!
1 Like
done syncing, using zebrad 3.1.0 and lightwalletd 0.4.18
1 Like
Done syncing, and running Zebra 3.1.0 + lightwalletd v0.4.18.
I can’t send links, but it’s:
https:// zecdolprice. uk:443 (without the gaps!)
Please let me know if there are any issues
1 Like
Not heard anything or been added, is there someone specific I should reach out to?
zecdolprice. uk:443
1 Like
Quick UI problem on the leaderboard, It says it shows top 50 server but only top 44 are shown.
1 Like
please add
ivlf2z6aksfi7h5yx2bs3osuppb2g3v5l7okdcvyo7yz3ghi7byw7ryd.onion:443
1 Like
Zebra 3.1.0 + LWD
rqjlg3q7qul4i7ha2je3b4trp4o2xex5kwpxuzw75cltizyiwkh6s4ad.onion:443
1 Like
To qualify for the reward on January 15th, operators must be running:
- zebra 3.1.0
- lightwalletd 0.4.18 or any version of zaino
The new leaderboard on Hosh only shows servers that are running these versions.
Servers updated, thank you for participating.
If your server is not appearing, note that it must pass one check to be added to the list. Try connecting to your server using a Zcash wallet to verify that it is working, or try pinging it with zecping.
3 Likes
done! zebra 3.1, lightwallet 0.4.18
tridbhm5oogy6k55mwcs4gvkewoewrxlzhyez55fkor2d5py3jhfomyd.onion:9067