Proof of personhood · Proof of personhood
BrightID vs Idena
BrightID (social graph verification parties) and Idena (proof-of-person blockchain with flip puzzles) both aim at sybil resistance, but they disagree on 4 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
Idena
Idena makes personhood a consensus role: identities revalidate on a fixed schedule by solving puzzles simultaneously. Strong equality guarantees, high ongoing user effort.
Openness 9/10
Attribute comparison
| Attribute | BrightID | Idena |
|---|---|---|
| Category | Proof of personhood | Proof of personhood |
| Network | Chain-agnostic (bridged attestations) | Idena (own network) |
| How a person is proven | Video verification parties building a social graph analysed for uniqueness | Synchronised validation ceremonies solving human-only flip puzzles |
| Biometric data | None collected | None collected |
| KYC requirement | No KYC | No KYC |
| Hardware needed | Any phone or laptop | Any phone or laptop |
| Key custody | User holds the keys | User holds the keys |
| Reputation model | Binary human / not human | Binary human / not human |
| Native token | None | iDNA |
| Public read API | Yes | Yes |
| Open source core | Yes | Yes |
| Who can revoke you | Graph analysis can drop a node below the verification threshold | Missing a validation ceremony downgrades or kills the identity status |
4 of 12 attributes differ; 8 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 | Idena |
|---|---|---|
| No biometric collectionmax 2 | 2/2 — None collected | 2/2 — None collected |
| No KYC requirementmax 2 | 2/2 — No KYC | 2/2 — No KYC |
| No specialised hardwaremax 1 | 1/1 — Any phone or laptop | 1/1 — Any phone or laptop |
| User-held keysmax 2 | 2/2 — User holds the keys | 2/2 — User holds the keys |
| 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 | 9/10 |
Best fit for BrightID
- Communities able to run recurring live verification sessions
- Projects avoiding biometrics and KYC entirely
Best fit for Idena
- Experiments needing one-node-one-person consensus
- Users willing to attend scheduled validation ceremonies
Verdict
On the openness criteria below, BrightID scores 9/10 and Idena scores 9/10 — 4 of 12 attributes differ. BrightID asks less of the user up front; Idena 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 Idena?▼
Network: BrightID — Chain-agnostic (bridged attestations); Idena — Idena (own network).
Does BrightID or Idena require biometrics or KYC?▼
BrightID: none collected, no kyc. Idena: none collected, no kyc.
Which one can a developer query from an API?▼
BrightID and Idena
Can BrightID and Idena 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