SSZ2026-08-28_004
SSZ Engine API #004
2026-08-28 4 decisions 232 transcript lines
Transcript
- Tamaghna Chourdhuri
Ill start at 2:35
Call summary
Targets
- •SSZ Engine API DevNet compatibility testing — folded into existing fork DevNet (no separate DevNet planned) - 00:11:31
Decisions
- •SSZ Engine API to ship as opt-in/experimental for Glamsterdam; mandatory for Hegota - 00:22:07
Highlights
- Testing:
- ·EL-side SSZ Engine API tests in progress (execution-specs); ~1 PR/week cadence due to review bottleneck; no CL engine test suite yet - 00:18:27
- Ssz Engine Api Spec:
- ·Agenda: merge SSZ Engine API PR, then follow-up PR for progressive types; HTTP/2 vs 1.1 deferred (key attendees absent) - 00:05:37
- ·Łukasz: favor merging spec now (optional/experimental), with JSON RPC fallback; refine later post-DevNet validation - 00:10:36
- ·Proposed rollout: opt-in/experimental for Glamsterdam, mandatory for Hegota; each EL exposes disable flag - 00:22:07
- ·Risk flagged: keeping SSZ secondary creates pressure to design JSON-friendly API shapes incompatible with SSZ encoding - 00:26:03
- Implementation Status:
- ·Łukasz: running agent against Nethermind impl vs spec; found minor inconsistencies; will post fixes to spec PR and Nethermind PR - 00:20:57
- ·Sameer (Lighthouse): SSZ Engine API working on Fulu with Erigon on local Kurtosis devnet; also testing with ethrex, looking good - 00:33:18
- ·Cross-client compatibility gap noted: single-EL testing insufficient; spec + tests needed to iron out inter-client differences - 00:33:41
Action Items
- •Tamaghna Chourdhuri - Raise SSZ Engine API PR merge + DevNet schedule on Monday ACDT; seek reviews from all client teams - 00:15:47
Key decisions
SSZ Engine API to ship as opt-in/experimental for Glamsterdam; mandatory for Hegota
Defined the rollout strategy for the SSZ Engine API across upcoming network upgrades.HTTP/2 vs 1.1 deferred (key attendees absent)
Decision on transport protocol version postponed due to missing stakeholders.Merge SSZ Engine API spec as optional/experimental with JSON RPC fallback
Decision to proceed with merging the specification to facilitate further refinement and validation post-DevNet.SSZ Engine API DevNet compatibility testing — folded into existing fork DevNet (no separate DevNet planned)
Decision to integrate testing into existing infrastructure rather than creating a dedicated DevNet.
AI Disclaimer: Some content or metadata on EIPsInsight may be AI-inferred or automatically compiled. If you find any discrepancy, please contact us at dev@avarch.org.