# Install teku with Homebrew Java Implementation of the Ethereum 2.0 Beacon Chain. Version 26.7.0 via Homebrew; verified 2026-07-01. ## Install ```sh sudo av install brew:teku ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install teku ``` Evidence: local Homebrew formula metadata ## Package facts - **Package key:** brew:teku - **Package manager:** Homebrew - **Package manager page:** - **Version:** 26.7.0 - **Source summary:** Java Implementation of the Ethereum 2.0 Beacon Chain - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** Apache-2.0 - **Source archive:** - **Last updated:** 2026-07-01T11:08:42Z - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - teku (cli) - teku (alias) ## Dependencies - openjdk@25 ## Build dependencies - gradle ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux ## Freshness - Page generated: 2026-07-08 - Package-manager version: 26.7.0 - Package-manager updated: 2026-07-01 - Local data: ok - Upstream repository: https://github.com/ConsenSys/teku - info: No cached GitHub release or tag data was available. ## Project history and usage 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. ### 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 - - - - - ## Security Notes narrow executable package without higher-risk signals. - **Geiger risk:** green / low - 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, /kvstore/generated-node-key.dat ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** teku - **Version Scheme:** 0 - **Revision:** 0 - **Head Version:** HEAD - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** head, stable ## Related links - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Language runtime packages](https://www.automicvault.com/pkg/language-runtime-packages/) - Matched language runtime, compiler, or interpreter metadata. - [Networking and protocol packages](https://www.automicvault.com/pkg/networking-protocol-tools/) - Matched network, protocol, or remote-service metadata. - [Documentation packages](https://www.automicvault.com/pkg/documentation-tools/) - Matched documentation, manual, or publishing metadata. - [openjdk@25](https://www.automicvault.com/pkg/brew/openjdk-25/) - Runtime dependency declared by Homebrew. - [gradle](https://www.automicvault.com/pkg/brew/gradle/) - Build dependency declared by Homebrew. - [lighthouse](https://www.automicvault.com/pkg/brew/lighthouse/) - Shares av.db curated category or tags: blockchain, cli, consensus-client, ethereum, networking. - [btcli](https://www.automicvault.com/pkg/brew/btcli/) - Shares av.db curated category or tags: blockchain, cli, networking. - [hsd](https://www.automicvault.com/pkg/brew/hsd/) - Shares av.db curated category or tags: blockchain, cli, networking. - [oasis](https://www.automicvault.com/pkg/brew/oasis/) - Shares av.db curated category or tags: blockchain, cli, networking. - [stellar-core](https://www.automicvault.com/pkg/brew/stellar-core/) - Shares av.db curated category or tags: blockchain, cli, networking. - [floresta](https://www.automicvault.com/pkg/brew/floresta/) - Shares av.db curated category or tags: blockchain, cli, networking. - [ord](https://www.automicvault.com/pkg/brew/ord/) - Shares av.db curated category or tags: blockchain, cli, networking. - [bitcoin](https://www.automicvault.com/pkg/brew/bitcoin/) - Shares av.db curated category or tags: blockchain, cli, networking. ## Combined YAML source View the package source record on GitHub. [combined/teku.yml](https://github.com/automic-vault/db/blob/main/combined/teku.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - av.db category and tag curation - package relationship graph - cross-ecosystem install command graph