Checking who is actually behind a project
- Author
- CRYPTO PORT Editorial
- Published
- Updated
- Reading time
- 6 min
In short
What you can establish about a project's operators comes from what they have published: the official site, documentation, company registrations and public announcements. Names and photographs are not proof of substance, and anonymity is not proof of fraud. What you can assess is how much has been disclosed and whether it hangs together.
Key points
- Work in order: official site, published docs, any company or registration details, then whether other public sources agree
- A claimed background means something only when it matches what the named organisation itself has published
- Stolen photographs and invented résumés are a known pattern — look for what fails to line up
- Do not investigate individuals; keep to what has been officially published
Definition
Assessing the entity behind a project from officially published information — how much is disclosed, how specific it is, and whether independent public sources agree.
Begin by reaching the real official site — through a pinned post on the project's own account or a link in its documentation, not through a search advert. Get this wrong and everything you then read about the team is a fake site's text. Make checking the domain letter by letter a habit.
Then read what has been disclosed. If a company operates the project, you may find a legal name, an address and a registration number. Where those exist, check the relevant country's public company or business registry for the same name and number. Where they do not exist at all — or there is a company name with no address and no number — the finding is that there is nothing to check against.
Next, look at what is said about people. Where names and backgrounds are published, the way to test them is to see whether the organisations or events named have themselves published the same thing. What matters here is restricting yourself to what the person has put out publicly. Digging into private life or inferring undisclosed attributes is not a use we endorse, and a wrong identification harms a real person.
Then check consistency over time. Do site updates, documentation revisions and announcement history match the claimed history? If a project says it has been building for years but everything public dates from the last few weeks, that mismatch is itself the finding. Repository activity and domain registration dates help with the same comparison.
Finally, what none of this tells you. A real company can still fail. A verifiable résumé does not mean funds are handled properly. And some well-known projects are run anonymously. What you get here is one thing only: whether the story and the public record contradict each other. It is not a forecast of success or safety.
Watch out for
- · Do not try to infer a person's address, family or employer; a wrong identification does real harm
- · Published names and faces prove nothing — photographs are trivially stolen
- · Nor can anonymity alone establish fraud. Judge by the consistency of what is disclosed
Frequently asked questions
Should I avoid projects with anonymous teams?
The risk is less the anonymity itself than not knowing who is answerable, or how to reach anyone, when something goes wrong. Some anonymous projects offset this with open code, transparent treasury handling and a long public record. Decide on the basis of how much you were actually able to confirm.