Getting Started

What Does DYOR Mean, and How Do Beginners Actually Do It?

DYOR means Do Your Own Research. This guide turns the slogan into an actionable checklist for beginners: verifying official channels, reading docs, checking contract verification, and using Etherscan, DeFiLlama, and Dune.

What Does DYOR Mean, and How Do Beginners Actually Do It?

Spend any time in Web3 communities and you will run into these four letters: DYOR. It stands for Do Your Own Research. The phrase appears at the end of project threads, influencer posts, and group-chat shills — sometimes as sincere advice, sometimes as a boilerplate disclaimer.

For beginners, DYOR is not a slogan but a set of concrete actions: before connecting your wallet to a project or buying a token, verify the key facts yourself, instead of treating "someone in the group said it's good" or "a big account is posting about it" as evidence. Web3 has no listing reviews or investor-protection machinery; whatever a project claims is just a claim, and the burden of verification falls almost entirely on you.

This article explains what DYOR actually checks, which tools to use, and the research mistakes beginners fall into most often. One thing up front: research helps you filter out obvious traps, but it is not investment advice — a project can pass every check and still fail.

Why "other people say it's good" is not evidence

Start with one uncomfortable fact: in crypto, the people recommending a project to you often have interests that are not aligned with yours.

  • An influencer's post may be paid promotion, frequently undisclosed.
  • The enthusiastic "community member" may be the project's own staff — or a shill for a scam.
  • Early holders want more buyers so they can exit at higher prices.
  • Even a sincere recommender has a completely different risk tolerance, cost basis, and information access than you.

More importantly, shilling carries no accountability. When a project goes to zero, the posts get deleted and the group chat disbands — but your loss is real. That is why the verification behind every decision has to be your own work: not because everyone is lying to you, but because nobody else is responsible for your wallet.

What basic research covers: an actionable list

Beginner-level DYOR does not require reading code. Do the following things well first.

1. Cross-check the official website and channels

Confirm the project's official URL from multiple independent sources: its CoinGecko/CoinMarketCap page, the bio of its official X (Twitter) account, its GitHub organization page. Copycat domains are the single most common scam technique. Once confirmed, bookmark the site and only enter through the bookmark afterward.

Also judge the quality of the official channels: does the X account have a coherent, long-running history, or was it created a month ago and filled with giveaway retweets?

2. Read the docs and whitepaper

You do not need to understand every technical detail. Focus on: what problem does the project actually solve? What does the token do inside the system (or does it exist only "to go up")? Is the token allocation and unlock schedule clearly stated?

Red flags: documents stuffed with buzzwords that never explain the mechanism, promises of fixed high yields, and pages devoted to price potential rather than the product itself.

3. Check whether the contract is verified

Paste the token or project contract address into Etherscan (or the block explorer of the relevant chain) and check whether the Contract tab shows a verified status — the green checkmark and visible source code. An unverified contract is not automatically a scam, but it means nobody can easily inspect its logic. For a beginner, simply skipping unverified contracts is the safer default.

While you are there, look at the holder distribution on the token page: if the top few addresses hold the vast majority of supply, both dump risk and exit-scam risk are higher.

4. Read the on-chain data

On-chain data does not lie, and a few free tools cover a beginner's needs:

  • Etherscan: contract verification status, holder distribution, transaction activity, contract creation date.
  • DeFiLlama: TVL (total value locked) trends for DeFi projects. Steady, diversified TVL growth is healthier than a single sudden spike — and whether a project is listed on DeFiLlama at all is itself a basic signal.
  • Dune: community-built dashboards. Search the project name and look at real user counts and retention, to judge whether the "hype" reflects genuine usage.

You do not need to master these tools. Being able to ask "is the trend healthy, and does the data match the marketing?" already puts you ahead of most people.

5. Look at the team and audits

Is the team public or anonymous? A public team's track record can be checked. Anonymity is not proof of a scam — Web3 has a long anonymous tradition — but the combination of anonymity, high-yield promises, and pressure to act fast is extremely dangerous.

On audits: has the project published an audit report, and from which firm? Note that "audited" does not mean "safe" — an audit covers a specific version of the code, and plenty of exploited projects had audits. Treat an audit as a plus, never as a guarantee.

6. Screen the community discussion

Join the project's Discord or Telegram, and ignore the member count — look at the quality. Is the discussion about the product and technology, or wall-to-wall "to the moon" and price shilling? Are skeptical questions answered seriously, or do the skeptics get banned and dogpiled? The latter is a classic warning sign.

Common research mistakes

  • Only looking at the price chart: early-stage prices are easy to manipulate. A rising chart does not mean a good project — honeypot tokens typically "only go up" right until they are exposed.
  • Treating influencer posts as research: retweeting a thread is not DYOR. Paid promotion and undisclosed incentives are pervasive in this industry.
  • Relying on a single source: the project's own marketing is always the most flattering version. Cross-check with at least two or three independent sources.
  • Treating "listed somewhere" as an endorsement: being tradable on a DEX or indexed by a data site has a very low bar and proves nothing about quality.
  • Researching once and relaxing forever: projects change, contracts get upgraded, teams turn over. Keep paying attention while you hold.

Checklist before you decide

  • The official URL is cross-confirmed by at least two independent sources and bookmarked.
  • You have read the docs and can explain in one or two sentences what the project does.
  • The contract is verified on a block explorer, and holder distribution is not extremely concentrated.
  • You have looked at the data on DeFiLlama/Dune and it broadly matches the marketing claims.
  • You know the team background and audit status — and you know an audit is not insurance.
  • The community tolerates skepticism, and discussion is not only about price.
  • Even if everything passes, you only commit a small amount you can afford to lose, ideally through an isolated wallet.

FAQ

Does DYOR require reading code? No. Beginner-level DYOR is mostly information verification: official channels, documentation quality, contract verification status, on-chain data, and community tone. None of that requires code, yet it filters out a large share of obvious scams.

Am I safe once I have done my research? No. Research lowers the odds of stepping into a trap; it cannot remove risk. Projects fail for market, technical, or team reasons — which is exactly why you only ever commit money you can afford to lose.

Should anonymous-team projects always be avoided? Not necessarily; anonymous building is a Web3 tradition. But anonymity makes accountability harder if things go wrong, so weigh it together with other signals and size your exposure down accordingly.

What if there is too much information to process? Flip the approach: look for dealbreakers first. An official site that cannot be cross-confirmed, an unverified contract, a community that bans skeptics — any single one of these is reason enough to walk away. That is more practical than trying to "understand everything."

References