Proof of personhood · Proof of personhood
BrightID vs TrustLayer Protocol
BrightID (social graph verification parties) and TrustLayer Protocol (peer-vouched human trust scores on base) both aim at sybil resistance, but they disagree on 5 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
TrustLayer Protocol
TrustLayer issues a device-held identity from a wallet signature, then grows a continuous trust score from independent peer vouches and recorded proofs. Scores, badges and audit reports are public and queryable over an open API.
Openness 10/10
Attribute comparison
| Attribute | BrightID | TrustLayer Protocol |
|---|---|---|
| Category | Proof of personhood | Proof of personhood |
| Network | Chain-agnostic (bridged attestations) | Base (EVM) |
| How a person is proven | Video verification parties building a social graph analysed for uniqueness | Wallet signature (EIP-191) plus mutual peer vouches |
| 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 | Continuous score that moves with real activity |
| Native token | None | $TRUST |
| Public read API | Yes | Yes |
| Open source core | Yes | Yes |
| Who can revoke you | Graph analysis can drop a node below the verification threshold | No central operator can revoke an identity; keys stay on the device |
5 of 12 attributes differ; 7 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 | TrustLayer Protocol |
|---|---|---|
| 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 | 1/1 — Continuous score that moves with real activity |
| 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 | 10/10 |
Best fit for BrightID
- Communities able to run recurring live verification sessions
- Projects avoiding biometrics and KYC entirely
Best fit for TrustLayer Protocol
- Apps that need sybil resistance today with no hardware rollout
- Communities building peer-to-peer reputation
- Teams that cannot collect KYC or biometric data
Verdict
On the openness criteria below, TrustLayer Protocol scores 10/10 and BrightID scores 9/10 — 5 of 12 attributes differ. TrustLayer Protocol asks less of the user up front; BrightID 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 TrustLayer Protocol?▼
Network: BrightID — Chain-agnostic (bridged attestations); TrustLayer Protocol — Base (EVM).
Does BrightID or TrustLayer Protocol require biometrics or KYC?▼
BrightID: none collected, no kyc. TrustLayer Protocol: none collected, no kyc.
Which one can a developer query from an API?▼
BrightID and TrustLayer Protocol
Can BrightID and TrustLayer Protocol 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