# tendermint mit Homebrew, Nix installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für tendermint in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:tendermint
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install tendermint
```

  Evidenz: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#tendermint
```

  Evidenz: nixpkgs package indexes: pkgs/by-name/te/tendermint/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Paketfakten

- **Paketschlüssel:** brew:tendermint
- **Paketmanager:** Homebrew
- **Version:** 0.35.9
- **Quellzusammenfassung:** BFT state machine replication for applications in any programming languages
- **Homepage:** <https://tendermint.com/>
- **Repository:** <https://github.com/tendermint/tendermint>
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- tendermint (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 0.35.9
## Projektgeschichte und Nutzung

Tendermint Core is a Byzantine Fault Tolerant state-machine replication engine used as blockchain consensus middleware. Its README describes it as software that takes a state transition machine written in any programming language and securely replicates it across many machines.

### Projektgeschichte

The Tendermint repository was created in May 2014. The project developed as a Go implementation of BFT consensus with a generic application interface, later documented as Tendermint Core and the Application Blockchain Interface.

Official documentation describes Tendermint as two chief components: the Tendermint Core consensus engine, which orders transactions consistently across machines, and ABCI, which lets application logic be implemented in any programming language. This separation made Tendermint a reusable engine rather than a single-purpose blockchain.

The README says Tendermint had been used in production in private and public environments, most notably in blockchains of the Cosmos Network. It also notes that the Tendermint Core feature set was later frozen for long-term support, with v0.34.24 used by cosmoshub-4.

### Adoptionsgeschichte

Tendermint's adoption is closely tied to Cosmos. Its ABCI model allowed the Cosmos SDK and other applications to build application-specific blockchains while relying on Tendermint for networking, mempool, consensus, and block replication.

The later CometBFT project identifies itself as a fork and successor to Tendermint Core, showing how the consensus engine continued under a new project identity while preserving the Tendermint consensus lineage.

Homebrew and Nix package coverage reflects a developer and operator audience: people install the `tendermint` binary to initialize nodes, inspect configuration, run local chains, or support blockchain development environments.

### Wie es verwendet wird

The official configuration docs say Tendermint Core uses `$TMHOME/config/config.toml` and that `tendermint init` creates a default configuration. The same configuration references `config/genesis.json`, `config/priv_validator_key.json`, and `config/node_key.json`, which are central files for running a node.

The getting-started docs present Tendermint as one process paired with a separate application process. Tendermint handles P2P and consensus, then forwards transactions to the application for validation and commit through ABCI.

For package users, this makes the command both a node daemon and a development tool: it can bootstrap config directories, run local test networks, and connect arbitrary ABCI applications to a BFT consensus layer.

### Warum Paket-Nerds sich dafür interessieren

Tendermint is significant in package-manager culture because it packages a full consensus node as a normal CLI formula. Installing it pulls a complex distributed-systems runtime into the same workflows as Go tools, local daemons, and blockchain testnets.

Its long pre-1.0 versioning and explicit upgrade warnings are also a packaging lesson: patch versions were intended to preserve blockchain histories, while minor bumps could require chain migration or restarts. That matters to maintainers because the binary's version is part of network compatibility, not just local tooling.

### Zeitleiste

- 2014: Tendermint GitHub repository created.
- 2018: The Tendermint BFT consensus paper was linked from the README as protocol analysis.
- 2020s: README described production use in private and public environments, especially Cosmos Network blockchains.
- 2020s: Tendermint Core feature set frozen for LTS, with v0.34.24 identified as the stable release used by cosmoshub-4.
- 2020s: CometBFT became the fork and successor to Tendermint Core.

### Related projects

- Cosmos SDK is the most prominent related application framework in the Tendermint ecosystem.
- CometBFT is the successor fork that implements the Tendermint consensus algorithm.
- Related libraries and applications named in the README include tendermint-rs, ABCI Tower, Cosmos Hub, Terra, Celestia, Anoma, and Vocdoni.

### Quellen

- <https://api.github.com/repos/tendermint/tendermint>
- <https://docs.tendermint.com/v0.33/introduction/what-is-tendermint.html>
- <https://docs.tendermint.com/v0.34/app-dev/getting-started.html>
- <https://docs.tendermint.com/v0.34/tendermint-core/configuration.html>
- <https://github.com/cometbft/cometbft#readme>
- <https://github.com/tendermint/tendermint#readme>
- source_facts.package-manager


## Sicherheitshinweise

generalized runtime or code generation signal.

- **Geiger-Risiko:** yellow / mittel
- generalized runtime or code generation signal


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: $TMHOME/config/config.toml, $TMHOME/config/genesis.json

## Credential files

- Unix: $TMHOME/config/priv_validator_key.json, $TMHOME/config/node_key.json
## Andere Paketmanager-Einträge

- Nix - tendermint: normalized package name match | nixpkgs package indexes: pkgs/by-name/te/tendermint/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/tendermint.yml](https://github.com/mxcl/pkgdb/blob/main/combined/tendermint.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph