How do I build a blockchain from scratch with Tendermint?

Start by implementing your application logic in any language using the ABCI interface, then set up nodes using the quick start guides for single nodes or clusters with docker-compose. You'll need to handle state machine replication and peer configuration manually.

Tendermint vs proof-of-work consensus like Bitcoin: what's the difference?

Tendermint uses Byzantine Fault Tolerant consensus for fast, deterministic finality without mining, making it more energy-efficient and suitable for apps needing quick confirmations. Proof-of-work relies on probabilistic finality and mining, which is slower but more decentralized in permissionless settings.

Can I use JavaScript or Python to write apps with Tendermint?

Yes, through the ABCI interface, you can write application logic in any language that supports socket or gRPC communication. However, you may need to implement ABCI clients yourself or use community libraries, as Tendermint itself is in Go.

How to upgrade a Tendermint network without breaking it?

Upgrades can be tricky due to breaking changes; refer to UPGRADING.md for guidance. Minor version bumps may require starting a new blockchain, so plan for data migration and test thoroughly in staging environments first.

What are common security vulnerabilities in Tendermint?

Vulnerabilities can arise in consensus logic or P2P gossip; report them via the security email listed. Follow best practices like using the latest supported versions, securing node configurations, and monitoring for disclosed issues in the security policy.

Tendermint or Ethereum for building dApps?

Tendermint is better for custom appchains needing BFT consensus and language flexibility, while Ethereum suits dApps leveraging its smart contract ecosystem and broader tooling. Tendermint excels in the Cosmos ecosystem with IBC interoperability.

tendermint — Byzantine Fault Tolerant Middleware

What is tendermint?

Tendermint Core is a Byzantine Fault Tolerant (BFT) consensus engine and blockchain replication layer. It enables developers to build secure, decentralized applications by providing a robust foundation for state machine replication without requiring mining. It acts as middleware that takes a state transition machine written in any programming language and securely replicates it across many machines.

Target Audience

Blockchain developers and teams building decentralized applications (dApps) or custom blockchain networks who need a production-proven, language-agnostic consensus layer. It is particularly suited for projects within the Cosmos ecosystem or those requiring BFT consensus without proof-of-work mining.

Value Proposition

Developers choose Tendermint Core for its production-proven Byzantine Fault Tolerant consensus, which ensures network security even with up to one-third of malicious participants, and its flexibility via the ABCI (Application Blockchain Interface), which allows application logic to be written in any programming language.

⟁ Tendermint Core (BFT Consensus) in Go

Use Cases

Best For

Building custom, application-specific blockchains (appchains) that require high security and deterministic finality.
Creating decentralized applications (dApps) within the Cosmos ecosystem that need to interoperate via the Inter-Blockchain Communication (IBC) protocol.
Developing blockchain networks that prioritize fast transaction finality over the probabilistic finality of proof-of-work systems.
Projects requiring a language-agnostic blockchain backend, allowing application logic to be written in Go, Rust, JavaScript, or any other language via ABCI.
Enterprise or consortium blockchains that need a Byzantine Fault Tolerant consensus mechanism for permissioned or private network environments.
Research and development in distributed systems, particularly for studying or implementing BFT consensus algorithms and state machine replication.

Not Ideal For

Teams needing a stable, version 1.0+ product with guaranteed backward compatibility and long-term support
Projects that don't require Byzantine fault tolerance or distributed consensus, such as centralized apps or simple databases
Developers wanting a fully integrated blockchain platform with built-in smart contracts and extensive out-of-the-box tooling
Applications prioritizing maximum throughput with minimal consensus latency, as BFT can introduce overhead compared to other algorithms

Pros & Cons

Pros

Production-Proven BFT Consensus

Used in major networks like Cosmos Hub and Terra, demonstrating reliability and security in real-world production environments, as highlighted in the README.

Language-Agnostic via ABCI

The Application Blockchain Interface allows state machines to be written in any programming language, providing unmatched flexibility for developers, as stated in the key features.

Efficient Gossip Protocol

Implements a secure peer-to-peer communication protocol based on research, ensuring efficient message propagation and network performance, detailed in the 'The latest gossip on BFT consensus' paper.

Byzantine Fault Tolerance

Ensures consensus even with up to one-third malicious participants, offering strong security guarantees for decentralized applications without mining, as core to its design.

Cons

Pre-1.0 Stability Risks

The project hasn't released v1.0, with breaking changes still possible and only patch updates for recent minor releases, posing risks for long-term production use, as admitted in the versioning section.

Complex ABCI Integration

Requires developers to build and integrate application logic separately via ABCI, adding significant development overhead compared to more turnkey blockchain solutions.

Limited Active Development

The core featureset is frozen for LTS, and the small team focuses on recent releases, which may reduce future innovation and support, as noted in the README update.

Frequently Asked Questions

What is tendermint?

Target Audience

Value Proposition

Use Cases

Best For

Building custom, application-specific blockchains (appchains) that require high security and deterministic finality.
Creating decentralized applications (dApps) within the Cosmos ecosystem that need to interoperate via the Inter-Blockchain Communication (IBC) protocol.
Developing blockchain networks that prioritize fast transaction finality over the probabilistic finality of proof-of-work systems.
Projects requiring a language-agnostic blockchain backend, allowing application logic to be written in Go, Rust, JavaScript, or any other language via ABCI.
Enterprise or consortium blockchains that need a Byzantine Fault Tolerant consensus mechanism for permissioned or private network environments.
Research and development in distributed systems, particularly for studying or implementing BFT consensus algorithms and state machine replication.

Not Ideal For

Teams needing a stable, version 1.0+ product with guaranteed backward compatibility and long-term support
Projects that don't require Byzantine fault tolerance or distributed consensus, such as centralized apps or simple databases
Developers wanting a fully integrated blockchain platform with built-in smart contracts and extensive out-of-the-box tooling
Applications prioritizing maximum throughput with minimal consensus latency, as BFT can introduce overhead compared to other algorithms

Pros & Cons

Pros

Production-Proven BFT Consensus

Used in major networks like Cosmos Hub and Terra, demonstrating reliability and security in real-world production environments, as highlighted in the README.

Language-Agnostic via ABCI

The Application Blockchain Interface allows state machines to be written in any programming language, providing unmatched flexibility for developers, as stated in the key features.

Efficient Gossip Protocol

Implements a secure peer-to-peer communication protocol based on research, ensuring efficient message propagation and network performance, detailed in the 'The latest gossip on BFT consensus' paper.

Byzantine Fault Tolerance

Ensures consensus even with up to one-third malicious participants, offering strong security guarantees for decentralized applications without mining, as core to its design.

Cons

Pre-1.0 Stability Risks

Complex ABCI Integration

Requires developers to build and integrate application logic separately via ABCI, adding significant development overhead compared to more turnkey blockchain solutions.

Limited Active Development

The core featureset is frozen for LTS, and the small team focuses on recent releases, which may reduce future innovation and support, as noted in the README update.

Frequently Asked Questions

tendermint

What is tendermint?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

tendermint

What is tendermint?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?