Welcome to CoinDropster
Enter a new password
Choose a new password
Enter a new password for your account.
All active sessions will be signed out.
By clicking “Sign in”, you confirm that you have read and agree to the CoinDropster Terms of Use, Privacy Policy and Disclaimer
Proof of Personhood Explained: Why Projects Verify Real Humans
What proof of personhood is and why it matters: how projects check that a real person is behind a wallet, the main approaches, and their pros, cons and risks.
What proof of personhood is and why it is needed is a question airdrop participants meet more and more often: a project wants to know that one real person stands behind a wallet, not a hundred addresses run by one operator. This article explains the main approaches to such checks, their strengths and weaknesses, which data you may be asked for, and which data should never be requested.
This material is educational and is not financial or legal advice. It does not guarantee any reward and does not replace a specific project's rules: verification requirements differ from project to project.
Why uniqueness checks exist
Creating a wallet costs nothing, so one person can control many addresses. This is called a Sybil attack, and it causes two problems for projects.
- Distributions. If a reward is split between addresses, an operator with a hundred wallets takes a share meant for a hundred different people. Real participants receive less.
- Voting. If vote weight is not tied to a token balance and one address equals one vote, many addresses distort the outcome. How voting works in general is covered in the article on DAO governance.
Proof of personhood addresses exactly this: confirming that an address belongs to a human and that this human has not signed up twice. Note that learning the person's name is not required for that. How projects look for suspicious address clusters after the fact is described in the article on Sybil detection methods.
The main approaches
Reputation scores based on activity and linked accounts
The system collects signals: the age and history of an address, linked accounts and profiles, verified actions. These add up to a score, and a threshold decides whether the address counts.
- Pros: no documents or biometrics, and the approach is flexible.
- Cons: scores can be wrong, and a newcomer or someone who simply uses the network little gets a low result. For projects the problem is that any metric eventually starts being imitated, so the set of signals has to keep changing.
Social account confirmation
Linking a social account or an email as a sign of a real user.
- Pros: simple and fast.
- Cons: accounts can be created in bulk, and the link itself ties a wallet to a public profile, which hurts privacy.
KYC with a provider
A document and face check by a specialised company. The project usually receives only the outcome (passed or failed), while the provider keeps the documents.
- Pros: the highest confidence in uniqueness.
- Cons: collection of ID data, leak risk, regional limits, and false rejections caused by a poor photo or an unusual document. More on requirements and country limits is in the article on KYC and regional restrictions.
Biometrics and device checks
The general idea is to match human traits (such as facial features or the iris) or hardware properties of a device, to make sure there is one registration per person.
- Pros: it is hard to turn one person into many.
- Cons: biometrics are the most sensitive data there is: a password can be changed, a face cannot. False rejections are possible, and so are questions about how such data is stored and whether collecting it is lawful. Tying a check to a device excludes people without suitable hardware.
Web of trust: vouching
Already verified members vouch for new ones. The idea is that it is harder to fool a community of real people than a set of automated checks.
- Pros: no documents needed, and it relies on community trust.
- Cons: a newcomer with no acquaintances struggles to get in, and if vouches are sold or traded, the network fills with fake members. That is a design problem for the systems themselves, and defending against it is their job.
In practice projects combine several approaches, and none is perfect: the stricter the check, the higher the risk of false rejections and the more data is collected.
What data is requested, and what must never be
It is normal for a check to ask you to:
- connect a wallet and sign a readable login message;
- link a profile or email, if you agree to it;
- complete a check with a KYC provider on the page listed on the project's official site.
It should never ask for:
- a seed phrase or private key. No genuine uniqueness check needs them in any form;
- a password for a wallet, email or exchange;
- remote access to your computer or phone;
- an unlimited approval or a signature that permits spending your tokens, presented as "identity confirmation". What such windows mean is explained in the article on what you sign in a wallet.
Scammers posing as "identity verification"
The topic is convenient for fraud because people have been taught that "verification" is normal. Typical signs: a direct message or comment about urgent "verification" or the reward will expire; a site with a look-alike address; a request to enter a recovery phrase "for matching"; a "support agent" who asks you to connect a wallet or install a program. If any of this matches, stop and compare the address with the project's official site. Fake-support schemes are described in the article on direct-message scams, and signs of fraudulent pages in the article on spotting fake claim sites.
Privacy and data storage
Before going through a check, ask yourself a few questions:
- Who exactly receives the data: the project or a separate provider?
- What is kept after the check: only the result, or the documents and images too?
- How long is the data stored, and can you request its deletion?
- Will it be publicly visible that a wallet is linked to a specific person or profile?
If the official privacy policy gives no clear answers, that is a reason to weigh whether participation is worth the data requested. Declining a check is a legitimate decision: it may mean a distribution is unavailable to you, but you are not obliged to hand over sensitive information. If your wallet was flagged by mistake, see the articles on qualifying without a Sybil flag and what to do after such a flag.
In the CoinDropster catalog every project has a page with its status and key facts, and status changes (Potential, Confirmed, Snapshot, Verification, Reward available or Distributed) are tracked. The Verification status hints that a checking stage is near, which is a reason to read the rules on the official site in advance. Checklists in the app keep deadlines close at hand. View tracked airdrops →