Home / Crypto / Academy / Research and fundamentals

Evaluating a team when anyone can claim anything

Websites list advisors who have never heard of the project, and profiles claim employers who never employed them. Verification is a specific skill and it takes about twenty minutes.

MODULE 43 OF 64 LEVEL 5: RESEARCH AND FUNDAMENTALS 13 MIN

Anonymity is not automatically a problem

Satoshi Nakamoto is anonymous. Several major protocols were built by pseudonymous developers and hold billions safely. Demanding real names as a blanket rule would have excluded some of the best things in the industry.

The question is not "are they anonymous" but what can they do to you. Anonymity is a risk multiplier applied to whatever power the team holds.

When anonymity is acceptable
Acceptable
No power to abuse
Immutable contracts, no upgrade key, no treasury, no ability to mint. The code is deployed and fixed. Who wrote it matters far less because they cannot change it or take anything.
Risky
Some power
Upgradeable contracts behind a timelock and multisig, or a treasury with governance. Recoverable if they vanish, and you are trusting people you cannot identify.
Disqualifying
Full power
A single anonymous wallet controlling the upgrade key, the mint function or the treasury. There is no meaningful difference between this and handing money to a stranger with a written promise.

A useful reframing: a pseudonymous developer with a five year public history of shipped work has a reputation that is expensive to burn, which is most of what a real name provides anyway. An anonymous account created four months ago has nothing at stake.

Verifying a named team, in twenty minutes

  1. Search the person, not the project. Their name plus their claimed previous employer. If a senior role at a well known company produces no independent trace, that is your answer.
  2. Check the profile's age and history. A professional profile created three months ago, listing a decade of experience, with connections only to other project members, is a construction.
  3. Confirm claimed employment independently. Conference talks, press coverage, patents, published papers, an old team page in an archive. Real careers leave residue in places the person does not control.
  4. Check advisors directly. Advisor lists are the most fabricated section on any crypto site. Message the advisor on their own established account and ask. People do reply, and they are sometimes surprised.
  5. Reverse image search the photographs. Stock imagery and stolen photographs remain common and take fifteen seconds to catch.
  6. Look for what they built before. A previous project is far more informative than a biography. If there was one, what happened to it? A team on their fourth token in two years is telling you the pattern.

Reading a code repository without being a developer

You do not need to read the code. You need to read the activity, which is visible at a glance and much harder to fake convincingly.

Commit history is trivially fabricated in bulk, and empty commits inflate counts. Look at what the commits contain and whether they cluster suspiciously. A repository created in one week containing four years of dated history is a specific and detectable fraud.

The recurring fabrications

Seen repeatedly, worth checking every time
Invented advisors
Most common
Real names and photographs used without permission. Costs nothing to fabricate and lends enormous credibility. Always verify at least one directly.
Inflated former employers
Very common
A three month contract becomes "led engineering at". Independent traces of senior roles are the check.
Fake audits
Common
A logo, or a report for a different contract address entirely. Verify on the auditor's own site and confirm the address matches the deployed one.
Purchased media coverage
Common
"As featured in" linking to paid placement. Check whether the piece is bylined by a real journalist and reads as reporting rather than a press release.
Borrowed team photographs
Declining but present
Reverse image search catches it immediately, which is why it is becoming rarer.

What actually predicts a team will not vanish

Ranked by usefulness: a shipped previous project that still runs; multiple years of public contribution under the same identity; public appearances where they answer hostile questions unscripted; and reputational exposure they cannot cheaply abandon. Note that none of those is a photograph or a job title.

READ NEXT

BEFORE YOU MOVE ON

Common questions

Is an anonymous crypto team a red flag?

It depends entirely on what power they hold. Anonymous with immutable contracts and no treasury is defensible. Anonymous with a single wallet controlling upgrades or minting is disqualifying.

How do I check a crypto project's GitHub?

Look at commit frequency over time, how many distinct contributors there are, whether issues get responses, whether it is a fork, and when the last commit was. You never need to read the code.

Are crypto advisor lists reliable?

They are the most frequently fabricated section on any project site. Message one advisor on their own established account and ask. It takes minutes and people do reply.

Risk warning: crypto is highly volatile and largely unregulated. You can lose everything you put in. Nothing here is financial, investment or tax advice.

← PREVIOUS
Reading a whitepaper without being sold to
NEXT →
Supply, unlocks and dilution: the maths that decides most outcomes