The Ledger
Lido Seeks Proposals for Isolated Ethereum Validator Signers
A Lido governance-forum request seeks open-source Ethereum validator signers that keep keys inside operator-controlled hardware. It sets requirements for client compatibility, slashing protection, testing and maintenance, with grants expected to be below $50,000.

Lido is seeking proposals for open Ethereum validator signers that keep staking keys inside hardware controlled by the operator, according to a request posted to its governance forum. The request has no application deadline; the post says proposals will be reviewed as they arrive.
Keys kept inside hardware
TheDZhon says two node operators had to exit their Lido validators after infrastructure compromises, in September 2025 and September 2026. The post describes tee-signer, a project Lido contributors are working on, as a pre-release built primarily for cloud trusted execution environments, and calls for alternative implementations.
The request allows designs using operator-run CPU trusted execution environments, Arm TrustZone boards, microcontrollers with secure elements, mobile phones with hardware secret management, professional on-premises hardware security modules, or existing remote signers adapted to run within those environments. On-premises support is required; cloud TEE support is optional.
A proposed signer must work through the standard remote-signing API with stock or patched upstream validator clients from at least three consensus-layer client implementations. Signers that only support their own client are out of scope. The request also discourages projects that share both hardware and code, while describing threshold signing as optional.
Security and testing requirements
Code written under a grant must be open source, with Apache-2.0 or MIT preferred; closed vendor platforms, including hardware and chip firmware, are permitted if listed. The key must remain inside the hardware boundary in plaintext terms: it must be generated there or imported in encrypted form, and recovery must use an encrypted copy on another device or a new key.
The signer must parse each request and calculate the signing root inside the boundary rather than signing a root supplied by the host. The appendix ideally places EIP-3076 slashing protection inside the boundary, with the record written before the signature goes out and surviving restarts and attempts to roll back the signer’s stored state. It also calls for explicit confirmation for changes to fee-recipient or exit settings, signed releases, reproducible builds, pinned cryptographic dependencies and a threat model.
Applicants are asked to run public test sets and publish results. The checks cover BLS signatures and signing roots, EIP-3076 slashing-protection tests, API compatibility, capacity and live validator duties. The capacity test should report signatures per slot while proposals, aggregation and sync-committee duties are running; about 100 attestations per slot is a target, not a minimum.
Grant terms and applications
The post estimates grants will be well below $50,000, though development hardware can be included in a budget. Payments are in stablecoins: 25% on approval, 50% after the signer meets the appendix requirements and completes 30 days of live duties on Hoodi or mainnet, and 25% over the first nine months of maintenance, paid quarterly.
Recipients commit to 18 months of maintenance from the first release, while the grant funds the first nine months. If a Curated operator runs the signer on mainnet by then, the post says the grant can be renewed annually; otherwise, funding ends after month nine.
A Curated operator may switch to a signer after it meets the appendix, runs for seven days on Hoodi and is reviewed by Lido’s node-operator contributors and staking-tech contributors. Community Staking Module operators may start earlier, and the node-operator contributors can provide Hoodi stake for testing.
Applicants are asked to post a proposal in the Community Grants / Initiatives forum with their team’s prior work, design and hardware boundary, client compatibility, requested amount, expected testing timeline, licence and maintenance commitment. The LEGO Council aims to decide within two weeks, with input from the node-operator and staking-tech contributors.
Sources
- Original source Lido Governance research.lido.fi
Related stories
- Lido proposes trustless and trusted MEV tracks
- Ethereum Draft Pitches BLS48-581 as a Backup for Validator Signatures
- Ethereum prototype stores an encrypted PIN fingerprint in a smart account
- Preprint proposes one-transaction proofs for Ethereum quantum migration
- Judge acquits Peraire-Bueno brothers in $25M Ethereum case