cometbft
A Byzantine fault-tolerant consensus engine for replicating state machines across distributed systems, powering blockchain networks.
What is cometbft?
CometBFT is a distributed, Byzantine fault-tolerant consensus engine that acts as middleware for deterministic state machine replication. It securely replicates applications across many machines, enabling the creation of scalable blockchain networks and decentralized systems. It is a fork and successor to Tendermint Core, implementing the Tendermint consensus algorithm.
Blockchain developers and teams building decentralized applications (dApps) or custom blockchain networks that require robust, high-performance consensus. It is particularly suited for projects within the Cosmos ecosystem or those needing language-agnostic state replication.
Developers choose CometBFT for its battle-tested reliability, high transaction throughput (up to 10k TPS), and the flexibility offered by its ABCI++ interface, which allows deep customization of the consensus process. Its modular, language-agnostic design separates consensus from application logic, improving maintainability.
Overview
CometBFT: A distributed, Byzantine fault-tolerant, deterministic state machine replication engine. A fork and successor to Tendermint Core.
Use Cases
Best For
- Building custom blockchain networks and app-chains
- Creating decentralized applications (dApps) requiring high transaction throughput
- Implementing Byzantine fault-tolerant consensus in distributed systems
- Developing within the Cosmos ecosystem interoperability framework
- Projects needing language-agnostic state machine replication
- Systems where deterministic consensus across many machines is critical
Not Ideal For
- Projects requiring simple, out-of-the-box consensus without custom programming, as ABCI++ integration adds complexity
- Teams operating in environments where Go is not preferred, since the core engine is Go-based and requires Go dependencies
- Applications with ultra-low latency requirements where BFT consensus overhead (e.g., message propagation delays) is unacceptable
- Small-scale or experimental projects where the operational burden of a distributed BFT system outweighs the benefits
Pros & Cons
Pros
Achieves speeds up to 10,000 transactions per second (TPS), as stated in the README, making it suitable for scalable decentralized applications.
ABCI++ enables programmability at every consensus step, allowing developers to customize the engine for specific blockchain logic, as highlighted in the features.
Replicates state machines written in any programming language, providing flexibility in tool selection, which is emphasized in the philosophy section.
Described as the most widely-adopted consensus engine, it has proven reliability in production, as noted in the GitHub description.
Cons
The README admits that MINOR version bumps may require starting a new blockchain, complicating upgrades and increasing migration effort.
ABCI++ and distributed consensus concepts demand significant expertise, which can be a barrier for teams new to BFT systems.
Maintained by Cosmos Labs, it ties closely to the Cosmos stack, potentially limiting flexibility and increasing vendor lock-in for non-Cosmos projects.
Frequently Asked Questions
Related Projects
go-ethereumGo implementation of the Ethereum protocol
kuboAn IPFS implementation in Go
lndLightning Network Daemon ⚡️
cosmos-sdk:chains: A Framework for Building High Value Public Blockchains :sparkles:
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.