kalidou.dev

Ethereum Foundation: PSE — pse.dev

Frontend engineer for the Ethereum Foundation's Privacy & Scaling Explorations team (2023 to 2025): built pse.dev, the team's project hub and blog, and a shared design system used across PSE properties.

Role
Frontend Engineer
Stack
React, Next.js, TypeScript, Tailwind CSS
Year
2025

Context

Privacy & Scaling Explorations (PSE) is the Ethereum Foundation team exploring zero-knowledge cryptography and privacy infrastructure. Its output is research: papers, protocols, and libraries. From 2023 to 2025 I was the frontend engineer responsible for the surfaces through which that research reaches developers, starting with the team's front door: pse.dev.

Problem

ZK research is hard to discover and harder to adopt. PSE ships dozens of projects across multiple languages and maturity levels, and needed a coherent public home that stayed accurate as a research team's fast-moving portfolio changed.

What I built

pse.dev: primary frontend engineer for the team's project hub and blog, 450+ commits in privacy-ethereum/pse.dev. The site indexes every PSE project with structured metadata, research posts, and ecosystem resources.

A shared design system and component library across PSE properties, so each new project site starts from a working system rather than a blank page. That foundation carried into the individual project sites I owned — ZK-Kit, Bandada, Anon Aadhaar, and jubmoji.quest — and into the Privacy on Ethereum section of ethereum.org.

Key decisions

  • A shared component library across PSE properties, so each new project site starts from a working design system rather than a blank page.
  • Structured project metadata on pse.dev, so every project is data, not a hand-written page, which keeps a research team's fast-moving portfolio accurate.
  • Documentation and marketing written for adopters, not researchers: lead with what each project does and how to use it, not the underlying math.

Impact

pse.dev is PSE's public front door: where the team's projects and research are indexed. The design system behind it standardized how the rest of the team's sites get built. Contributions also reached the ecosystem's event platforms, including Devconnect and ETHDenver.

worksnext