Establishing the APM Committee

Proposals
21

mev-commit (Primev) Testing Results

We’ve concluded the mev-commit testing phase, as described in the APM Decision.
Over the past weeks, Lido validators opted into Primev’s mev-commit network on the Hoodi testnet. Below is a concise summary of the most relevant findings from (1) Primev’s published results and (2) our internal performance analysis.

Key Results
During the Hoodi testnet phase, ~16,000 Lido validators opted into Primev’s mev-commit network across 8 operators. Adoption came in waves, with a large batch (~10k validators) onboarded in early December.

Primev-reported metrics (shared with Lido team):

  • 0 slashing events
  • 0.53% missed proposal rate (8/1,506 blocks)
  • 98.5% active-online rate
  • 93.8% clean-day rate

Lido internal analysis confirms:

  • ~99.84% average uptime across clusters
  • 98.9–100% proposal success per operator
  • 99.55% overall proposal success
  • No operator-specific degradation linked to mev-commit

Even under elevated testnet missed-slot conditions, Lido clusters maintained strong proposer performance.

Overall Assessment
Combining Primev’s reported metrics with our internal validation:

  • No slashing observed
  • Missed proposals remain extremely low
  • Uptime and attestation performance remain within normal ranges
  • No cluster-specific performance degradation
  • Rewards distribution successfully tested

Under Hoodi testnet conditions, mev-commit integration appears operationally stable and technically compatible with Lido’s validator set.
Further mainnet validation would be required to assess long-term revenue impact and latency sensitivity under real economic load, but the testing phase does not surface material technical blockers.
Thus, I am recommending the inclusion in the APM Allow List.

22

Hi @Gabriella_S, @cnupy

We’re looking to work on one of the Commit-Boost PBS follow-up areas mentioned by the APM Committee; particularly post-audit change review, broader client compatibility/regression testing, or direct Docker support.

Please, before we start working on it, we would like to confirm whether any of these are still outstanding and not already being handled. If there’s a specific gap the Committee would find useful for us to take on, a brief pointer on the expected scope would be very helpful. Thank you!

23

At the moment, we don’t have a need for further assistance on the committee. Thank you for the offer; we can revisit this at a later date if it makes sense.

1 Like