Pearl's public site names zero people. No team page, no founders, no engineers — a deliberately faceless front. But a company leaves a paper trail. Pulled from public GitHub history and published papers, here's the shape of the team behind it — roughly twenty people, real credentials, real institutions. We're not publishing a name-by-name dossier on engineers who never chose to go public; the fragments below are real but deliberately unattributed.
The founders
Named on the record — the one part of this roster that's already unambiguous.
Founder · CEO
Omri Weinstein
ON THE TAPE KEYNOTE
Ex-NVIDIA, ex-VAST Data; Hebrew University faculty. The public face — the one on the keynote tape.
Founder · Co-founder
Ilan Komargodski
CO-AUTHOR PoUW PAPER
Hebrew University cryptographer. Co-authored the proof-of-useful-work paper the entire chain rests on.
CLASSIFIED
Fifteen résumés, no names attached
The bench never went public the way the founders did — nobody here chose this. Every card below is one real person — real role, real background, real tenure — scattered out of order on purpose. Read it as a shape, not a directory.
Protocol Engineer
Prior: core contributor, major L1 blockchain
Owns the Go node / consensus layer, and is one of only four people with release-gate approval — trusted to actually ship.
Owns the zero-knowledge proving stack — the math that makes it trustless.
On the bench since May 2026
GPU Kernel Engineer
Prior: joint industry-academic PhD, ML systems
The reference implementation behind Hawkeye — Pearl's entire verification keystone — lives in a personal repo under this same work email.
On the bench since Feb 2026
Mining Systems Engineer
Prior: Hebrew University PhD, medical-AI research background
Added themself as codeowner in their very first commit — a small tell of seniority from day one.
On the bench since Apr 2026
Cryptography Engineer
Prior: cryptography PhD, Paris
The bench runs deep on ZK math — not a one-person job.
On the bench
Infra & DevOps
Prior: —
Default owner across nearly the entire repo — reviews almost everything that ships. Also one of the four with release-gate approval. First commit: literally "Initial Pearl implementation."
On the bench since Mar 2026
Infra / CI Engineer
Prior: Technion-trained, compiler background
Builds the tools that build the chain.
On the bench
Desktop Client Engineer
Prior: —
Ships the actual UI, and is one of the four with release-gate approval — real product, not just protocol.
On the bench since May 2026
Wallet Engineer
Prior: ran a bot/automation startup before this
Owns the money-facing surface, and is the fourth release-gate approver — the part users actually touch, shipped by someone trusted to ship it.
On the bench
Desktop Engineer
Prior: long-tenured open-source contributor
Committing to public repos years before Pearl existed.
On the bench
CUDA Kernel Engineer
Prior: —
Low-level GPU kernel work — the unglamorous, load-bearing engineering the verification scheme actually runs on.
On the bench
CUDA Kernel Engineer
Prior: —
A second kernel engineer on the same effort — this is a two-person specialty, not a one-person job.
On the bench
ML Engineer
Prior: computer vision & edge-AI background
Pointed a very different skill set at mining.
On the bench
Inference Optimization Engineer
Prior: ex-Tel Aviv University
Makes inference fast — the day job, now pointed at Pearl.
On the bench
ML / Research
Prior: —
Surfaced only through org-membership records — exact role isn't disclosed anywhere public. We're not going to guess at one.
On the bench
COMPILED FROM PUBLIC RECORDS — PUBLIC GITHUB COMMIT HISTORY AND PUBLISHED ARXIV PAPERS. BENCH FACTS ARE REAL; ATTRIBUTION TO SPECIFIC PEOPLE IS INTENTIONALLY NOT PUBLISHED.
The shape of the team — no names required
You don't need anyone's name to see the structure. Group the ~20 people by what they actually do, and one thing jumps out: every functional cluster is stitched to the others through a single internal identity — Duplex — via commit emails and self-chosen handles. This is the org chart of a faceless company, drawn entirely from public code and papers.
ROLES ONLY, NO NAMES. EVERY GROUPING AND EVERY LINK IS DERIVED FROM PUBLIC GITHUB CODEOWNERS, COMMIT METADATA, HUGGINGFACE MEMBERSHIP, AND PUBLISHED PAPER AUTHORSHIP.