Proof of personhood · Proof of personhood

Proof of Humanity vs TrustLayer Protocol

Proof of Humanity (video registry with crypto-economic challenges) 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.

Proof of Humanity

Proof of Humanity trades privacy for adversarial auditability: registrations are public videos anyone can challenge with a deposit. Sybil resistance is enforced economically.

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

AttributeProof of HumanityTrustLayer Protocol
CategoryProof of personhoodProof of personhood
NetworkEthereum / GnosisBase (EVM)
How a person is provenPublic video submission, vouching, and dispute resolution via Kleros arbitrationWallet signature (EIP-191) plus mutual peer vouches
Biometric dataNone collectedNone collected
KYC requirementNo KYCNo KYC
Hardware neededAny phone or laptopAny phone or laptop
Key custodyUser holds the keysUser holds the keys
Reputation modelBinary human / not humanContinuous score that moves with real activity
Native tokenNone$TRUST
Public read APIYesYes
Open source coreYesYes
Who can revoke youAnyone can challenge a registration; arbitration decides removalNo 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.

CriterionProof of HumanityTrustLayer Protocol
No biometric collectionmax 22/2None collected2/2None collected
No KYC requirementmax 22/2No KYC2/2No KYC
No specialised hardwaremax 11/1Any phone or laptop1/1Any phone or laptop
User-held keysmax 22/2User holds the keys2/2User holds the keys
Continuous reputationmax 10/1Binary human / not human1/1Continuous score that moves with real activity
Public read APImax 11/1Documented public endpoints1/1Documented public endpoints
Open source coremax 11/1Core implementation is public1/1Core implementation is public
Total9/1010/10

Best fit for Proof of Humanity

  • Governance systems that want an adversarial, publicly auditable registry
  • Communities comfortable with public video identity

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 Proof of Humanity scores 9/10 — 5 of 12 attributes differ. TrustLayer Protocol asks less of the user up front; Proof of Humanity 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 Proof of Humanity and TrustLayer Protocol?

Network: Proof of Humanity — Ethereum / Gnosis; TrustLayer Protocol — Base (EVM).

Does Proof of Humanity or TrustLayer Protocol require biometrics or KYC?

Proof of Humanity: none collected, no kyc. TrustLayer Protocol: none collected, no kyc.

Which one can a developer query from an API?

Proof of Humanity and TrustLayer Protocol

Can Proof of Humanity 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