EIPsInsight

Loading Experience

Preparing your insights...

Loading0%
PQI2026-05-20_040

PQ Interop #040

2026-05-20 3 decisions 421 transcript lines

Transcript

Ask about this call

Answered from this call's summary and transcript only.

AI-generated — verify against the recording.

Call summary

Targets
  • Tomorrow: Zeam to open PRs for aggregate coverage and proposer aggregation metrics — 00:27:41
  • 1–2 months: lean spec ready for broader review by beacon client teams and EF — 00:47:27
Decisions
  • Spec freeze: no major new features added while teams stabilize DevNets — 00:17:34
  • Keep conservative XMSS parameters for now; revisit main branch only if performance is an absolute blocker — 00:37:10
  • Stabilization target: finality with 1K validators across clients before advancing the spec — 00:45:58
Highlights
  • Devnet Status:
    • ·DevNet 5 spec merged: single proof posted per block on-chain — 00:17:16
    • ·DevNets fail with >2 subnets; P95 aggregation is 4s vs 0.8s slot interval — 00:19:26
    • ·DevNet 4/5 branch is 3x slower than main branch due to conservative XMSS parameters — 00:28:50
    • ·8-core aggregator hardware identified as insufficient; 16-core minimum recommended — 00:38:14
  • Client Updates:
    • ·Ethlambda has working EL integration via engine API; demo shown running with ethrex, Nethermind, Geth, Erigon, Nimbus, Besu — 00:45:09
    • ·Ethereum-package updated to support lean clients (lambdaclass/ethereum-package PR #19) — 00:49:01
  • Research And Spec:
    • ·Plonky3 optimization PRs merged; full benchmarking suite for WEER and new Monolith arithmetization added — 00:13:24
    • ·Lean spec stabilization underway; discv5 removed; plan to solicit feedback from beacon client teams and EF — 00:15:26
    • ·Thomas presenting post-quantum consensus for Ethereum at a Zurich research conference this week — 00:17:09
  • Technical Blockers:
    • ·Main XMSS branch is faster but uses unproven security parameters; decision deferred — 00:36:01
    • ·Block production (not just aggregation) suspected as root cause for >2 subnet failures — 00:38:57
    • ·Multi-subnet topology may require an additional ~1–1.2s aggregation interval — 00:43:03
Action Items
  • Gajinder Singh / Zeam — Zeam to upstream aggregate coverage and proposer aggregation metrics to lean spec by tomorrow — 00:47:05
  • Mega | Lambda — Ethlambda to PR block-building improvements to lean spec for cross-team benefit — 00:45:13
  • Emil (T. Wambsgans) / Parthasarathy Ramanujam — Determine minimum hardware spec for aggregators (target: next call) — 00:34:37

Meeting chat17

  • Mercy Boma Naps-Nkari

    +===============================================================+ CHAIN STATUS: Current Slot: 613 | Head Slot: 612 | Behind: 1 +---------------------------------------------------------------+ Connected Peers: 30 +---------------------------------------------------------------+ Head Block Root: 0x6e178f90ad457e6a612800e901d723146bceb65b77ea9ada51204b3d6d462306 Parent Block Root: 0xbb6a3823f595f2f12d3e6425c8b9aa0828bf5358686f97af90075d3000a54b13 State Root: 0xcd85a742eb3d47fb193932371f747711842aa3add92dd648cad3aac1df7c3da9 Timely: NO +---------------------------------------------------------------+ Latest Justified: Slot 608 | Root: 0x5e7001d8f9fc4f85393e6d24700ab02efd03bf8cc0d216b13b77629854651550 Latest Finalized: Slot 607 | Root: 0x1102a2e2f02fd59825505951a37dcf1d898ade3b0b12d01e68084c90c219291e +===============================================================+

  • Parthasarathy Ramanujam

    Nlean is by Kai (not by Nimbus)

  • Kamil Salakhiev

    what clients support shadow? I may try to test ~64 nodes under realistic networking conditions

  • Shariq

    We’ll aim to address the per client aggregator stability on Hive as well.

  • Gajinder Singh

    Replying to "what clients support..." zeam should as Kai has been maintaining this

  • Gajinder Singh

    Replying to "what clients support..." will ask him to assist you in shadow runs

  • Parthasarathy Ramanujam

    Reacted to "We’ll aim to address..." with 👍

  • Iván | ethrex

    https://lean.devnet4.ethlambda.xyz

  • Iván | ethrex

    The PR adding support for Lean Ethereum to ethereum-package https://github.com/lambdaclass/ethereum-package/pull/19. Instructions to run both only Lean client local devnets and Lean clients + ELs can be found in the PR description

  • Iván | ethrex

    If you want to test you client against ELs you’d just need to implement communication and then you can use the Kurtosis/ethereum-package to deploy your devnet

  • Pablo Deymo | Lambda

    PR 367 https://github.com/lambdaclass/ethlambda/pull/367

  • Iván | ethrex

    Reacted to "PR 367 https://githu..." with 👍

  • Gajinder Singh

    Replying to "PR 367 https://githu..." great work overall!

  • Pablo Deymo | Lambda

    Reacted to "great work overall!" with ❤️

  • Pablo Deymo | Lambda

    Replying to "PR 367 https://githu..." thanks

  • Pablo Deymo | Lambda

    Replying to "PR 367 https://githu..." We think the PR could be polish a lot

  • Mega | Lambda

    The PR is big right now, but it can probably be simplified a lot

Key decisions

  • Spec freeze: no major new features added while teams stabilize DevNets

    teams need to stabilize DevNets before adding new features
  • Keep conservative XMSS parameters for now; revisit main branch only if performance is an absolute blocker

    performance issues would require a revisit of the main branch
  • Stabilization target: finality with 1K validators across clients before advancing the spec

    spec will be advanced only after achieving finality with 1K validators