TrustLayer is the decentralized human trust layer for Web3 — a Base-native protocol that publishes portable, sybil-resistant Trust Scores derived from peer vouches and on-chain proofs. Any dApp can verify a user is a real human in a single Solidity call, without KYC or biometrics.

Yes. Creating a Trust ID, vouching peers, and earning $TRUST rewards is free. Only optional premium tiers or write operations charge $TRUST fees.

Does TrustLayer require KYC or biometrics?

No. TrustLayer never collects KYC, iris scans, or personal data. Identity comes from peer vouches and wallet signatures — reputation is math, not documents.

What is the $TRUST token?

$TRUST is TrustLayer's native token on Base with a fixed 1B supply. It powers vouching rewards, badge fees, staking gates, and revenue-funded buyback-and-burn.

How does TrustLayer compare to Worldcoin?

TrustLayer requires no biometric hardware, is fully non-custodial, and lives on Base. Worldcoin uses iris scans and centralized orb hardware. See the full comparison at /vs/worldcoin.

Attestation aggregation · Proof of personhood

Gitcoin Passport (Human Passport) vs TrustLayer Protocol

Gitcoin Passport (Human Passport) (stamp aggregation from third-party accounts) and TrustLayer Protocol (peer-vouched human trust scores on base) 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.

Gitcoin Passport (Human Passport)

Passport sums independent stamps into a unique-humanity score. Breadth is its strength; the score inherits the trust assumptions and outages of every stamp provider.

Openness 7/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	Gitcoin Passport (Human Passport)	TrustLayer Protocol
Category	Attestation aggregation	Proof of personhood
Network	EVM (multi-chain attestations)	Base (EVM)
How a person is proven	Collecting stamps from linked Web2 and Web3 accounts into a unique-humanity score	Wallet signature (EIP-191) plus mutual peer vouches
Biometric data	Optional, provider dependent	None collected
KYC requirement	Optional KYC path	No KYC
Hardware needed	Any phone or laptop	Any phone or laptop
Key custody	User holds the keys	User holds the keys
Reputation model	Sum of third-party stamps	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	Stamp providers control their own issuance; scorer weights are governed centrally	No central operator can revoke an identity; keys stay on the device

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.

Criterion	Gitcoin Passport (Human Passport)	TrustLayer Protocol
No biometric collectionmax 2	1/2 — Optional, provider dependent	2/2 — None collected
No KYC requirementmax 2	1/2 — Optional KYC path	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 — Sum of third-party stamps	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	7/10	10/10

Best fit for Gitcoin Passport (Human Passport)

Grant rounds and quadratic funding
Apps happy to rely on external account ownership as a proxy for humanity

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 Gitcoin Passport (Human Passport) scores 7/10 — 8 of 12 attributes differ. TrustLayer Protocol asks less of the user up front; Gitcoin Passport (Human Passport) 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 Gitcoin Passport (Human Passport) and TrustLayer Protocol?▼

Category: Gitcoin Passport (Human Passport) — Attestation aggregation; TrustLayer Protocol — Proof of personhood.

Does Gitcoin Passport (Human Passport) or TrustLayer Protocol require biometrics or KYC?▼

Gitcoin Passport (Human Passport): optional, provider dependent, optional kyc path. TrustLayer Protocol: none collected, no kyc.

Which one can a developer query from an API?▼

Gitcoin Passport (Human Passport) and TrustLayer Protocol

Can Gitcoin Passport (Human Passport) 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.

Get a Trust ID Read the API docs

Keep reading

All ecosystem comparisons In-depth TrustLayer vs gitcoin-passport write-up Live trust leaderboard Public trust reports