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.

KYC-anchored identity · Proof of personhood

Galxe Passport vs TrustLayer Protocol

Galxe Passport (kyc-anchored credential passport for campaigns) and TrustLayer Protocol (peer-vouched human trust scores on base) both aim at sybil resistance, but they disagree on 10 of 12 measurable attributes. This page compares them field by field from published protocol behaviour — no marketing scores, no invented metrics.

Galxe Passport

Galxe Passport binds a KYC check to a soulbound credential used across quest campaigns. Convenient inside that ecosystem, custodial in trust model.

Openness 2/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	Galxe Passport	TrustLayer Protocol
Category	KYC-anchored identity	Proof of personhood
Network	Multi-chain (Galxe credentials)	Base (EVM)
How a person is proven	Document KYC verification minted as a soulbound passport credential	Wallet signature (EIP-191) plus mutual peer vouches
Biometric data	Required to verify	None collected
KYC requirement	KYC required	No KYC
Hardware needed	Any phone or laptop	Any phone or laptop
Key custody	Issuer-controlled credential	User holds the keys
Reputation model	Pass that expires and is renewed	Continuous score that moves with real activity
Native token	GAL	$TRUST
Public read API	Yes	Yes
Open source core	Proprietary	Yes
Who can revoke you	Issuer controls credential validity	No central operator can revoke an identity; keys stay on the device

10 of 12 attributes differ; 2 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	Galxe Passport	TrustLayer Protocol
No biometric collectionmax 2	0/2 — Required to verify	2/2 — None collected
No KYC requirementmax 2	0/2 — KYC required	2/2 — No KYC
No specialised hardwaremax 1	1/1 — Any phone or laptop	1/1 — Any phone or laptop
User-held keysmax 2	0/2 — Issuer-controlled credential	2/2 — User holds the keys
Continuous reputationmax 1	0/1 — Pass that expires and is renewed	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	0/1 — Proprietary implementation	1/1 — Core implementation is public
Total	2/10	10/10

Best fit for Galxe Passport

Campaign and quest platforms needing verified participants
Airdrops that accept KYC as the anti-sybil gate

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

Category: Galxe Passport — KYC-anchored identity; TrustLayer Protocol — Proof of personhood.

Does Galxe Passport or TrustLayer Protocol require biometrics or KYC?▼

Galxe Passport: required to verify, kyc required. TrustLayer Protocol: none collected, no kyc.

Which one can a developer query from an API?▼

Galxe Passport and TrustLayer Protocol

Can Galxe 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 Live trust leaderboard Public trust reports