Post-Quantum (PQ) Interop #38, May 6, 2026

Protocol Calls & happenings
1

Agenda

Meeting Time: Wednesday, May 06, 2026 at 14:00 UTC (60 minutes)

GitHub Issue

2

Meeting Summary:

The Post-Quantum Interop meeting #38 focused on updates and planning for DevNet 5, with discussions centered around improving client interoperability and scaling capabilities. Gajinder reported on Zoom’s work optimizing their client aggregator and exploring Goldfish consensus mechanisms, while Derek demonstrated new improvements to the Hive UI for better test visualization and results tracking. Unnawut presented benchmarking results from LeanBench, showing performance scaling for different CPU configurations and recommending maximum 16-32 cores for optimal performance. Shariq shared progress on running stable DevNets using Kubernetes-based tools called Lean Start, focusing initially on three clients (Reem, Zeeam, and ETH Lambda) to achieve better debugging and stability. The team discussed the priority of implementing DevNet 5’s single proof per block mechanism using Type 1 and Type 2 aggregation before addressing consensus protocol changes, with Anshal confirming the API specifications were nearly complete. Thomas emphasized the importance of testing Post-Quantum (PQ) attestation capabilities as a top priority, suggesting they could temporarily use 3SF Mini while working toward a potential future implementation of Goldfish.

Click to expand detailed summary

Gajinder provided updates on Zoom’s client optimization efforts, including work on parallelizing flows and resolving performance bottlenecks. The team is also exploring payload aggregation specifications and investigating Goldfish’s compatibility with 3SF, noting that they need a finality gadget that runs independently from the availability protocol to enable proper node pruning and caching. The discussion will continue later in the call with Yann regarding these research findings.

The team discussed improvements to the Hive UI for testing and monitoring dev nets. Derek demonstrated a new grid view interface called “Lean Latest” that provides a more digestible way to see test results across different clients, showing pass/fail status and allowing easy navigation to logs and failure details. The team is still working on integrating lean spec test vectors, with Kolby handling that implementation. Shariq explained that these improvements help optimize dev net resources by allowing teams to identify compatible clients before deployment.

The team discussed updates and plans for DevNet 5, focusing on implementing a single proof per block and testing PQ (Provable Quantum) attestation. Unnawut presented benchmarking results from LeanBench, which showed that performance scales linearly with modern CPUs up to 16 cores, with 32 cores showing diminishing returns. The team agreed to prioritize implementing PQ attestation before finalizing the consensus mechanism, potentially using Goldfish instead of 3SF Mini. Anshal confirmed that the API specifications for DevNet 5 are nearly complete and ready for a PR. The group decided to schedule a breakout call next week to discuss the consensus mechanism details, particularly regarding finality gadgets and fork choice rules. Shariq shared progress on stabilizing clients in DevNet 4, running tests with Reem, Zim, and ETH Lambda, and noted that ETH Lambda is not reaching finalization while the others are. The team also discussed the importance of testing PQ attestation with growing numbers of validators to support potential acceleration of the PQ roadmap.

Next Steps:

  • Anshal: Open a PR on LeanSpec for recursive proof aggregation with type 1 and type 2 signatures for DevNet 5
  • Emil: Complete integration work on LeanSec with prod and test config signatures so Anshal can update bindings
  • Emil: Build helper function to extract proof for a particular message based on index
  • Gajinder and team: Schedule a breakout call for next Thursday or Friday to discuss Goldfish and finalization mechanism (after Thomas and Emil return from Rome)
  • Anshal: Add helper functions on specs side and client implementation side for DevNet 5 single block proof
  • Kolby: Complete work on integrating lean spec test vectors into Hive
  • Derek: Add legend to client interop grid view and fill empty gaps with clients testing against themselves
  • Derek: Add scoring display to the main Hive page for easier visibility of test results

Recording Access:

3

YouTube recording available: https://youtu.be/RWmlIA4Gu4I