pkg.soopen package index

brew / rang 11088

Installer tendermint avec Homebrew, Nix

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de tendermint pour les workflows d'agents IA.

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install tendermint

local Homebrew formula metadata

Linux

Nixvérifié · 92%
nix profile install nixpkgs#tendermint

nixpkgs package indexes · pkgs/by-name/te/tendermint/package.nix · Source: api.github.com

aperçu

Résumé du paquet

BFT state machine replication for applications in any programming languages

Commandes et alias

  • tendermint

historique

Historique du projet et usages

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.

Historique du projet

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.

Historique d'adoption

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.

Modes d'utilisation

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.

Pourquoi les passionnés de paquets s'y intéressent

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.

Chronologie

  • 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.

posture de sécurité

Niveau de risque : yellow

generalized runtime or code generation signal.

Classificateur de risque

risque yellow · confiance moyen · runtime

Pourquoi

  • generalized runtime or code generation signal

Signaux

  • text:programming language,repl

Comportement d'installation

  • Aucune métadonnée de bottle Homebrew n’a été enregistrée.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des plugins.

local files

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

Config paths the tool may read or write during local use.

Unix
$TMHOME/config/config.toml$TMHOME/config/genesis.json

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
$TMHOME/config/priv_validator_key.json$TMHOME/config/node_key.json

exécutables

Exécutables installés

CommandeTypeExpositionNote
tendermintexécutableexécutable indexéDécouvert depuis l'index local des exécutables.

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-08-03
version du gestionnaire0.35.9
gestionnaire mis à jour
données localesinconnu
amontnon disponible
dernière version détectéenon détecté
  • OKAucun avertissement de fraîcheur n'a été généré.

métadonnées d'installation

Métadonnées du paquet

Clé du paquetbrew:tendermint
Version0.35.9
Gestionnaire de paquetsHomebrew
Page d'accueilhttps://tendermint.com/
Dépôthttps://github.com/tendermint/tendermint
Bouteillenon enregistré
Serviceaucun déclaré

correspondances dans les bases sources

Autres enregistrements de gestionnaires de paquets

Les correspondances proviennent d’index externes de gestionnaires de paquets et restent séparées des liens de paquets Automic Vault locaux.

Nix95%

tendermint

nix profile install nixpkgs#tendermint
  • normalized package name match
  • Correspondance par : Tendermint
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/te/tendermint/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Sources utilisées

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