A consistent, research-driven process behind every rating and review.
Founder credibility, doxxing status, and past track record.
Supply, vesting schedule, allocation fairness.
Third-party audits and known red flags.
Engagement quality and realistic delivery timelines.
Our crypto presale review methodology is built around a fixed set of criteria applied to every project we evaluate, so that a well-marketed presale and a quiet one are judged by the same standard. This page walks through exactly what we check, how we weigh it, and where the limits of any review process sit, since no methodology can eliminate the underlying risk of early-stage crypto investing.
A review on this site is meant to give a reader a structured, evidence-based picture of a project's design and risk factors before they decide whether to research it further, not a prediction of future token price. We separate what is verifiable, such as whether a contract has been audited, from what is promotional, such as a project's own claims about its future growth. Distinguishing between those two categories is the core function of the methodology described here.
Every presale we review is assessed across the same five categories:
We look at total supply, allocation across team, investors, treasury, and public sale, and the vesting schedule attached to each allocation. Projects with large team or investor allocations unlocking quickly, relative to the public sale, are flagged as a structural risk, since that combination can create sustained sell pressure once tokens unlock. We also check whether the stated tokenomics in the whitepaper match what is actually encoded in the smart contract.
We check whether a project has a completed third-party audit, who performed it, and whether the audit covers the specific contract version currently in use for the presale. An audit from a recognized firm covering the live contract carries more weight than a self-reported or unnamed audit. We also note any unresolved high-severity findings disclosed in the audit report itself.
This draws on the process described in our team verification page. We note whether the team is publicly identifiable with a checkable history, partially transparent, anonymous but third-party verified, or fully anonymous, and we treat this as one input among several rather than a standalone pass-or-fail filter.
We assess whether the project's stated use case matches what the tokenomics and technical documentation actually support, and whether the roadmap contains specific, checkable milestones rather than vague long-term promises. A roadmap with concrete near-term deliverables tends to be a stronger signal than one focused entirely on distant, unspecified goals.
Rather than counting followers, which can be purchased, we look at whether the team communicates directly and substantively with its community, including how they respond to hard questions in open channels like Discord or Telegram AMAs. Consistent, direct communication over time is weighted more heavily than short bursts of promotional activity around a launch.
Each category contributes to an overall assessment, but we do not reduce a review to a single misleading composite number presented without context. A project can score well on tokenomics and audit status while still carrying real team-transparency risk, and our reviews are written to reflect that nuance rather than average it away. Where a project fails a category outright, such as having no audit at all for a live public sale, that is called out explicitly rather than blended into an overall score that might obscure it.
Reviews draw on the project's own whitepaper and website, the deployed smart contract, published audit reports, on-chain data such as wallet distribution where available, and direct engagement with the project's team or community channels. We do not rely solely on a project's self-reported marketing materials, and where a claim cannot be independently verified, the review says so rather than treating it as confirmed.
Presale projects evolve, sometimes quickly. A review reflects the information available at the time it was last checked, and we note the review or update date so readers can judge how current the analysis is. Significant developments, such as a new audit, a change in tokenomics, or a security incident, can prompt an update outside of a regular review cycle.
No review process can predict whether a project will succeed, whether a team will follow through on its roadmap, or how a token will perform after listing. Presale investing carries a high risk of partial or total loss regardless of how a project scores in our review, and nothing on this page or in any review should be read as investment advice or a guarantee of outcome. The purpose of this methodology is to make the checkable facts about a project easier to find and evaluate, not to remove the underlying uncertainty of investing at an early stage.
No. Review scores are produced independently of any advertising or sponsorship relationship, as set out in our editorial policy.
We note this in the review itself. Limited team responsiveness is treated as a relevant data point rather than being left out.
No. We prioritize projects based on reader interest, available public information, and team responsiveness, since a review depends on having enough verifiable material to assess.
Each category feeds into an overall assessment, but reviews are written to preserve important nuance, such as a project scoring well on tokenomics while still carrying real team-transparency risk, rather than blending everything into one number that could obscure a category failure.
We check the deployed contract's supply, allocation, and vesting logic directly where possible, rather than relying solely on the figures presented in a project's whitepaper or marketing materials.
It is treated as one of five core inputs rather than a standalone pass-or-fail filter, so a project with limited team disclosure can still be evaluated on its tokenomics, audit status, and roadmap credibility.
Every review notes the date it was last checked, and we update reviews outside the regular cycle when a significant development occurs, such as a new audit or a security incident.
"