# Installer teku avec Homebrew

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

## installation

```sh
sudo av install brew:teku
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install teku
```

  Preuve: local Homebrew formula metadata

## Faits du paquet

- **Clé du paquet:** brew:teku
- **Gestionnaire de paquets:** Homebrew
- **Version:** 26.7.1
- **Résumé source:** Java Implementation of the Ethereum 2.0 Beacon Chain
- **Page d'accueil:** <https://docs.teku.consensys.net/>
- **Dépôt:** <https://github.com/ConsenSys/teku>
- **Dernière mise à jour:** 2026-07-11T10:20:41Z
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- teku (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 26.7.1
## Historique du projet et usages

Teku is Consensys' open source Ethereum consensus client written in Java. It implements a beacon node and validator client for proof-of-stake Ethereum, making the Homebrew package useful to operators who want a packaged consensus-layer binary rather than a Docker-only workflow.

### Historique du projet

The public Consensys/teku repository dates to 2018, during the Ethereum 2.0 beacon-chain development period. The current documentation describes Teku as an Ethereum consensus client, previously called an Ethereum 2.0 client, with both beacon node and validator-client functionality.

Teku's role changed with Ethereum's transition from the Eth2 terminology to the execution/consensus split. Consensys documentation states that The Merge completed on September 15, 2022 and that an Ethereum node now combines a consensus client such as Teku with an execution client such as Besu.

### Historique d'adoption

Teku was adopted in the staking and validator-operations community as one of the client options for running Ethereum proof-of-stake infrastructure. Official docs cover mainnet and testnet operation, validator key loading, Prometheus metrics, REST APIs, external signing, and execution-client integration.

The tool's adoption is tied to Ethereum client diversity: operators pair Teku with execution clients, run it as a beacon node, or run its validator-client subcommand against local or remote beacon nodes.

### Modes d'utilisation

Package users typically install Teku to run a beacon node, run validators, test networks, expose metrics, or manage validator lifecycle commands such as voluntary exits. Teku options can be provided on the command line, through TEKU_* environment variables, or in a YAML configuration file.

In Homebrew and package-manager workflows, Teku matters because it gives validator operators a reproducible CLI binary with standard Unix service and config-file integration, instead of requiring a bespoke Java build.

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

Teku is a good example of a blockchain node package whose real value is not just the executable, but the surrounding operational contract: config files, keystore paths, JWT secrets, metrics ports, and upgrade cadence all matter to stakers.

For package nerds, it sits at the intersection of Java packaging, long-running daemon management, and high-stakes protocol upgrades, where timely formula updates can be operationally important.

### Chronologie

- 2018: Consensys/teku repository created.
- 2020: Ethereum beacon-chain validator operation becomes Teku's central production use case.
- 2022: Ethereum's Merge completes; Teku is documented as a consensus client paired with an execution client.
- 2026: Teku 26.7.0 is published in the official GitHub releases.

### Related projects

- Besu is the Consensys execution client commonly paired with Teku in documentation.
- Web3Signer is referenced by Teku docs for external validator signing.
- Other Ethereum consensus clients fill the same operational niche, but Teku's Java implementation and Consensys backing distinguish it.

### Sources

- <https://docs.teku.consensys.io/concepts/node-types>
- <https://docs.teku.consensys.io/get-started/start-teku>
- <https://docs.teku.consensys.io/introduction>
- <https://github.com/Consensys/teku>
- <https://github.com/Consensys/teku/releases/tag/26.7.0>


## Notes de sécurité

narrow executable package without higher-risk signals.

- **Risque Geiger:** vert / faible
- narrow executable package without higher-risk signals


## 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: /home/me/me_node/config.yaml

## Credential files

- Unix: /home/validator/keys, /home/validator/passwords, <data-beacon-path>/kvstore/generated-node-key.dat

## Combined YAML source

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


## Sources

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