A week ago, when I deployed the test version, I imported all the nodes from Hosh. However, there may already be new ones, so you can easily add your own nodes using the website or the Telegram Mini App.
You can view detailed check results and downtime statistics, and export them to CSV (in case someone needs that ).
You can also subscribe to node status change notifications — if any issue occurs, you’ll be able to react quickly and bring your node back online.
The Top 50 statistics are still being collected during the first month, so they will become more meaningful starting next month.
If you find any bugs or have feature requests, don’t hesitate to contact me!
I’m excited to announce that I’ve launched a new Lightwalletd node for the Zcash mainnet. This server is publicly available for anyone to use with their light wallets.
Node Information:
Version: v0.4.18-25-g6a173e6
Current Block: 3,205,744
Vendor: ECC LightWalletD
Transparent address (t-addr) support: Yes
Network: mainnet
Sapling activation height: 419,200
Latest Zebra confirmation: v3.1.0+5
Available Endpoint:
z3.deepikaw.xyz:443
Features:
Fully synchronized with mainnet
Compatible with mobile and desktop wallets using Lightwalletd protocol
Supports both transparent and shielded addresses
Running the latest ECC software
Goal:
To contribute to Zcash infrastructure decentralization and provide a reliable endpoint for light wallet users.
I remind you, that you can add nodes there by yourselves by pressing “Add Node” button in the header.
Also, subscribe for node status change notifications and it will help you to maintain your node online and fix issues ASAP.
Important reminder, Nodus does not accept nodes without SSL. I think that the privacy should be private
@emersonian My node is constantly jumping from online to offline and back.
I’m checking it each time and it’s working. It’s definitely the issues on your checking server.
Also, I added my node to Nodus and there’s still NO bad checks and it’s online.
Please, check your server, because I think that these indicators are not objective and because of this the real indicator of my uptime is distorted.
keep having issue posting the server address, says no links allowed.
lwd.lightwallet.zecfiorg:9067 (remove the and replce.
Donation address should be broadcasted (Orchard UA):
u1t720vu9cs6ztp59cspq56un2dspt2eu0l2mepuyc2xqckptusyavlkjwglzs542ha8tzn588x9hfpe8d5wercjh4xyng0y4gawc4ge9musqj6at36ukfm5ensdc30uhpucetrpveywksf55fmm75aww9jwpsnjgqzhgq44hwrc6kcfxp
39 operators qualified for the January 2026 reward, receiving $300 each (0.724 ZEC) for a total of 28.236 ZEC. Operators with multiple hostnames received the reward once.
LetsEncrypt just announced the availability of IP address SSL certificates (without a domain) - that might be of interest to some node operators. This means that operating a Zcash light wallet node no longer requires purchasing or owning a domain name, as is the case for Tor operators.
If you have a server you would like to be included, please respond here after making sure that your Zcash wallet is able to connect to it, we recommend using Zashi, Zingo, or Ywallet to test. Placing a pull request on the Hosh Github repository is another way to get quickly included.
Kind regards, 0/ I don’t understand why I don’t appear on the list, even though there are still 11 operators needed to complete the 50 operators who will receive rewards for this month. I am attaching all the evidence that I have had everything up to date for some time now.
I don’t see transparency here. My node has almost 800 checks difference with the first one and has been registered since November. On the 28th, 29th, and 30th of December, the page was down. I don’t know if something happened with the checks during that time.
@emersonian Should we be using port 443 for TLS enabled daemons? The default compose in zecrocks/zcash-stack/docker uses 9067, but I noticed in the docs that the connect page shows grpcurl commands that are sent to 443 while the one using 9067 has a comment saying it’s for insecure/non-TLS daemons. My daemon uses a sectigo issued certificate, but grpc is currently on 9067.
Just in case my last message got lost in the other replies, please include my node (lwd.forzcash.online:9067) in the next node list update. Zebra is fully synced with the blockchain and lightwalletd is responding correctly.
I also forgot to mention in my last reply that I seem to have an issue with watchtower. I’m getting a “Error response from daemon: client version 1.25 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version“ error message, so I’ve stopped that container for now.
I might think the measurement has changed a lot. I see this because my node has gone down several times for hours, for example, 6 hours, and its score dropped to 3 points, but in that same timeframe, the node’s availability doesn’t increase as quickly. So, I think there are some unclear conditions, such as simply pinging the node’s IP address or domain.
Website: https://nodus.alexxiy.top
Telegram Mini App / Bot: https://t.me/zec_nodus_bot (or just @zec_nodus_bot in Telegram)
).
Node Information:
Available Endpoint:
Features:
Goal:
Technical Details:
