Provenance node is the Windows-ready client for running a full node on the Provenance Blockchain, a proof-of-stake network built for financial services. It suits developers, infrastructure operators and technically minded users who want to join the network or study how it works. The software is distributed as the provenanced daemon, the core application that keeps a node in sync with the chain.
Provenance node for Windows is free and released under the Apache 2.0 license. The code is written in Go and available as a Windows build or installer, so you do not need to compile it yourself. The current listed release is v1.31.0-rc1, a release candidate, which is worth remembering before you put a node into production. The source is public on GitHub, so anyone can review the code and its changes.
What Is a Provenance Node, Exactly?
A node is a program that runs on your computer and talks to other computers in a blockchain network. It downloads blocks, checks that they follow the network rules and relays transactions to its peers. Running one means your machine holds its own copy of the ledger instead of trusting someone else's view of it.
In the Provenance ecosystem, the provenanced daemon plays this role. It handles the networking, storage and rule checks that keep the node aligned with the chain. When people say they are running a Provenance node, they usually mean this background process, not a graphical app with buttons for sending coins.
That distinction matters when you plan your setup. A node needs steady network access and disk space, and it works best as a service you leave running, not a program you open only when you need it.
How Proof-of-Stake Shapes Network Participation
In a proof-of-stake network, participants lock up tokens as a form of commitment, and the protocol uses that stake to decide who proposes and confirms blocks. This replaces the hardware race found in proof-of-work systems, where miners compete with computing power and electricity.
Not every node takes part in consensus. Some nodes only follow the chain and answer queries, while others take on validation duties that come with the stake requirements of the network. Knowing which role you want before you start helps you pick the right configuration.
Because the rules are set by protocol, a node operator's job is mostly to keep the software current, keep the clock accurate and protect any keys involved. The consensus logic itself is handled by the software, so you do not tune it by hand.
Practical Use Cases for a Windows Node
Developers often run a node to test applications against a real network without depending on a public endpoint that may be rate-limited or unavailable. A local node gives you a predictable place to send requests while building and debugging.
Analysts and researchers use nodes to read chain data directly. If you want to track activity on the Provenance Blockchain for a report or a personal project, a node provides a primary source rather than secondhand summaries.
Teams exploring finance-focused applications can use a node to rehearse integration work before going live. Students of Cosmos-style chains can also learn how consensus, networking and state storage fit together by watching a node operate on their own machine.
Key features
Full node software for Provenance Blockchain
Proof-of-stake consensus
Designed for financial services
Open source under Apache 2.0
Windows build or installer
Supported coins
The Provenance Blockchain is the network this node serves, and it is the place where its consensus and state live. The project's documentation also references Cosmos (ATOM), which reflects the program's position within the wider Cosmos ecosystem. A node supports the chain it connects to rather than acting as a multi-asset wallet.
How to install Provenance node on Windows
- 1
Get the installer or build
Open the official project website or the GitHub Releases page at github.com/provenance-io/provenance. Download only from the official website or those release pages, and choose the Windows build or installer. Check that the version number matches the release you intend to run.
- 2
Verify the file
Compute the SHA-256 checksum of the downloaded file in PowerShell using Get-FileHash, then compare it with the value published with the release. If the release includes a signature, verify that as well. Do not run a file whose checksum does not match.
- 3
Install or extract
Run the installer and follow its prompts, or extract the build to a dedicated folder you control. Keeping the node in its own directory makes backups, upgrades and removal simpler. Avoid placing it in a shared or synced folder.
-
Initialize and start
Follow the initialization and configuration steps in the project documentation to create the home directory and configuration files. Then start the provenanced process from a terminal and let it sync. Initial synchronization can take a long time and depends on your connection and disk speed.
How to use Provenance node
Once the node is installed, the work is mostly configuration and patience. The steps below describe a typical first session on Windows. Exact commands and flags change between releases, so match them to the documentation for the version you installed.
- Open PowerShell and run the program's version command to confirm the binary starts correctly.
- Initialize the node's home directory using the initialization command from the project documentation, which creates the configuration and genesis files.
- Open the configuration file and review peer settings, ports and logging options before you start the node for the first time.
- Start the provenanced process in a terminal window and watch the output while the node connects to peers and begins syncing blocks.
- Check the sync status through the local RPC endpoint described in the documentation, so you can tell when the node has caught up with the chain.
- Keep the terminal or a background service running, and check the GitHub release notes regularly so you can apply updates on your own schedule.
Pros & cons
- Free to use, with no licensing fees
- Open source under the permissive Apache 2.0 license
- Windows build or installer available, so Go is not required to run it
- Built for financial services use cases on its own network
- Proof-of-stake design that the project presents as eco-friendly
- The newest listed version is a release candidate, so details may change before the final release
- Narrower focus than general-purpose node software; the main use is the Provenance network
- Setup assumes comfort with terminal commands and configuration files
- A node needs steady network access and ongoing attention to updates
Is Provenance node safe?
Download only from the official website or the project's GitHub Releases page, then verify the SHA-256 checksum or signature before running the file. Never enter a seed phrase on third-party websites, and never share validator or wallet keys with anyone. A node runs continuously with network access, so keep it in a dedicated folder, limit which other programs can reach its ports and avoid unofficial forks or builds from unknown mirrors. Keep your configuration and any key material backed up offline in a secure location.
- Official source only. Download from github.com/provenance-io/provenance. 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
Compared with Cosmos Hub's gaiad, which runs the Cosmos Hub itself, Provenance node focuses on the Provenance Blockchain and its financial-services design. Celestia App and Evmos also serve networks in or around the Cosmos ecosystem, but each targets its own chain and tooling. Geth is the Go implementation of the Ethereum protocol, and Bitcoin Core runs Bitcoin's proof-of-work network, so both suit different ecosystems. Aptos offers a node and command-line tools for a separate chain. If your goal is the Provenance network, this is the direct choice; for another chain, pick the client that matches it.
Specifications
- Price
- Free
- Type
- Open source
- License
- Apache 2.0
- Latest version
- v1.31.0-rc1
- Last update
- 30 Oct 2026
- Windows support
- Yes (Windows build or installer)
- Source code
- github.com/provenance-io/provenance
Frequently asked questions
Running the software is reasonable if you get it from the official project sources and verify the file before use. Check the SHA-256 checksum or signature, keep the node in its own folder and never share keys or enter a seed phrase on websites. Treat the release candidate as pre-release software and test it first.
Yes, Provenance node is free to download and use. It is released under the Apache 2.0 license, which allows you to use, modify and redistribute the code under the license terms. Your main costs will be your own hardware, storage and internet connection.
No, you do not need Go for everyday use. The program is written in Go, but a ready-made Windows build or installer is available. Go and similar tools are typically needed only when you compile the software from source yourself.
The provenanced daemon is the core program that runs a Provenance node. It handles networking, storage and rule checks that keep your machine synchronized with the Provenance Blockchain. It runs in the background, so most people operate it from a terminal rather than a graphical window.
Provenance node connects to the Provenance Blockchain, a proof-of-stake network built for financial services. It is not a node for Cosmos Hub, although the project sits within the broader Cosmos ecosystem. Make sure you are using the client that matches the chain you want to join.
No. Gaia, which runs as gaiad, is the node for the Cosmos Hub network, while Provenance node serves the Provenance Blockchain. The two programs share a broader ecosystem connection but run separate chains. Choose based on which network you intend to join.
Verdict
Provenance node is a sound choice if you want to run a full node on the Provenance Blockchain from a Windows PC and you are comfortable with command-line setup. It is free, open source under Apache 2.0 and designed around financial-services use cases. It is less suited to casual users who only want a wallet or a quick way to check balances. Because the newest listed build is a release candidate, check the latest version on the official website before setting up a node you plan to rely on.