How to a Project Evaluate

Second lens, and you already own the tool for it. In the tokenomics lesson you learned to read a token like plumbing: faucets pour supply in, drains pull it out, and the float is only the sliver trading right now while most of the tub can be waiting offstage.

Tap each row to see the token checks, and the selling-pressure flag nobody in the pitch will mention.

Third lens: is anyone genuinely using this thing? This is the find-the-tenant question from the earning lesson, pointed at usage instead of yield. Real traction is people who would stay if the rewards stopped. Manufactured traction is activity that exists only because the project is paying for it.

On-chain activity can be read on a block explorer, but you have to read it honestly. A thousand transactions from five wallets cycling tokens is not a thousand users. A subsidy can rent a crowd, and the crowd leaves with the subsidy.

Last lens: the security posture. In the previous checkpoint you learned the difference between the word audited printed on a landing page and a published report you can actually open: who reviewed it, what scope they covered, and whether the issues they found were fixed.

Tap each row to see the trust checks, and the flag a confident logo cannot cover.

Most red flags are reasons to look harder. A few are reasons to stop. These are the disqualifiers, and the rule is simple: any single one of them, on its own, ends the conversation. You do not need all four lenses to come back clean to walk away. You need one of these to come back true.

There are three. An anonymous team making claims you cannot verify while the treasury is already unlocked and movable. A yield where you cannot name a single payer. A selling-pressure schedule that the project itself never mentions. None of these needs a second opinion.

Here is a project page on the bench. Every detail is invented, but each one has real cousins you will see on any given week: a loud headline, anonymous handles, a thin float with an unmentioned unlock, activity that started with the rewards, and the word audited with no report behind it.

You are not guessing now. You have four lenses and a list of disqualifiers. Run them on the page and say what it tells you.

Now the same four lenses on a different, also fictional, page. The method is not only a way to find bad projects. It is a way to see what an honest one offers, so you know the difference and do not treat every project as a predator.

Team: a public repository with a real history you can read. Token: an unlock schedule published openly, nothing hidden. Traction: people paying to use it, with activity that predates the rewards. Trust: an audit report you can open, plus a bounty and timelocks. Calm where the other page was loud, evidence where it had urgency.

It is tempting to read a clean inspection as a green light to bet everything. That is the one mistake this whole lesson can accidentally cause, and it is worth naming before you leave.

So DYOR finally has a method behind it. You run four lenses in order: team, the verifiable people behind it; token, the plumbing and the hidden unlocks; traction, real usage versus rented activity; trust, the security posture you can actually open. Any one disqualifier ends it early, and a clean pass still gets sized carefully, because the method filters out the bad and cannot certify the good.

But here is the harder truth waiting in the next lesson. You can pick a genuinely good project and still lose money, because the market has its own reflexes that have nothing to do with the project itself.

So the next question is not about any single project. It is about you, and the crowd, and price. Next: why do beginners systematically lose money in these markets, and what small set of behaviors flips the odds?