Ethos Human Verification has now verified 1,300+ humans, without iris scans, face scans or government ID. In the first five days after verification opened to any human verified member with a credibility score above 1600, 169 new verification bonds were created and 66 people were verified.
Those numbers matter for any team trying to tell real people from bots. Most identity options in crypto ask users for biometrics or ID documents. Ethos asks other people to vouch for them, with their own credibility at stake.
The trade Ethos wanted to avoid
Ethos’s case study describes the usual choice in crypto identity as a trade nobody should have to make: scan your biometrics with proprietary hardware, or hand your government ID to a centralized KYC provider.
Both options carry risk. According to the study, biometric identity projects have been banned or suspended in over 10 countries, and KYC databases remain honeypots for hackers.
Instead of asking whether a machine can verify that someone is human, Ethos has trusted humans verify each other.
How verification works
We’ve covered the launch of Human Verification before. In short, the process has three steps:
- Request and bond. The user stakes 10,000 XP and signs an onchain bond declaring: “I am human. I have no other Ethos profiles claiming to be human.” If the bond is broken, 800 credibility score is slashed.
- Verify. Three independent verifiers, each human verified with a 1600+ credibility score, confirm through a live video call, voice call or in person meeting after personally interacting with the applicant.
- Verified. An onchain “Human Verified” credential is issued, along with a +100 credibility boost. The credential is permanent, portable and composable across any protocol, and the bond is recorded onchain and tied to the profile forever.
At a glance:
- Who can verify: any HV member with a 1600+ score
- Verification method: live call or in person
- Cost to verify: 10,000 XP
- Verifications required: 3
- Credibility score at stake: 800
- Credibility boost: +100
- Biometrics: none
- Government ID: none
Why both sides are accountable
The system relies on both the applicant and the verifiers having something to lose. The applicant’s bond costs 800 credibility score and permanent loss of verified status if it’s broken.
Verifiers carry risk too. A verifier who confirms people who should not be verified can be slashed, and that revokes every verification they have ever performed. That gives each verifier a reason to take every call seriously.
How it compares with biometrics and KYC
The case study sets Ethos Human Verification against biometric proof of personhood and traditional KYC:
- Biometrics required: iris or face scan for biometric PoP, photo ID and selfie for KYC, none for Ethos HV
- Hardware needed: a specialized device for biometric PoP, a phone camera for KYC, any device for Ethos HV
- Centralized data risk: high for both biometric PoP and KYC, none for Ethos HV
- Regulatory bans: 10+ countries for biometric PoP, varies for KYC, zero for Ethos HV
- Cost to integrate: partnership required for biometric PoP, a fee per verification for KYC, a free API for Ethos HV
- Onchain: partial for biometric PoP, offchain for KYC, fully onchain for Ethos HV
- Fraud accountability: none for biometric PoP or KYC, bond and slashing for Ethos HV
Where teams could use it
The study lists several ways projects could put the credential to work:
- Token sales and presales: gate allocations to verified humans so bot wallets cannot snipe supply.
- Airdrop distribution: filter sybils before they drain an allocation, without KYC friction.
- Prediction markets: stack HV alongside existing identity layers for higher confidence trading access.
- Social trading and leaderboards: make sure the traders people follow are real humans, not bot networks.
- DeFi lending: use HV as a trust primitive for undercollateralized lending.
- DAO governance: one person, one vote, without biometric surveillance.
According to the study, Human Verification is free to integrate through the Ethos API and requires no changes to a team’s existing stack.
This article is adapted from the Ethos case study.
