The ticker is not enough.
A ticker, logo, chart image, or social handle can be copied. The first public-proof habit is to identify the exact contract or mint address and treat every other claim as secondary until that identifier is anchored.
One exact address that appears consistently across the project's official surfaces and public references.
Different addresses in replies, screenshots, Telegram messages, or link previews that ask you to act quickly.
Start from a page the project controls.
A token reference is stronger when it is anchored to an official website, documentation page, or public project channel. A repost can be useful for discovery, but it should not become the source of truth.
A stable source page that states the address and links to the relevant explorer or official route.
Only seeing the address in cropped graphics, influencer posts, replies, or messages that cannot be independently checked.
The path matters as much as the promise.
Even when the address is correct, route confusion can still create risk. The public route should explain where a user is expected to verify, inspect, or trade, and it should not depend on private instructions.
Official links to the route, explorer, or reference page, with the same token identifier visible at each step.
A page that pushes urgency before showing the exact token, public route, and reason the link is official.
Authority state is not small print.
Mint authority, freeze authority, upgradeability, liquidity locks, and holder concentration are not automatic good-or-bad labels. They are control signals that deserve plain-language context before a user treats the chart as the whole story.
Clear explanation of the visible control state and where it can be checked publicly.
"Trust us" language when meaningful controls are still active or unexplained.
Good research should survive a refresh.
A token story changes quickly. If something important changes tomorrow, there should be a public place to verify what changed, when it changed, and whether the source, route, and controls still line up.
A public update trail, proof pack, or watchlist habit that lets the same token be checked again later.
A decision that relies on memory, old screenshots, or a reply thread that no longer matches the current state.