| Authors | Kobi Gurkan; Koh Wei Jie; Barry Whitehat |
|---|---|
| Published | February 2, 2020 |
| Project | Semaphore, a project associated with Privacy & Scaling Explorations (PSE) |
| Document | Community proposal / technical paper, Version 1 |
| Paper license | Not stated in the PDF |
| Official paper | Semaphore: Zero-Knowledge Signaling on Ethereum (PDF) |
Disclaimer: This page summarizes a technical document for education. It is not investment, legal, or security advice. Read the original paper and current documentation before relying on an implementation.
| Original paper | Original paper |
|---|---|
| Directories | Ethereum Whitepapers & Research |
This is a summary of the February 2020 Semaphore v1 community proposal. It describes that paper’s design and examples; it should not be read as a complete description of later Semaphore versions.
What the paper proposes
The paper presents Semaphore as a framework for signaling from within a registered group. A member can prove that they belong to the group and publish a signal without revealing which identity in the group produced it. The application decides how people enter the group and what signals it accepts. Semaphore supplies the proof and signaling mechanism; it does not decide whether a group’s membership rules are fair or resistant to fake identities.
The design combines an identity commitment tree, a zero-knowledge proof, and a context-specific nullifier. In the paper’s Ethereum implementation, the contracts maintain group state and check proofs. The signal itself is stored publicly, so the content of a signal may still reveal information even when the sender’s group identity is hidden.
How v1 signaling works
- Enrollment: An application checks its own eligibility rules and adds a commitment for an accepted identity to a Merkle tree. The public tree represents the set without publishing the identity’s private material.
- Membership proof: To signal, a member creates a zero-knowledge proof that their commitment is included under an accepted tree root, without revealing which leaf is theirs.
- Scoped nullifier: The proof also produces a nullifier tied to an external nullifier chosen for a context, such as a particular question. The contract can reject a second signal from that identity in the same context while allowing a signal in a different context.
- Public signal: The application-defined message is recorded. A relayer may submit the transaction for the member, which can reduce the direct link between the member’s Ethereum address and the transaction, but does not guarantee anonymity against every other source of information.
The paper specifies a Groth16 zk-SNARK construction using the BN254 curve, along with implementation details from its 2020 design. Those details are historical and should not be assumed to describe the present protocol implementation.
Examples in the paper
The proposal describes MicroMix, a mixer example, and OneOfUs, an anonymous survey or voting example built around event attendance credentials. They illustrate how an application can set enrollment rules, choose a context, and interpret signals. They are examples in the paper, not evidence that every Semaphore-based application has the same properties or that these prototypes are current production services.
Limits and security assumptions
- Membership is application-defined. A proof shows that an identity is in the registered set. It does not prove that one identity equals one real person. The application’s onboarding rules determine who qualifies and whether Sybil resistance exists.
- Signals are not automatically secret. The paper’s signaling model stores messages publicly. Applications must avoid putting identifying information in the signal and must account for timing, relayer, network, and other metadata.
- A nullifier is scoped, not universal. It prevents repeat signaling only under the same configured context and according to the contract’s rules. It does not by itself guarantee a fair election or prevent collusion.
- Proof security depends on the full system. Circuit, setup, contract, key-management, and application assumptions matter. A protocol-level proof does not replace review of a particular deployment.
V1 and current Semaphore
The official documentation now presents Semaphore V4 and maintains separate versioned documentation. V4’s published materials describe changes such as a new identity schema and Lean Incremental Merkle Tree. That is a later design. This entry remains focused on the 2020 v1 paper so the original paper’s claims are not confused with current code or specifications.
The current GitHub repository lists an MIT license for the software. The v1 PDF itself does not state a license, so the repository’s code license should not be treated as a license for the paper.
Social Media Sentiment
A small, older Reddit sample mentions Semaphore in broader zero-knowledge explainers as a way to prove group membership and send votes or endorsements with parts of a member’s identity hidden. The discussion is general and not a focused review of the protocol; it does not provide enough evidence to infer current community sentiment, adoption, or performance.
Last updated: 2026-10
Related Terms
See Also
Sources
-
Gurkan, Kobi; Koh Wei Jie; Barry Whitehat. February 2, 2020. Semaphore: Zero-Knowledge Signaling on Ethereum. The original 16-page community proposal summarized here; it identifies the authors, date, v1 design, and paper examples.
-
Privacy & Scaling Explorations. Semaphore V1 documentation. What Is Semaphore? (V1). Explains registered identities, public signals, external nullifiers, and the versioned implementation context.
-
Semaphore Protocol. Current documentation. What Is Semaphore? and V4 benchmarks. These current materials distinguish later protocol versions from the 2020 paper.
-
Semaphore Protocol. Software repository. semaphore-protocol/semaphore. Describes the current codebase and its repository-level MIT license; that license does not establish the paper’s license.
-
r/ethfinance contributors. June 28, 2022. Daily General Discussion: zero-knowledge technology. A broad community explainer that briefly describes Semaphore among Ethereum privacy applications; used only as a limited discussion sample, not as evidence of current adoption.