# SSV Anchor Client on Hoodi Testnet Performance Update **URL:** \ **Category:** Node Operators\ **Created:** [May 4, 2026, 2:08pm UTC](https://research.lido.fi/t/ssv-anchor-client-on-hoodi-testnet-performance-update/11537 "2026-05-04T14:08:37Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![snk999](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/snk999/32/5067_2.png) [@snk999](https://research.lido.fi/u/snk999)\ **Post date:** [May 4, 2026, 2:08pm UTC](https://research.lido.fi/t/ssv-anchor-client-on-hoodi-testnet-performance-update/11537/1 "2026-05-04T14:08:37Z")
## **Summary** This update shares the results of a two-month performance evaluation of the [Anchor SSV](https://anchor-book.sigmaprime.io/) client (built by Sigma Prime) on the Hoodi testnet. Based on strong performance results, it is suggested that Anchor can be used by operators in mainnet SSV clusters within the Simple DVT Module, as well as the Curated Module (assuming Node Operators run a testing environment on Hoodi). ## **Background** Anchor is an independent, Rust-based implementation of the SSV protocol, developed by Sigma Prime on the foundations of their Lighthouse Ethereum consensus client. It is the second SSV client, introduced to bring multi-client diversity to the SSV network. Anchor’s continued development is backed by a long-term commitment from the SSV DAO under [DIP-56](https://snapshot.org/#/s:mainnet.ssvnetwork.eth/proposal/0xc85cfa3a06fcb92fc111e1bed1088c1c036b05e49a2e22e42d4fe6899bb10854): a two-year agreement between the SSV Foundation and Sigma Prime providing $2.5M for continued maintenance and strategic development of Anchor through 2026–2027, covering protocol upgrades, feature work, and community support. This support ensures that Anchor is not a one-off grant-funded release but a supported, actively maintained second client, with a dedicated Sigma Prime team responsible for keeping it stable and feature-complete. Anchor has also undergone a [security audit](https://drive.google.com/file/d/1VULtCy5PDm41tSKchp1QUxZVO_8eJ4sL/view?usp=drive_link) by a third-party firm, with the findings published by Sigma Prime. SSV-based setups currently power more than[18% of the Ethereum validator set](https://explorer.rated.network/?network=mainnet&view=pool&timeWindow=1d&page=1&pageSize=15&poolType=all) (per [Rated Network](https://explorer.rated.network/o/SSV?network=mainnet&timeWindow=1d&idType=pool)), so improving resilience at the SSV client layer directly strengthens the fault tolerance of the Lido validator set across the Simple DVT and Curated Modules. ## **Performance Data** The performance monitoring period ran from February 1 to March 31, 2026, across two Lido x SSV clusters on Hoodi: **Dauntless Diplodocus** (mixed: Anchor + SSV Labs Go client, 96 validators) and **Mighty Megalosaurus** (fully Anchor, 98 validators), totalling 194 validators. During this time, the fully-Anchor Mighty Megalosaurus cluster averaged **99.96% uptime** , **83.62% attester effectiveness** , and a **100% block proposal success rate** (32/32). The mixed Dauntless Diplodocus cluster averaged **96.54% uptime** , **78.42% attester effectiveness** , and also achieved a **100% block proposal success rate** (20/20). Both clusters comfortably exceeded the Hoodi 30-day network average attester effectiveness of **73.75%**. These results are reinforced by Anchor’s mainnet track record to date, all verifiable by validator index on beaconcha.in. Sigma Prime runs four of its own SSV operators on mainnet as a production-grade test of Anchor (operators 2042–2045, covering 10 validators in total), and these have a **99.90% mean lifetime BeaconScore** , with 9 of the 10 validators at a perfect 100.00%. Beyond Sigma Prime’s own setup, SSV operator 688 has also been running Anchor on mainnet across 20 validators, with a **99.75% mean lifetime BeaconScore** and 14 of those 20 validators at a perfect 100.00%. ## **Conclusion** Given these results, Anchor can be considered a viable client option on mainnet for SSV-based setups within Lido, alongside the existing SSV Labs Go client. For Simple DVT clusters, operators interested in switching to Anchor should coordinate with Simple DVT coordinators as part of any client change and flag it within their cluster thread. For the Curated Module, the same recommendation applies, with the additional expectation that node operators first validate Anchor in their own Hoodi testing environment before running it on mainnet, and coordinate the change with the Lido NOM team in advance. ---
**Author:** ![cronky4](https://avatars.discourse-cdn.com/v4/letter/c/90ced4/32.png) [@cronky4](https://research.lido.fi/u/cronky4)\ **Post date:** [May 7, 2026, 8:12am UTC](https://research.lido.fi/t/ssv-anchor-client-on-hoodi-testnet-performance-update/11537/2 "2026-05-07T08:12:00Z")
> [@snk999](#): > > Anchor has also undergone a security audit by a third-party firm Who is the third-party firm? ---
**Author:** ![BlockShane](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/blockshane/32/6896_2.png) [@BlockShane](https://research.lido.fi/u/BlockShane)\ **Post date:** [May 8, 2026, 6:52pm UTC](https://research.lido.fi/t/ssv-anchor-client-on-hoodi-testnet-performance-update/11537/3 "2026-05-08T18:52:23Z")
hi, BlockShane here from the anchor team. Really grateful for @snk999’s write up! quick reply that the security audit was performed by Sigma Prime’s information security services team. Hope that clears things up : )