Vero

Vero is a multi-node validator client designed to protect validators from client bugs. It does this by cross-checking the blockchain state across multiple client implementations before submitting attestations.

Vero works on both Ethereum and Gnosis Chain, and is compatible with all CL and EL clients.

Documentation

Docs are available at vero.docs.serenita.io.

Contributing

Contributions are welcome! See CONTRIBUTING.md for more details.

Resources

A selection of talks, articles, and community resources for learning more about Vero:

• Guides
  • Eth Docker: Running Vero with three client pairs
• Presentations
  • EthClient Summit 2025: When Clients Disagree: Picking a Side Safely
  • EthStaker's Staking Gathering 2025: Improving Ethereum's Resilience With Multi-node Validator Setups
  • EthCC 2025: Improving client diversity with Vero
  • Lido Node Operator Community Call #22: Improving Client Diversity with Vero
  • EthStaker's Community Call #56: Vero
• Questions
  • Telegram
  • Discord (invite-only)
• Workshops
  • Dappcon 2025: Protecting Validators From Client Bugs Using Vero

Acknowledgements

We'd like to acknowledge the work of all teams that helped shape Vero, including:

• Ethereum and Gnosis Chain client teams, researchers and everyone else working on these public goods
• @protolambda and his Python SSZ implementation
• Kurtosis and their contributions to ethereum-package
• The EF DevOps team and their continued work on amazing tooling like ethereum-package which helped thoroughly test Vero before launching it on testnet