Hello, good day. I’m relatively new to cryptocurrencies and I’m trying to contribute to projects that I believe have potential, like Zcash. I don’t have a large investment capital, and I can’t deny that the rewards for running a node are motivating. I’ve been running it since mid-December and haven’t received a single dollar. I was thinking of continuing if USDT drops a bit so I can keep paying to maintain the active node. Thank you very much for your attention, and have a great day.
Still no update? 
Hi everyone - apologies for the delay here. We discovered a potential critical security issue and decided to pause payouts while we investigated. We have completed the investigation, everything is fine and our reward funds are safe in a new wallet. We will publish the new UFVK shortly.
Here is what we discovered, it was our own mistake and not a problem with Zcash itself in any way: Security Disclosure: Zec.rocks snapshots of zcashd included wallet keys
We are processing reward payments within the next few hours and will post here once they are completed. Thank you for your patience, we wanted to be extremely cautious with the reward funding until we figured out exactly what was going on.
Thank you for participating!
6 Likes
February 2026 Rewards
50 nodes qualified for the February 2026 reward, receiving $300 each (1.172 ZEC) for a total of 58.6 ZEC. Operators with multiple hostnames received the reward once.
| Server | Version | Uptime | Ping |
|---|---|---|---|
| api-zec.noderoller.cloud:9067 | Zebra:4.1.0 | 99.97965% | 504ms |
| chmodas.org:443 | Zebra:4.1.0 | 99.96888% | 409ms |
| donatemezecfor.beer:443 | Zebra:4.1.0 | 99.95865% | 434ms |
| light.myown.party:443 | Zebra:4.1.0 | 99.95989% | 583ms |
| light.tracier.space:443 | Zebra:4.1.0 | 99.98979% | 602ms |
| lightapi.justneedto.click:9067 | Zebra:4.1.0 | 99.97929% | 507ms |
| lightwallet.online:443 | Zebra:4.1.0 | 99.96870% | 442ms |
| ltwallet.netter.top:9067 | Zebra:4.1.0 | 99.97323% | 1574ms |
| lw.chponks.site:443 | Zebra:4.1.0 | 99.92568% | 571ms |
| lwal.podev.name:9067 | Zebra:4.1.0 | 99.96790% | 429ms |
| lwd.z0n.jp:443 | Zebra:4.1.0 | 100.00000% | 498ms |
| lwz.ourwork.shop:443 | Zebra:4.1.0 | 100.00000% | 441ms |
| lwzec.formers.sbs:443 | Zebra:4.1.0 | 99.97807% | 583ms |
| myzec.cryptover.site:443 | Zebra:4.1.0 | 99.94578% | 533ms |
| node.manyrz.xyz:443 | Zebra:4.1.0 | 100.00000% | 125ms |
| node.zecwhales.online:443 | Zebra:4.1.0 | 100.00000% | 500ms |
| sn-hub.de:9067 | Zebra:4.1.0 | 99.97787% | 389ms |
| w.optiontec.cfd:443 | Zebra:4.1.0 | 100.00000% | 431ms |
| webhighway.website:443 | Zebra:4.1.0 | 100.00000% | 467ms |
| z.arounder.co:9067 | Zebra:4.1.0 | 99.97843% | 526ms |
| z.devels.club:443 | Zebra:4.1.0 | 99.92208% | 505ms |
| z.miscthings.casa:9067 | Zebra:4.1.0 | 99.97735% | 430ms |
| z.netgates.xyz:443 | Zebra:4.1.0 | 99.83712% | 722ms |
| z.networkx.icu:443 | Zebra:4.1.0 | 99.98874% | 522ms |
| zaino.netstable.stream:443 | Zebra:4.1.0 | 100.00000% | 397ms |
| zc.craftor.website:9067 | Zebra:4.1.0 | 99.96711% | 529ms |
| zc.nettools.uno:443 | Zebra:4.1.0 | 99.96675% | 628ms |
| zc.verson.store:443 | Zebra:4.1.0 | 99.98866% | 466ms |
| zcash.johndo.men:443 | Zebra:4.1.0 | 99.96555% | 584ms |
| zcash.monster:443 | Zebra:4.1.0 | 99.98861% | 610ms |
| zcashlw.devshore.ovh:443 | Zebra:4.1.0 | 99.95558% | 618ms |
| zcashrpc.work:443 | Zebra:4.1.0 | 99.89821% | 539ms |
| zcashwalletapi.fun:443 | Zebra:4.1.0 | 99.87826% | 649ms |
| zec.alexxiy.top:9067 | Zebra:4.1.0 | 99.98918% | 559ms |
| zec.visionx.bond:9067 | Zebra:4.1.0 | 100.00000% | 435ms |
| zecapi.linkpc.net:443 | Zebra:4.1.0 | 99.97832% | 900ms |
| zecapi.online:443 | Zebra:4.1.0 | 99.96675% | 514ms |
| zeclight.lol:443 | Zebra:4.1.0 | 99.94530% | 583ms |
| zeclight.renfa.skin:9067 | Zebra:4.1.0 | 99.92178% | 532ms |
| zeclwnode.mylabtest.vip:9067 | Zebra:4.1.0 | 99.94514% | 595ms |
| zecnode.sarl:443 | Zebra:4.1.0 | 99.97752% | 530ms |
| zecrpc.dpdns.org:443 | Zebra:4.1.0 | 99.94362% | 433ms |
| zecw.newfactor.biz:443 | Zebra:4.1.0 | 99.90198% | 654ms |
| zecwal.sandycat.cc:443 | Zebra:4.1.0 | 100.00000% | 458ms |
| zlw.nodemaster.link:9067 | Zebra:4.1.0 | 99.98965% | 1849ms |
| znode.roamerx.win:443 | Zebra:4.1.0 | 99.97689% | 411ms |
| znodo.edgarlenon.xyz:443 | Zebra:4.0.0 | 100.00000% | 234ms |
| zw.run.place:443 | Zebra:4.1.0 | 100.00000% | 463ms |
| zwallet.techly.fyi:443 | Zebra:4.1.0 | 100.00000% | 604ms |
| zzz.stripest.online:443 | Zebra:4.1.0 | 100.00000% | 593ms |
TXID: 36cb8d981985fbfc5c5eb72346f75b141e2efdb7d2c343f094765976ece68068
Wallet Rotation
Payouts were delayed this month in an abundance of caution when we detected unusual wallet activity. Due to the discovered security issue, we have rotated to a new wallet.
For continued transparency, here is the view key which allows you to watch our payouts from the new wallet:
uview1epqsm6445vq38qwmuhjhn9vrs549vfzyvu2mzxpwe4tugq3klmewpmka89lh8u29j0ksykkvxk54uccmuvh9mk6dxkq5k6rxl7c5sdk8m4pp7257vl7kc7mfxfavsth0u0pgg33mkulz6qakf2ffd4aw4hl7w6933nn70dh2x7ek02f2dpwyvptfx8amqgq3jm5guhalyjlwqmlfk9mscf82taerpqt348ttn32sev2epjcvwa5mm8jy5282ywvn3h25jlgt3ufg6ywn8epcjspe3ulq7gyd6zgrr085qgznqudu6dy50hwyrgtv90r977ezpyrmjr89qtglxren3rak9jg7nz6r3n8snc27s9judmh2mxfdzy5gulmaqke4w6tlqks2csw4q
Birthday: 3253000
To watch payouts live, try out our new Zcash block explorer! It is a work in progress, but we would love your feedback on it. It’s the first Zcash block explorer that fully supports view keys:
Prepare to upgrade your servers
We will announce new node version requirements within the coming week, please continue to keep your nodes updated.
Thank you for your patience with us this month as we delayed payouts to investigate the security issues. We are no longer using zcashd anywhere in our payments stack whatsoever.
Let’s keep growing the Zcash network!
4 Likes
Hello emersonian; I have checked Hosh: Zcash Light Wallet Uptime and couldn’t find my node listed. Is there any other procedure to undertake before a node to be added to the list? If yes then kindly direct me; and if not, please here’s when I requested it Zcash Operators: Earn ZEC for your uptime - #231 by speedfox
Hola, superadas algunas cuestiones nuevamente en linea.
Dejo esto por aca tambien:
Here’s my node, latest software, now syncing. Please add
eto-volosy.hair:443
I have been waiting for about 2 months now to see if the end of the month would fix it. There is an issue with the calculations reflected on the monitoring portal, specifically with the ‘Last 7 Days’ and ‘failed over past 30 days’ fields. My node has been active since December 30th, and since January when I updated to Zebra version 4, it still shows 11 error marks even though that happened in January. This is even affecting the average of the last 7 days when it has actually been at 100%. And now, at this point in March, why is January data still being reflected in the last 30 days when it has really been at 100%? The only time I paused it for a brief moment while doing the update was in January, and it has been reflecting the January data even in these 2 new months where it has been 100% operational. My node is zec.topacio.trade:443
Hi!
You also can take a look at your node on Nodus
Your downtime history (select 30d range for the last 30 days):
Nodus calculations is a little bit different and based only on downtime, not on check count.
Your node on Nodus 30d uptime: 99.892%, on Hosh: 99.87945% which is +/- near.
It doesn’t matter if your node is 100% uptime (as mine and as anyone’s as well). If checker couldn’t reach your node it’s assumed as down.
I made a script which checks my node state on Hosh and if it’s down, I recheck from my location right away and my check always shows that the node is okay. This is the issues on the server’s network and intermediate providers which are on the path to your node from Hosh server.
Today I applied some fixes on Nodus which should significantly decrease “false down” checks. And in the future I’ll add checkers from different locations, so node will be considered down only when all checkers in multiple locations can’t reach it.
I can improve the top50 list on Nodus, but @emersonian hasn’t shared me the right algo yet. Of course, I can take a look on Hosh’s git, but I it’s better to me get real conditions and do it from the scratch to avoid “copying” any bugs from one code to another (if they are there).
2 Likes
Node location is very important, checks from multiple sources would be a game changer.
For example my (exit) node is in Germany and I see a latency of 150 ms in Nodus, but 500 in Hosh. Probably some checks from Hosh fail also because of timeouts.