Proof of personhood · Proof of personhood
BrightID vs Worldcoin (World ID)
BrightID (social graph verification parties) and Worldcoin (World ID) (iris-scan proof of personhood) both aim at sybil resistance, but they disagree on 7 of 12 measurable attributes. This page compares them field by field from published protocol behaviour — no marketing scores, no invented metrics.
BrightID
BrightID derives uniqueness from a human-verified social graph. Privacy posture is strong; onboarding depends on scheduled live sessions with other people.
Openness 9/10
Worldcoin (World ID)
World ID proves a person enrolled once at an Orb, producing a binary human signal backed by an iris template hash. It is strong on uniqueness and dependent on proprietary hardware distribution.
Openness 5/10
Attribute comparison
| Attribute | BrightID | Worldcoin (World ID) |
|---|---|---|
| Category | Proof of personhood | Proof of personhood |
| Network | Chain-agnostic (bridged attestations) | Ethereum / Optimism / World Chain |
| How a person is proven | Video verification parties building a social graph analysed for uniqueness | Iris biometric enrolment on Orb hardware, zero-knowledge nullifier on chain |
| Biometric data | None collected | Required to verify |
| KYC requirement | No KYC | No KYC |
| Hardware needed | Any phone or laptop | Purpose-built hardware |
| Key custody | User holds the keys | Shared between user and operator |
| Reputation model | Binary human / not human | Binary human / not human |
| Native token | None | $WLD |
| Public read API | Yes | Yes |
| Open source core | Yes | Yes |
| Who can revoke you | Graph analysis can drop a node below the verification threshold | Foundation and Orb operators control enrolment and verification rollout |
7 of 12 attributes differ; 5 are identical.
Openness criteria, scored openly
The matrix scores what a protocol asks of a user and how much of the result stays verifiable in public. It is not a quality, security or market ranking, and it is not derived from TrustLayer trust scores.
| Criterion | BrightID | Worldcoin (World ID) |
|---|---|---|
| No biometric collectionmax 2 | 2/2 — None collected | 0/2 — Required to verify |
| No KYC requirementmax 2 | 2/2 — No KYC | 2/2 — No KYC |
| No specialised hardwaremax 1 | 1/1 — Any phone or laptop | 0/1 — Purpose-built hardware |
| User-held keysmax 2 | 2/2 — User holds the keys | 1/2 — Shared between user and operator |
| Continuous reputationmax 1 | 0/1 — Binary human / not human | 0/1 — Binary human / not human |
| Public read APImax 1 | 1/1 — Documented public endpoints | 1/1 — Documented public endpoints |
| Open source coremax 1 | 1/1 — Core implementation is public | 1/1 — Core implementation is public |
| Total | 9/10 | 5/10 |
Best fit for BrightID
- Communities able to run recurring live verification sessions
- Projects avoiding biometrics and KYC entirely
Best fit for Worldcoin (World ID)
- Projects that require Orb-grade physical uniqueness
- Markets with Orb operator coverage
Verdict
On the openness criteria below, BrightID scores 9/10 and Worldcoin (World ID) scores 5/10 — 7 of 12 attributes differ. BrightID asks less of the user up front; Worldcoin (World ID) offers a stronger external anchor where its trust assumptions are acceptable. Pick by what you must not collect, and by whether you need a one-off human check or a score that keeps moving.
Frequently asked questions
What is the main difference between BrightID and Worldcoin (World ID)?▼
Network: BrightID — Chain-agnostic (bridged attestations); Worldcoin (World ID) — Ethereum / Optimism / World Chain.
Does BrightID or Worldcoin (World ID) require biometrics or KYC?▼
BrightID: none collected, no kyc. Worldcoin (World ID): required to verify, no kyc.
Which one can a developer query from an API?▼
BrightID and Worldcoin (World ID)
Can BrightID and Worldcoin (World ID) be used together?▼
Yes. They produce independent signals, so apps commonly combine a personhood check with a continuous reputation score before granting access or rewards.
Check a wallet against TrustLayer now
Trust scores, verifier counts and score factors are public and queryable — one request, no key required for read endpoints.
Keep reading