PQ Interop #038
Transcript
Ask about this call
Answered from this call's summary and transcript only.
AI-generated — verify against the recording.
Call summary
Targets
- •End of next week - Goldfish finality gadget breakout session — 01:09:01
Decisions
- •Devnet 5 ships PQ recursive aggregation first; Goldfish consensus optional — 01:06:40
- •Freeze spec changes after Goldfish integration to focus on stability testing — 01:13:10
Highlights
- Devnet 5 Scope:
- ·Devnet 5 goal: single recursive proof per block via Type 1/2 aggregation — 00:58:37
- ·PQ testing prioritized over consensus mechanism changes — 01:00:08
- ·Type 1/2 signature APIs mostly finalized; helper function needed from LeanVM — 01:05:04
- ·PQ roadmap acceleration possible; real-world testing urgent priority — 01:12:23
- Client Progress:
- ·Zeam optimizing aggregator performance and payload re-aggregation API — 00:16:46
- ·Goldfish incompatible with 3SF; finality gadget research needed — 00:18:25
- ·LeanStart tool enables single-command Kubernetes devnet deployment — 00:47:03
- ·Ethlambda added LibP2P Identify Protocol support for Zeam interop — 00:52:01
- Performance Benchmarks:
- ·Lean signature performance flat across modern 4+ core CPUs — 00:32:04
- ·Aggregation scales linearly to 16 cores; 32+ cores show diminishing returns — 00:33:08
- ·XMSS signing optimization dropped time from 200ms to 5ms — 00:36:23
- ·1,000 validators achievable in current slot timing; 10,000 possible with adjustments — 00:42:09
- Testing Infrastructure:
- ·Hive UI redesigned with grid view for easier test result navigation — 00:21:41
- ·Lean spec test vectors integration into Hive in progress — 00:31:41
- ·Observatory site running stable for weeks with devnet visualizations — 00:56:56
- ·LeanBench benchmark harness automated across GCP instance types — 01:09:10
Action Items
- •Anshal — Raise spec PR for recursive proof aggregation with Type 1/2 signatures — 01:05:04
- •Gajinder/All teams — Schedule Goldfish breakout call for finality gadget discussion — 01:08:25
Meeting chat39
- Mega | Lambda
Looks great!!
- unnawut
Reacted to "Looks great!!" with ❤️
- T. Wambsgans
thats interesting
- T. Wambsgans
idk why
- T. Wambsgans
good info, thanks a lot
- T. Wambsgans
correct
- Parthasarathy Ramanujam
I think 200ms is optimistic as we are not in the same datacenter.
- Parthasarathy Ramanujam
Cool benchmarks.
- T. Wambsgans
Reacted to "Cool benchmarks." with 👏
- Yann Vonlanthen
How are the budget constants chosen? Or are they just placeholders right now?
- Shariq Naiyer
- T. Wambsgans
for info: it works nice on my safari, but not on my firefox (macos)
- unnawut
Replying to "How are the budget c..." Just placeholders, based on the values we use in the past devnets
- Yann Vonlanthen
Replying to "How are the budget c..." Thanks!
- Yann Vonlanthen
Reacted to "Just placeholders, b..." with 👍
- unnawut
Replying to "for info: it works n..." Bench right? Thanks! I’ll have a look
- T. Wambsgans
Replying to "for info: it works n..." will send screenshot on TG
- unnawut
Reacted to "will send screenshot..." with ❤️
- Parthasarathy Ramanujam
The script does that.
- Gajinder Singh
ansible is deployed from a master
- Parthasarathy Ramanujam
lean-quickstart had support for k8s as well. We just deferred full implementation for later
- Shariq Naiyer
Reacted to "lean-quickstart had ..." with 🔥
- unnawut
Reacted to "Thanks!" with ❤️
- Gajinder Singh
problem with k8s is that it runs its own network layer if you wanna run it in multiple nodes, which might be prohibitive to have closer to real network conditions even if nodes are across data centers for k8s its priamarily ansible vs k8 tradeoff and ansible might allow a per node management better than k8 although it can also be done in k8s so in the end its more about what people are well versed with
- unnawut
Reacted to "problem with k8s is ..." with 👍
- Gajinder Singh
Replying to "problem with k8s is ..." (disclaimer: I run multiple node k8s for personal stuff, so I do know a bit about its admininstration)
- Gajinder Singh
Replying to "problem with k8s is ..." nodes = machines in k8s lingo
- unnawut
Reacted to "I think 200ms is opt..." with 👍
- Shariq Naiyer
Reacted to "problem with k8s is ..." with 👍
- Yann Vonlanthen
100% agree!
- Shariq Naiyer
Replying to "problem with k8s is ..." interesting I am going to look into this tradeoff further I haven’t used ansible as much yet
- Gajinder Singh
Replying to "problem with k8s is ..." your work is quite redundant in that regard to be honest, we should coordinate on how to maximise useful work
- Gajinder Singh
Replying to "problem with k8s is ..." although good work
- T. Wambsgans
I am going to send a msg in TG @Anshal
- Anshal
Reacted to "I am going to send..." with 👍
- Yann Vonlanthen
I think switching to Goldfish makes sense only if it simplifies things, if you feel like it doesn’t, I wouldn’t make it a priority at all
- Gajinder Singh
Replying to "I think switching to..." we wanna devnet the PQ heartbeat for mainnet, so that is the target we should go for in terms of consensus
- Yann Vonlanthen
Reacted to "we wanna devnet the ..." with 👍
- unnawut
Reacted to "we wanna devnet the ..." with 👍
Key decisions
Devnet 5 ships PQ recursive aggregation first; Goldfish consensus optional
Devnet 5Prioritizing post-quantum recursive aggregation for the Devnet 5 scope while making Goldfish consensus an optional component.Freeze spec changes after Goldfish integration to focus on stability testing
Establishing a protocol specification freeze following the integration of Goldfish to shift focus toward stability and performance testing.