Proof of personhood · Proof of personhood

TrustLayer Protocol vs Worldcoin (World ID)

TrustLayer Protocol (peer-vouched human trust scores on base) and Worldcoin (World ID) (iris-scan proof of personhood) both aim at sybil resistance, but they disagree on 8 of 12 measurable attributes. This page compares them field by field from published protocol behaviour — no marketing scores, no invented metrics.

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

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

AttributeTrustLayer ProtocolWorldcoin (World ID)
CategoryProof of personhoodProof of personhood
NetworkBase (EVM)Ethereum / Optimism / World Chain
How a person is provenWallet signature (EIP-191) plus mutual peer vouchesIris biometric enrolment on Orb hardware, zero-knowledge nullifier on chain
Biometric dataNone collectedRequired to verify
KYC requirementNo KYCNo KYC
Hardware neededAny phone or laptopPurpose-built hardware
Key custodyUser holds the keysShared between user and operator
Reputation modelContinuous score that moves with real activityBinary human / not human
Native token$TRUST$WLD
Public read APIYesYes
Open source coreYesYes
Who can revoke youNo central operator can revoke an identity; keys stay on the deviceFoundation and Orb operators control enrolment and verification rollout

8 of 12 attributes differ; 4 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.

CriterionTrustLayer ProtocolWorldcoin (World ID)
No biometric collectionmax 22/2None collected0/2Required to verify
No KYC requirementmax 22/2No KYC2/2No KYC
No specialised hardwaremax 11/1Any phone or laptop0/1Purpose-built hardware
User-held keysmax 22/2User holds the keys1/2Shared between user and operator
Continuous reputationmax 11/1Continuous score that moves with real activity0/1Binary human / not human
Public read APImax 11/1Documented public endpoints1/1Documented public endpoints
Open source coremax 11/1Core implementation is public1/1Core implementation is public
Total10/105/10

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

Best fit for Worldcoin (World ID)

  • Projects that require Orb-grade physical uniqueness
  • Markets with Orb operator coverage

Verdict

On the openness criteria below, TrustLayer Protocol scores 10/10 and Worldcoin (World ID) scores 5/10 — 8 of 12 attributes differ. TrustLayer Protocol 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 TrustLayer Protocol and Worldcoin (World ID)?

Network: TrustLayer Protocol — Base (EVM); Worldcoin (World ID) — Ethereum / Optimism / World Chain.

Does TrustLayer Protocol or Worldcoin (World ID) require biometrics or KYC?

TrustLayer Protocol: none collected, no kyc. Worldcoin (World ID): required to verify, no kyc.

Which one can a developer query from an API?

TrustLayer Protocol and Worldcoin (World ID)

Can TrustLayer Protocol 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