Reworking validator operations for the Pectra era
Validator Tools is a desktop control panel for Ethereum validators. It turns EIP-7002 exits, EIP-7251 consolidations, MEV-Boost policy, withdrawal credentials, redundancy and monitoring into clear, repeatable workflows instead of ad-hoc scripts and spreadsheets.
Local-first · Keys stay under your control · Works with Lighthouse, Teku, Prysm, Nimbus, Lodestar
Validator Tools sits between your validators and your signing stack, turning exits, partial withdrawals, consolidations and MEV policy into one predictable, auditable run.
Validator Tools runs next to your beacon and validator clients as a desktop operational layer. It plans and rehearses 7002 exits, 7251 consolidations, BLS→0x01 changes and payout runs, then hands payloads to the signing stack you already trust.
Build, sign, and export BLS→Execution (0x00→0x01) changes entirely offline; construct and submit EIP-7002 exit and partial-withdraw requests with on-chain fee discovery, EIP-1559 gas configuration, bounded retries, and batch execution. Run high-throughput withdrawal scanning by 0x01 address or validator index over a configurable lookback window with deadline control and per-block stats (avg, p50/p95).
Operate from a single console with Beacon/RPC health checks, utility static calls, structured JSON/CSV export, and local-first security (no secret persistence by default). Mainnet and Holesky supported; flexible Beacon authentication (Bearer / X-API-Key / query).
Desktop builds for Linux (AppImage), macOS and Windows. Your platform is highlighted.
Short, practical answers to how Validator Tools fits into your validator workflow, how it interacts with your signing setup, and what to expect around exits, partial withdrawals and consolidations.
It runs locally on your machine. The app talks only to your Beacon/RPC endpoints and your signing path. No hosted backend, no telemetry, no secret retention unless you explicitly opt in.
Mainnet and Holesky, with full flows for EIP-7002 and 7251. Works with Lighthouse, Teku, Prysm, Nimbus and Lodestar through standard Beacon & execution endpoints.
No. It prepares unsigned payloads for BLS→Execution (0x00→0x01), exits, partial withdrawals and consolidations. Signing stays where you keep it — a local signer, Safe or HSM.
Yes. Flows are designed around prepare → sign → execute. You can export payloads, have them signed elsewhere, then feed signed transactions back for submission and history.
Instead of scripts and spreadsheets, everything becomes a structured run: inputs → checks → run plan → sign → execute → export. Queue pressure, retries, fee caps and ETA modelling are handled inside the tool.
Yes. You can plan consolidations, model effective balance and APR impact, build transactions offline and replay the same plan on Holesky before promoting it to mainnet.
Operator runbooks, troubleshooting guides and release notes live in the documentation. They mirror the main flows in the app: exits, partials, consolidations and MEV operations.
Yes. There are dedicated notes for Safe / HSM setups, multi-operator workflows and audit-friendly history exports for stakeholders, accounting and compliance.
