zcashd is the original full node software for the Zcash network, aimed at developers, node operators and privacy-minded users who want to verify the chain themselves instead of trusting a remote server. It is open source and free to obtain.
Before you go further, understand its status: the project has reached End of Life, so it no longer receives active development, and the Zcash project points users toward newer node software such as Zebra and the Zallet wallet. This page explains what zcashd does, how the ready-made program is typically installed on Windows, and what to consider when comparing it with other full nodes. Because node software can connect to wallet functions, the safety notes matter as much as the feature list.
What Is a Zcash Full Node?
A full node is a program that downloads and checks the entire history of a blockchain. Instead of trusting a website or a remote server to report balances and transaction status, the node applies the network's rules to every block it receives. If a block breaks those rules, the node rejects it.
Zcash supports shielded transactions, where the sender, receiver and amount can be hidden from public view. Nodes still have to validate those transactions, which is part of why running one is more involved than running a simple client. A node must confirm that the cryptographic proofs are valid without learning more than the protocol reveals.
For most people, a full node is not the easiest way to use a cryptocurrency. It is the way to check the chain yourself. Wallets that connect to a full node generally give you more independence than wallets that ask a third-party server for information, though they also take more time, disk space and attention to set up.
Who Is zcashd For?
zcashd was built as the reference Zcash consensus node, so its natural audience is people who need to see how the network is supposed to behave. Developers who build wallets, block explorers or exchange integrations often run a node to test their software against real chain data. Researchers who study the protocol may also want a reference implementation to compare against other software.
Node operators form another group. Running a node on a machine that stays online helps the network stay decentralized, because more independent copies of the chain are harder to switch off or censor. Operators who keep a node running for the long term should pay close attention to the project's support status.
zcashd is not a good fit for someone looking for a simple app to send ZEC from a phone. It is a node first, not a consumer application. Because the project has reached End of Life, anyone starting a new project should look at the successor software the project recommends rather than building on zcashd. Users who only want to hold coins are usually better served by a dedicated wallet.
How Full Nodes Verify the Blockchain
When a node starts for the first time, it connects to peers on the network and begins downloading blocks. Each block is checked against consensus rules: its structure, its proof of work, the validity of each transaction, and whether it builds correctly on the chain the node already knows. Only blocks that pass every check become part of the node's local view.
This process is why initial synchronization takes time. A node must process the full history, not just the latest state. Storage needs grow as the chain grows, so free disk space and a stable internet connection make a noticeable difference during the first sync.
Once synced, the node relays valid blocks and transactions to peers and keeps watch for new blocks. If it sees a competing chain with more accumulated work, it reorganizes its view to follow that chain. Understanding these basics helps you read node logs and judge sync progress without worrying about every message.
Key features
Full consensus validation
Reference implementation
Open source code on GitHub
Supported coins
The project documentation names Bitcoin (BTC) and Zcash (ZEC), and it mentions Ledger hardware wallets alongside the software. In practice, zcashd is a node for the Zcash network, so ZEC is the asset most readers will care about.
How to install Zcash (zcashd) on Windows
- 1
Get the file from an official source
Download only from the official website or the project's GitHub Releases page at github.com/zcash/zcash. Avoid mirrors, torrent links and forum posts offering pre-built binaries.
- 2
Check the SHA-256 checksum or signature
Compare the file's SHA-256 hash against the value published with the release, or verify the signature if one is provided. A mismatch means the file should not be installed, and you should download it again from the official source.
- 3
Confirm the Windows build in the release
Windows builds are noted for this project, but the Releases page is the authoritative list of what is currently offered. Look through the assets on the latest release for a Windows archive or installer. If none is listed, do not try to repurpose a build from another source.
-
Extract or run the installer and start the node
Run the installer or extract the archive into a folder of your choice, then start the node from a terminal. The first block synchronization can take a long time and needs substantial free disk space, so plan for both before you begin.
How to use Zcash (zcashd)
Running zcashd is a matter of starting the node, letting it synchronize, and keeping it connected. The steps below assume you have already verified and installed the program.
- Open a terminal in the folder where zcashd is installed and start the node.
- Let the initial block synchronization finish before relying on any balance or transaction data it reports.
- Review the configuration options in the documentation so the data directory and network settings match your setup.
- Keep the machine online and the node running so it can stay in step with the network.
- Monitor the logs for errors, peer connections and sync progress during the first days.
- Read the project's migration guidance on Zebra and Zallet before deciding how long to keep using zcashd.
Pros & cons
- Free and open source, with the code publicly available on GitHub
- Serves as the original reference implementation for the Zcash network
- Lets you validate the chain yourself rather than trusting a remote server
- Project documentation includes an official migration path to newer software
- End of Life status means no further active development
- The project lists Linux as its main platform, and Windows support is not a firm promise
- Full node synchronization is resource-heavy, with a long initial download
- Not suited to first-time users who only want a simple wallet
Is Zcash (zcashd) safe?
zcashd has reached End of Life, so the project no longer ships regular updates, including security fixes. Running unsupported software that can touch a wallet or keys carries more risk the longer it stays in use. Download the file only from the official website or the GitHub Releases page for the zcash repository, and never from forum links or unofficial mirrors. Compare the SHA-256 checksum of the downloaded file with the value published with the release, or verify the project signature where one is provided. Never enter a seed phrase on any third-party website, and treat any site that asks for one as a scam. If your goal is ongoing use, plan a move to supported software.
- Official source only. Download from github.com/zcash/zcash. Ignore ads and lookalike domains.
- Check the SHA-256. Compare the installer hash with the value the developer publishes before running it.
- Never share your seed phrase. No developer, support agent or website — including CryptApps — will ever ask for it.
Alternatives
zcashd and the other programs in this category are all full nodes, but each one serves a different chain. Litecoin Core and Dogecoin Core run nodes for their own networks. Monero CLI is a daemon and console wallet for Monero, a privacy-focused network with its own design. Komodo Core, Namecoin Core, Qtum Core, Syscoin Core and KatKoyn Core likewise follow their own protocols. If your goal is Zcash specifically, zcashd is the original reference node, but its End of Life status points the choice toward Zebra instead. Compare release dates and support status on each project page before you commit.
Specifications
- Price
- Free
- Type
- Open source
- License
- —
- Latest version
- v6.20.0
- Last update
- 19 Jul 2026
- Windows support
- Likely (builds for Windows; check releases)
- Source code
- github.com/zcash/zcash
Frequently asked questions
No. The project has reached End of Life, which means it no longer receives active development. Recent code activity in the repository does not change that status, so the official End of Life notice is the figure to rely on when judging long-term support.
The project lists Linux as its main platform and notes that Windows builds exist. Check the assets on the latest GitHub release to see whether a Windows archive or installer is offered before you plan your setup.
It can be, if you take basic precautions. Download only from the official GitHub Releases page, verify the SHA-256 checksum or signature, and keep in mind that End of Life software no longer receives security fixes.
The Zcash project points users toward Zebra for node software and Zallet for wallet functions. Review each project's documentation and support status to decide which fits your use case.
No. Many people use Zcash through lightweight wallets that do not store the full chain. Running a full node gives you independent validation, but it requires more storage, time and maintenance than most casual users want.
The project documentation mentions Ledger hardware wallets. Read the documentation carefully to understand how any hardware wallet connects before relying on that setup for your funds.
Verdict
zcashd is historically important and open source, but it has reached End of Life. It suits people who want to study how a reference Zcash node works, read its code, or compare behavior while developing tools. It is a poor choice for a new production node or a first wallet. If you are evaluating Zcash node software today, check the latest version on the official website and read the project's migration guidance on Zebra and Zallet before you commit.