CometBFT for Windows gives blockchain developers a ready-made consensus engine, the component that lets many independent machines agree on one shared history of transactions. It is aimed at developers and infrastructure teams who build or run their own blockchain networks. The project was formerly known as Tendermint, is open source, is free to use, and is written in Go.
This page explains what the engine does, how to get the Windows build or installer, and how it compares with other node software. One caution first: the latest tagged release is v2.0.0-alpha.1, a pre-release, and the codebase is actively updated. Treat it as a development tool for testing, not a finished production component. Readers who only want to hold or send coins will find more suitable tools elsewhere in this catalog.
What Is a Consensus Engine and Why It Matters
A blockchain is a shared ledger that many computers keep in sync, and no single party controls all of them. Consensus is the process by which those computers agree on which transactions come next and in what order. Without it, two nodes could record different histories and the network would split.
A consensus engine automates that agreement. It sends proposals, collects votes, and commits a block only once enough participants have signed off. Developers rarely want to design this logic from scratch, because mistakes in voting or message handling can halt a chain or let a faulty node corrupt the record.
CometBFT packages this work as a reusable component. It is the part of the stack that answers the question 'what is the agreed next block?', while the application answers 'what does this block do to balances and rules?' Understanding that boundary is the first step to using the project correctly.
Who CometBFT Is For
CometBFT suits blockchain developers who are building a new chain or experimenting with app-specific networks. A typical reader writes application code in Go, wants to test how validators behave, and needs a consensus layer that is designed for real networks.
It is also useful for infrastructure engineers who maintain nodes for an existing Cosmos-based network and need to understand the engine underneath. Learning how blocks are proposed and committed helps in diagnosing stalls, upgrades, and peer connection problems.
It is less suitable for people who simply want a wallet, a miner, or a trading tool. Those users interact with finished applications rather than the engine itself. If your goal is to hold coins on Windows, look at wallet programs instead, and treat this page as background reading rather than an everyday setup guide.
Real-World Scenarios for a Test Network
A common first project is a single-machine test network. A developer starts one node on a Windows PC, connects a simple application through the interface, and watches blocks being produced. This shows how transactions move from submission to commitment without the cost of a public chain.
Another scenario is a small private network of several nodes on one laptop or across a few test machines. Here the important lessons concern validator sets, what happens when one node goes offline, and how the network recovers. Running these experiments before touching any public network saves time and protects real funds.
Teams also use the engine to rehearse upgrades. They can run a version of their application against a newer engine build and check whether blocks still commit as expected. Because the latest tagged release is an alpha, such rehearsals are exactly where the project is best used at present.
Key features
Byzantine fault-tolerant consensus
Application interface for custom logic
Windows build or installer
Docker platform support
Supported coins
The project's documentation mentions Cosmos (ATOM) as a network connected to this engine's ecosystem. CometBFT itself does not hold coins or tokens; assets live on the chains built with it, so check each chain's own documentation for its token and network details.
How to install CometBFT on Windows
- 1
Download the release
Open the GitHub Releases page at github.com/cometbft/cometbft/releases and choose the Windows build or installer for the version you want. Download only from the official website or GitHub, not from mirrors or file-sharing sites.
- 2
Verify the file
Compare the file's SHA-256 hash with any checksum published alongside the release, and check a signature if the release provides one. If the values do not match, delete the file and download it again from the official source.
- 3
Install into a dedicated folder
Run the installer or extract the build into a folder you control, such as a project directory on a separate drive. Keeping the engine apart from personal documents makes it easier to update or remove later.
-
Confirm it starts
Open a terminal in that folder and start the program with its built-in help or version option to confirm the file runs. If you prefer containers, the project lists Docker as a supported platform, and you can use that route instead.
How to use CometBFT
CometBFT is normally used as part of a larger application, so the workflow below describes a typical developer test rather than a single click.
- Initialize a node home directory with the engine's configuration files.
- Edit the configuration to set a node name, peer addresses, and the ports your test network should use.
- Start your application so it listens for requests from the engine through the standard interface.
- Start the engine and confirm it connects to the application and to any peers.
- Submit a few test transactions and watch blocks being committed in the logs.
- Stop the nodes cleanly and keep a copy of the configuration you used, so the test can be repeated.
Keep test networks on your own machine or a private network while you learn. Record which engine version you ran, because pre-release versions can change behavior between builds. When something goes wrong, the logs usually show whether the problem lies in peer connections, the application interface, or block timing, which narrows down the fix.
Pros & cons
- Free and open source, with source code and releases published on GitHub
- Built on the design lineage of the Tendermint project it succeeded
- Clear separation between consensus logic and application logic
- Windows build or installer available, plus Docker support
- The latest release is a pre-release (v2.0.0-alpha.1), not a stable production version
- Requires developer knowledge; it is not a wallet or end-user application
- Needs an application built on top of it before it does anything useful
Is CometBFT safe?
Download CometBFT only from the official GitHub repository at github.com/cometbft/cometbft or its Releases page. Do not install copies from third-party download sites, forum posts, or repackaged archives, because they may contain modified code. Verify the SHA-256 checksum or signature against the values published with the release before you run the file. Because the latest release is an alpha, expect bugs and changes between builds, and do not use it to secure real funds or production networks. If your test setup involves validator keys, never enter a seed phrase or key material on any website, and keep keys out of shared folders. Check the releases page for the most recent version before starting a new project.
- Official source only. Download from github.com/cometbft/cometbft. 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
CometBFT is a consensus engine, not a complete node for a finished network. Geth and Bitcoin Core are full clients for Ethereum and Bitcoin, where you run the whole protocol and sync the chain for that network. Aptos's node and CLI tools cover a specific layer-one network as well. Cosmos Hub's gaiad and Celestia App are application-level programs built on Cosmos-style consensus, so they package a particular chain's rules along with the consensus machinery. CometBFT is the component you would use to build such a chain yourself, or to study how one works. If you want to join an existing network as a user, one of those full clients is usually the more direct choice.
Specifications
- Price
- Free
- Type
- Open source
- License
- —
- Latest version
- v2.0.0-alpha.1
- Last update
- 22 Oct 2026
- Windows support
- Yes (Windows build or installer)
- Source code
- github.com/cometbft/cometbft
Frequently asked questions
Yes, CometBFT is the consensus engine that was formerly known as Tendermint, and the project continues under the new name. If you find older tutorials or code that refer to Tendermint, the underlying consensus ideas are similar, although interfaces and versions may differ. Check the current project documentation before following an older guide, since details change between releases.
It can be, if you get the file from the project's GitHub Releases page and verify it before running. Compare the SHA-256 checksum or signature, and avoid copies from third-party sites. Because the latest release is a pre-release, treat it as test software and do not connect it to networks holding real funds without careful review.
No, CometBFT is a consensus engine for blockchain networks, not mining software. It coordinates how nodes agree on blocks, which is a different job from the hashing that miners perform. The engine does not promise any income, and nothing on this page should be read as a suggestion that running it will earn money.
For the ready-made Windows build or installer, you do not need to install Go. The project is written in Go, so Go is a build-time tool used by developers who compile the engine from source. If you plan to modify the code or build your own binary, you will need the Go toolchain installed separately.
The project's documentation mentions Cosmos (ATOM) as a network in its ecosystem, which is why many Cosmos-based chains build on this engine. CometBFT does not hold ATOM itself. Users interact with Cosmos through the chain's own node or wallet software, so check that software's documentation for supported features.
Yes, CometBFT is free and open source. The source code is public on GitHub, so you can read it, build it yourself, or contribute. Your own costs, such as hardware, storage, or cloud hosting, are separate from the software itself.
Yes, Docker is one of the platforms the project lists. Running the engine in a container keeps its files and network settings isolated from the rest of your system, which helps during testing. Use a container runtime such as Docker Desktop, and pull images only from trusted, official sources.
The latest tagged release is v2.0.0-alpha.1, a pre-release, so it is not a stable production version. Use it for learning, experiments, and private test networks. Before any production deployment, wait for a stable release and review the project's documentation and open issues carefully.
Verdict
CometBFT is a serious, free consensus engine for developers who want to build or study blockchain networks, and it runs on Windows through a build, an installer, or Docker. It is not a wallet, miner, or trading tool, and most everyday crypto users will never need it. The current release is an alpha, so the best use today is learning, prototyping, and private test networks. If you are building a chain, start here and follow the safety steps above. If you want to join an existing network, a full node client is a more direct fit.