Note: Donations made to Protocol Guild are distributed among Ethereum protocol contributors, including client teams. All recipients and splits can be seen here.
+Note: Donations made to Protocol Guild are distributed among Ethereum protocol contributors, including client teams. All recipients and splits can be seen here.
+Note: Donations made to Protocol Guild are distributed among Ethereum protocol contributors, including client teams. All recipients and splits can be seen here.
+ +| Client | +Github | +Docs | +Chat | +Status | + +Language | + +|||||
|---|---|---|---|---|---|---|---|---|---|---|
| + {%- if client.link -%} + + {{client.name}} + + {%- else -%} + {{client.name}} + {%- endif -%} + | + {%- if client.github -%} ++ + {{site.data.icons.github}} + + | + {%- else -%} +- | + {%- endif -%} + {%- if client.docs -%} ++ + {{site.data.icons.docs}} + + | + {%- else -%} +- | + {%- endif -%} + {%- if client.chat -%} + {%- assign chat_icon = site.data.icons.chat -%} + {%- if client.chat contains "discord" -%} + {%- assign chat_icon = site.data.icons.discord -%} + {%- endif -%} + {%- if client.chat contains "t.me" -%} + {%- assign chat_icon = site.data.icons.telegram -%} + {%- endif -%} ++ + {{chat_icon}} + + | + {%- else -%} +- | + {%- endif -%} + {%- if client.status -%} +{{client.status}} | + {%- else -%} +- | + {%- endif -%} + + {%- if client.lang -%} +{{client.lang}} | + {%- else -%} +- | + {%- endif -%} + +
| Feature / Property | ++ Vero + | ++ Vouch + | +
|---|---|---|
| Attestation Strategies | +M of N | +M of N, First, Best | +
| Signer | +Web3Signer | +Dirk | +
| Distributed Validator Keys | +No, uses whole key | +Yes, uses sharded keys | +
| Active-active Redundancy | +Vero Sponsors only | +Yes | +
| Ethereum Remote Signing API | +Yes | +No | +
| Slashing Protection | +Yes | +Yes | +
| Slashing Detection | +Yes | +No | +
| Ease of Migration | +Designed for simple adoption and rollback | +More complex setup and integration | +
| Eth Docker Support | +Yes | +Yes | +
| Open Source | +Yes | +Yes | +
| Dependency Surface | +Minimal codebase and external dependencies; single maintainer | +Large/complex codebase (~5x Vero) and external dependencies; creator retired, codebase maintained by Bitwise | +
| Typical Use Case | +Simple way to protect validators from client consensus bugs | +Highly-configurable multi-node validator setups with sharded validator keys | +
Multinode validator clients provide protection against client bugs that can cause validators to vote for an invalid fork of the chain. They do so by combining data from multiple consensus and execution clients, requiring M-of-N connected clients to agree before casting their vote.
+ +When one client diverges or behaves inconsistently, the validator client continues operating through the rest of the clients as long as M of them agree on which fork to vote for. This way a defect or downtime in any single client does not disrupt validation activity.
+ +This approach protects both the operator and the Ethereum network by reducing correlated failures, lowering risks during consensus bugs and improving overall resilience.
+ +See the Multinode Clients section to understand if Vero or Vouch is better for you. Under most situations Vero will cover 99% of usecases including institutional staking operations.
+For an automated tool (with a GUI) to switch execution clients,
see Accidental-Green's Ethereum Client Switcher