Check a crypto project by verifying its identity, deployed product, token mechanics, control permissions, and claims through appropriate independent evidence. No single badge or checklist proves legitimacy or investment quality. Record what is confirmed, what is uncertain, and which risks remain before committing money.
Replace a vague verdict with specific questions
Legitimate can mean several things: a real team, functioning software, accurate disclosure, lawful activity, or an investment that fits your needs. Those are separate questions. A project can satisfy one while leaving another unresolved.
Write down the decision you are considering. Buying a token, using a protocol, providing liquidity, and accepting a private investment offer create different exposures. The evidence needed should match that action.
List the material claims: who operates it, what exists today, why the token is needed, who can change the rules, and how users recover assets. Distinguish implemented features from roadmap promises.
Use a record with three categories: verified observation, project assertion, and unresolved question. This prevents a claim repeated across several promotional pages from being mistaken for several independent confirmations.
Verify identity and relationships
Locate the official domain, documentation, named operators, and relevant entity information. Compare them across independently reached sources. Copied corporate information or a recognizable brand reference does not establish the page's actual ownership.
If the team describes prior work, find the original organizations and records. A biography hosted only on the project's own page is a claim to investigate. Lack of public names is a limitation to assess rather than automatic proof of a crime.
For partnerships, obtain confirmation from the named partner where possible. A logo, sponsored event appearance, or technical integration can each mean something different. Specify which relationship the evidence actually supports.
If authorization or registration is claimed, verify the exact entity, jurisdiction, product, and permitted activity through the relevant official source. Do not assume a corporate registration authorizes every financial offering globally.
Watch for urgency, guaranteed returns, and pressure from a private relationship. Investor education guidance describes how confidence can be built before directing funds to a fraudulent destination. Familiarity with the promoter is not independent evidence.
Inspect what users interact with today
Find the deployed contracts or functioning product corresponding to the documentation. A public repository can show development work without proving the deployed version matches that code.
Contract verification can help compare published source with a deployment. It does not itself certify the economic design or remove dangerous privileges. Identify the relevant version, network, and any upgrade mechanism.
Read what an audit covered, which code version was reviewed, and what findings remained. Locate the report through the auditor's official channel where possible. Audits have limits, including components and later changes outside their scope.
If the product relies on a bridge, oracle, administrator, or external custodian, include that dependency in the investigation. A decentralized label does not establish equal independence across every component.
Use public records to check concrete activity, but do not overinterpret them. Transactions and addresses can show movements without revealing real customer demand, real-world ownership, or the purpose of every action.
Follow the token's economic rights and controls
Ask what owning the token permits. Governance participation, access to a feature, a redemption claim, and a revenue expectation are different arrangements. Read the actual rights rather than inferring them from a slogan.
Check supply, allocation, and release rules against official documentation and current data where available. Large holdings, future releases, or changeable issuance can affect exposure, but a single ownership statistic requires context.
Identify privileges such as minting, transfer restrictions, fee changes, pauses, and upgrades. Determine who can exercise them and through what process. If you cannot interpret a material permission, record the need for qualified analysis.
For a product promising yield, identify who pays and what activity creates it. Token incentives, borrowing interest, and trading fees have different economics. An annualized headline is not a guaranteed personal return.
Inspect an exit route. A quoted price needs sufficient liquidity for your size, while a redeemable product needs conditions and available assets. A successful deposit does not establish that withdrawal is immediate or unconditional.
Use an evidence worksheet
- Describe the intended commitment, including asset, amount scope, platform, and network. Keep it separate from a price prediction.
- List the claims that would materially influence that commitment. Prioritize custody, permissions, source of return, and exit.
- For each claim, record the original source and an appropriate independent check. State exactly what the check establishes.
- Mark contradictions and missing data. Do not fill gaps with assumptions borrowed from a similarly named project.
- Identify the consequences if a claim is wrong or a control is misused. This turns an abstract concern into a practical exposure.
- Decide whether the evidence is sufficient for your task. Choosing not to proceed while an important point is unresolved is a valid outcome.
Keep the conclusion narrow and current
Write a dated conclusion that names both established facts and unresolved risks. Avoid turning a completed checklist into a universal safe label. Project operations, permissions, and liquidity can change.
A market loss does not by itself prove fraud, and a rising price does not validate a project. Use observed actions and documented claims when discussing potential misconduct.
If you need to report a suspected scam, preserve the domain, communications, contracts, addresses, and hashes. State observations clearly without inventing intent or real-world identities you cannot establish.
Do not pay an unsolicited investigator who promises guaranteed approval or recovery. Public project analysis should not require your wallet's secret material.
A useful review leaves you able to explain what the project does, what power insiders retain, what evidence supports its claims, and what could prevent your intended exit. That is a concrete basis for further decisions without pretending uncertainty has disappeared.
If two sources repeat identical claims, investigate whether they share an origin. Syndicated announcements and paid promotional articles can look like independent corroboration while adding no new evidence. Follow a claim back to the original statement, then seek a source able to confirm the relevant fact. For example, a claimed partnership should be checked with the named partner, while a deployed contract should be compared with the project’s actual network instructions. Record the scope of that confirmation. This keeps the review focused on evidence quality rather than the number of pages mentioning a project.
Reader questions
Does exchange listing prove the project is safe?
A listing has a particular scope and does not establish every aspect of product quality, permission risk, or suitability.
Is an anonymous team automatically fraudulent?
Anonymity limits some checks but is not proof of intent. Evaluate the specific controls, evidence, and exposures.
Can a whitepaper replace looking at deployed contracts?
No. It describes a design or proposal. Implementation and current operation need their own evidence.