Agenda
UTC Date & Time
Resources
- Previous call: pqi #028 - Forkcast
- Facilitator email: will@ethereum.org
- Facilitator Telegram: @corcoranwill
- Telegram: PQ Interop — threads:
#general,#devnet-1,#devnet-2,#devnet-3,#devnet-4,#devnet-5,#tooling,#leanVM,#onboarding
High-Level Documents
- Devnet-0 : lean consensus client interop
- Devnet-1 : PQ signature signing & verification
- Devnet-2 : single-layer PQ signature aggregation
- Devnet-3 : aggregator role separation + subnet aggregation
Overview
A. Devnet-3: Implementation Status (Devnet N)
B. Devnet-4: Specification Status (Devnet N+1)
C. Metrics & Observability
D. Schedule / Next Steps
Previous Call Meeting Minutes (Call 28 — Feb 25, 2026)
A. Devnet-3: Implementation Status
Client Readiness
| Client | Implementation | Spec Tests | Interop | Docker | Notes |
|---|---|---|---|---|---|
| Zeam | Interop working. Improved node performance (caching for state transitions). Still debugging checkpoint sync (node rejoining network). | ||||
| Ream | Interop confirmed (tested with 3 clients, Partha tested 5). Fixed checkpoint sync HTTPS issue (swapped Rust library). Ready for long-running Devnet-3. Starting Devnet-4 work. | ||||
| Qlean | Kamil still traveling. | ||||
| Lantern | Interop confirmed (Partha’s testing). Debugging finality issues after slot ~3000 on Devnet-2. Bringing fixes to Devnet-3 branch, new image coming. | ||||
| Ethlambda | Local devnets working (2 Zeam + 2 Ethlambda). Fixed message interop issue. Added attestation committee count CLI param. Built HTML live chain status viewer (fork choice visualization). | ||||
| Lighthouse | No representative on call. | ||||
| Grandine | Still working on Devnet-3, some work remaining before interop. | ||||
| Gean | Completed Devnet-1 (tested locally, leanQuickStart not supporting Devnet-1). Working to catch up to Devnet-3. | ||||
| Nimbus | No representative on call. |
Legend:
Complete |
In progress |
Not started |
Unknown
Devnet-3 Interop Achieved
- 5 clients interoperating (Partha’s testing): Zeam, Ream, Lantern, Ethlambda + leanSpec
- Checkpoint sync: Tested successfully for 5 clients
- Ready for long-running Devnet-3
B. Devnet-4: Specification Status
Spec Progress
- Lead: Anshal (Zeam) — spec work starting, targeting completion by end of week
- High-level doc: To be created in PM repo
SSZ Signature Container Discussion
Question raised (Gajinder): Do we need SSZ container for signatures? Clients don’t hash_tree_root signatures currently.
Resolution:
- Not needed for now — signatures arrive as bytes, no hash_tree_root required
- Signatures separated from attestations in block (unlike Beacon Chain)
- Can proceed with interop without full SSZ container implementation
- Unnawut to set up Docker registry for leanSpec node (publish on merge to main)
ZK-Friendly Encoding Discussion
- Context: Devnet-4 will use recursive aggregation from leanMultisig
- Encoding approach: “Average target sum” encoding (simpler than hypercube)
- Implementation needed: New message hash implementation in leanSig
- Status: Benedict’s paper encoding to be implemented; Emil/Thomas to work on it as time permits
- Not blocking: Anshal can proceed with spec using finalized API
Research Updates
- leanSpec minimal client (Thomas):
- Local interop tests (leanSpec ↔ leanSpec) showing encouraging results
- Wants client teams to test against leanSpec
- Added test vectors for gossipsub, sync, etc.
- leanSpec is Devnet-3 ready
- Poseidon-2 security (Thomas):
- After recent paper on Poseidon-2 improvements/attacks, exploring alternatives
- Evaluating Poseidon-8, Poseidon-1, other hash functions
- Working on Plonky3 framework integration for benchmarking
- Lean VM performance (Emil):
- Modified ISA and compiler
- ~30% improvement in both XMSS and recursion performance
C. Metrics & Observability
Checkpoint Sync Testing (Katya)
5 clients tested successfully- Latest Lantern image working
- Minor fixes shared with Ethlambda team
Dashboards
- Devnet-2: Dashboards merged into single dashboard, leanQuickStart update coming
- Devnet-3: Dashboard PR to merge, will be integrated into leanQuickStart
- Note: Initial Devnet-3 dashboards may be rough — feedback welcome
D. Schedule / Next Steps
- Next call: March 4, 2026 (Wednesday)
- Fort Mode schedule: To be shared in PQ channel this week
Action Items
| Owner | Action | Status |
|---|---|---|
| Anshal (Zeam) | Complete Devnet-4 spec | Target: end of week |
| Anshal (Zeam) | Create Devnet-4 high-level doc + update PM cross-reference | Pending |
| Ream | Start Devnet-4 implementation | Starting this week |
| Lantern | Release new Devnet-3 image with Devnet-2 fixes | This week |
| Ethlambda | Apply minor checkpoint sync fix (from Katya) | This week |
| Unnawut | Set up Docker registry for leanSpec node (auto-publish on merge) | Pending |
| Thomas/Emil | Implement ZK-friendly encoding in leanSig (when time permits) | Ongoing |
| Katya | Merge Devnet-3 metrics PR + update leanQuickStart | This week |
| Gean | Continue catching up to Devnet-3 | Ongoing |
| All clients | Test interop against leanSpec node | Ongoing |
Devnet-3 Long-Running Readiness
| Client | Ready |
|---|---|
| Zeam | |
| Ream | |
| Lantern | |
| Ethlambda | |
| leanSpec |
Meeting Time: Wednesday, March 04, 2026 at 14:00 UTC (60 minutes)