Install teku with Homebrew

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• teku

Project history

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.

Adoption history

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.

How it is used

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.

Why package nerds care

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.

Timeline

• 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