How to Do Your Own Research (DYOR) on a Token

DYOR is the phrase people use for doing research before buying, and the phrase is often used to describe something much weaker than actual research: reading a thread.

Here is what genuine research on a token involves, in the order that saves the most time.

Start with what the token is for

Read the documentation, not the marketing. A token that describes itself as a "decentralised solution for" a problem nobody has is telling you something.

The useful questions are concrete: what does a holder actually do with it, what revenue does the protocol earn, and what would break if the team stopped building.

Look at the supply

Total supply, circulating supply, and the unlock schedule. Then look at who holds the rest.

The number that matters most is concentration. A handful of wallets holding most of the supply means those wallets can sell into any liquidity that exists. Check the distribution before reading anything else about the project.

Find the treasury and the team's wallets

Projects publish a treasury address. Watching it shows you when the team is selling or deploying, which is usually before any announcement.

Team wallets matter for a different reason: if a large holder dumps, the price moves regardless of what the roadmap says. Read where the tokens are, not who the team says they are.

Read what the contract can actually do

Token approvals and contract functions are where losses happen. A contract that can restrict transfers, or mint new supply, is a materially different risk from one that cannot.

Check whether the contract can be upgraded and by whom. An upgradeable contract means the rules can change after you have bought.

Separate what you know from what you are told

Distinguish verified facts from claims. On-chain data is verifiable. A partnership announcement is a claim. A roadmap is a claim.

Write down which is which, and size your position according to how much of your thesis rests on the claims.

Decide before you buy

DYOR is only useful if it changes what you do. Decide the size, the entry, and the condition that would make you exit, before the position exists.

A short record is not a bad sign

A team that has been working for a year with nothing shipped is not necessarily dishonest. It is also not yet a product.

The question is whether the work so far demonstrates the ability to ship. A public repository with regular commits and working software tells you more than a roadmap slide.

Reading the treasury flow

Transfers from the treasury to an exchange usually mean selling. Transfers to a published bridge or to a known exchange address mean funding operations. Watching the direction over weeks gives you an early signal that announcements do not.

What to do with the conclusion

Write down the two or three claims your thesis depends on, and note which are verified and which are not. Size the position according to how much of it rests on the claims.

That single step does more than any amount of further reading, because it converts research into a decision with a defined risk.

Separating fact from claim

Keep the two categories separate:

• Verified: on-chain supply distribution, unlock schedules, treasury movements.
• Claims: partnerships, listings, roadmap items, anything from marketing.

Frequently asked questions

Is reading the whitepaper enough?

No, and a whitepaper is usually the least informative document a project produces. The verifiable material is on-chain: who holds the supply, when it unlocks, and where the treasury has moved.

How do I check if a token is a rug pull?

Look at holder concentration first. A few wallets holding most of the supply, thin liquidity relative to the headline valuation, and an unlock schedule that releases a large share soon are the patterns that precede most losses.

What does an upgradeable contract mean for my position?

It means the rules can change after you buy. If the contract can be upgraded, ask who holds that authority and whether there is a timelock, because an upgrade can introduce transfer restrictions or minting that were not in the original code.