PQI2026-04-22_036
PQ Interop #036
2026-04-22 2 decisions 219 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
- •Next week - DevNet 5 features discussion and spec updates — 00:35:56
- •Next few days - Fort Mode recordings published with improved audio — 00:41:25
Decisions
- •Use 'Lean Fork' naming instead of DevNet 4/5 versioning in spec — 00:27:03
- •Postpone DevNet 5 discussion to next week; prioritize DevNet 4 stability — 00:36:51
Highlights
- Spec Updates:
- ·Fork protocol inherent system proposal for spec modernization under review — 00:22:11
- ·Agreement to use single 'Lean Fork' instead of DevNet versioning — 00:27:03
- ·Ongoing: Plonky3 sum check optimization, Bitcoin hash function adaptation — 00:31:29
- ·Sum check variable reversal improves padding and packing friendliness — 00:32:47
- Client Updates:
- ·Ream added Q-Lean, Grandine to Hive; integrating test fixtures — 00:13:22
- ·Coolin added DevNet 4 metrics, aggregator switch API, validator support — 00:14:10
- ·Lantern added aggregator endpoint, DevNet 4 metrics; fixed bug — 00:14:59
- ·East Lambda improved aggregator 3X via compilation target change — 00:16:05
- ·Gean raised Hive PR; implemented pending attestation buffering — 00:17:05
- ·Grandine added Hive support, aggregator toggle API — 00:18:05
- ·Zim integrated Hive into daily CI; working on fork choice pruning issues — 00:19:00
- Organizational:
- ·DevNet 5 discussion postponed to next week; focus on DevNet 4 stability — 00:35:13
- ·Fort Mode takeaways: increased testing, right-sizing client participation — 00:39:37
- ·Fort Mode recordings ready within days with improved audio/captions — 00:41:25
- Testing Progress:
- ·Major test vector additions to spec covering networking, SSZ, signatures — 00:21:17
- ·Multiple subnets testing prioritized to test all aggregators simultaneously — 00:32:50
Action Items
- •All client teams — Add all new spec test vectors to client test suites — 00:33:27
- •All teams — Discuss DevNet 5 feature list async in Telegram DevNet 5 channel — 00:35:56
Meeting chat2
- Parthasarathy Ramanujam
My mic isnt working
- Parthasarathy Ramanujam
sorry
Key decisions
Use 'Lean Fork' naming instead of DevNet 4/5 versioning in spec
Agreement to use a single 'Lean Fork' name for spec modernization instead of versioning based on DevNet numbers.Postpone DevNet 5 discussion to next week; prioritize DevNet 4 stability
Decision to focus on the stability of the current DevNet 4 before planning features for DevNet 5.