Hi all, closing out the PERCH evaluation. The one-month Hoodi measurement window ran from 17 September to 15 October with six curated module operators participating: P2P, Rocklogic, Ebunker, Stakefish, HashKey Cloud and Stakely. Below is the fleet-level summary.
Short version: the gateway ran alongside existing setups for the full window without incident, blocks reached Lido nodes 407 ms sooner over mump2p than over public libp2p across the four weeks, and wrong head votes fell 45% against the June control week, with Lido holding well below the Hoodi network’s wrong head rate in every week.
What the Hoodi test was designed to show
That the mump2p gateway runs stably alongside libp2p and your existing validator setup, with no changes to client software, keys or consensus logic, and no added slashing risk. Alongside stability, we tracked two performance reads. The first is block arrival: whether blocks reach your nodes earlier via mump2p than over public libp2p. The second is the on-chain outcome that late block arrival most directly affects: wrong head votes. A wrong head vote is an attestation that voted for a head which turned out not to be canonical, because the block arrived too late to be seen.
How it was measured
- 267 of 307 Lido validator keys on Hoodi across the six operators. Only keys active in both the control and treatment windows with at least 95% duty coverage are counted, so the comparison is like for like.
- Control: 16 to 23 June, before any gateway was connected. Treatment: four consecutive weeks, 17 September to 15 October, with gateways connected.
- Attestation outcomes come from on-chain data via Xatu and are reported at the fleet level, aggregated across participating operators, as agreed when the window opened. With roughly 15 keys per operator on Hoodi (0x02 keys), per-operator numbers are too thin to read.
- Wrong head rates are also shown relative to the full Hoodi validator set over the same windows. Hoodi’s network-wide rate moved a lot between June and October, so the relative read matters as much as the raw one.
- Block arrival compares timing at the mump2p gateways against public Xatu sentry nodes over the same slots. Each operator can check this independently against their own gateway metrics in Grafana.
Block arrival (17 September to 15 October, 180,327 slots measured)
- Blocks arrived 407 ms sooner over mump2p than public libp2p: p95 arrival from slot start 1,614 ms to 1,207 ms (-25%). The weekly lead ranged from 382 to 420 ms, so the result held steadily across the window.
- Propagation spread 6.6x tighter: p95 minus first arrival 463 ms to 70 ms
- Late blocks (p95 arrival after 4 s) 5.8x fewer: 1.97% of slots to 0.34%
- 71% of slots were accelerated by mump2p, measured at 16 mump2p gateways against 24 to 31 public Xatu sentries per week
Attestation outcomes (17 September to 15 October)
- Wrong head votes down 45% against the control week: 0.847% to 0.469% of attested head votes. Every treatment week came in below the control: -79%, -62%, -12%, -26%.
- Relative to the network: Hoodi’s own wrong head rate fell from 2.18% in June to between 0.54% and 1.98% across the four treatment weeks, so part of the drop reflects the network itself. Netting that out, Lido sat at 0.39x the network rate in June and 0.40x across the window (0.34x, 0.44x, 0.52x, 0.32x by week) - consistently around 60% below the network.
- Wrong head votes on canonical slots, the category mump2p targets most directly, fell 60% on a weekly average against the control (3,123 to 1,264), and between 35% and 82% in any given week.
- Missed block proposals fell from 14.5% (46 of 317) in the control week to 2.0% (36 of 1,804) across the four weeks. Proposal outcomes on Hoodi are heavily shaped by network conditions, so this is shown for context rather than as a mump2p effect.
Reading the results
- Hoodi’s network conditions swung widely over the window, with the network-wide wrong head rate ranging from 0.54% to 1.98% week to week. That is why the fairer read is Lido relative to the network. On that read, Lido held its position at around 0.4x rather than pulling further ahead.
- Gains narrowed after week 2. Lido’s wrong head rate was 0.18% and 0.32% in weeks 1 and 2, then 0.74% and 0.63% in weeks 3 and 4, tracking the network’s own deterioration in those weeks. Missed proposals edged up from 1.3% to 2.9%, still well below control. Single weeks on Hoodi should be read with caution for this reason.
- Late inclusions behind non-canonical slots, which mump2p does not address, ran 14% to 32% above control.
- Taken together, the Hoodi phase shows the integration works and carries no operational risk, with a directional signal that block propagation and head-vote outcomes improve. The clearer performance read comes from mainnet, where network conditions are stable enough to measure it.
- Hoodi results should not be read as a forecast of mainnet performance. The testnet is small, conditions are noisier, and the absolute figures are not comparable.
- On stability: the gateway ran alongside existing setups for the full window with no changes to validator software, keys or consensus logic, and no slashing events.
What’s next
- The Lido team is reviewing the report. Any next steps for Lido delegated stake will be coordinated with Lido once that review is complete.
- Participating operators are welcome to keep their gateways running in the meantime - nothing changes on your side.
- Thank you to everyone who connected keys and kept us posted on changes to your setups.



