A useful Solana token review begins with a precise identity and a record of permissions. Price, a familiar symbol, and an active community do not answer who can create more units, restrict transfers, or remove a trading route. Those questions belong in the first screening pass because they determine which later observations are meaningful.

The goal is a dated evidence record that another reader can reproduce. Start with the Solana screening criteria, then build a separate note for identity, control, supply, holders, and execution. This workflow is an educational method for investigating a candidate; it does not turn a completed checklist into a prediction of price or a recommendation.

1. Establish the exact mint before reviewing the story

Copy the full mint address into the review and record the network, token program, observation time, and source of the address. Check that project materials and the market being examined identify the same mint. Preserve the full address even if your working view displays a shortened form. If two sources disagree, keep the discrepancy open until the identity can be resolved.

In its official token documentation, Solana explains that the mint account identifies a token and stores supply, decimals, mint authority, and freeze authority. Mint authority permits the creation of additional units; freeze authority can prevent transfers or burns from affected token accounts. A token account records units held for a particular owner and mint. These are distinct records, so the wallet holding tokens is not automatically the party controlling issuance.

Use that distinction to label screenshots and exports accurately. A balance view should identify its owner and mint. A control view should identify the role being inspected. Avoid a single field called “owner,” which can conceal different questions about account ownership, program control, and project administration.

2. Build a permission table with an explanation for each role

For every permission visible in the relevant mint and program configuration, record the controlling address, its apparent arrangement, and the evidence supporting that interpretation. Use descriptions such as “address present,” “role absent,” or “control arrangement unverified.” A recognizable address label is a research lead, not evidence that the claimed organization currently controls it.

  • Issuance: identify who could approve additional units and the documented circumstances for doing so.
  • Transfer restrictions: identify the permission, affected accounts, and stated reasons it might be exercised.
  • Changes: inspect any additional controls associated with the actual token program and configuration.
  • Accountability: record who explains the policy, where changes are announced, and what evidence would confirm implementation.

Do not treat the absence of one authority as an all-purpose safety result. Your finding should describe the particular permission checked. A retained authority also needs context: compare its technical scope with the project's stated operating model, then explain the exposure created by a mismatch. Where a signing arrangement is claimed, seek evidence of its participants and approval rules without requesting private keys or confidential signing material.

Resolve disagreements between observations

If two readers report different authority states, compare the network, full mint address, observation time, and program interpretation before drawing a conclusion. Preserve both results and identify the smallest repeatable check that could resolve the difference. A refreshed public read may clarify the current state while leaving an earlier change to investigate. Explain which question the new observation answers and which historical question remains open.

3. Reconcile supply figures instead of copying the largest label

Create separate fields for observed supply, the units used to display it, claimed circulating supply, and any stated future issuance schedule. Record how each number was obtained. When a dashboard supplies a circulation figure, ask which balances it excludes and whether that exclusion reflects a verifiable restriction or an editorial assumption.

Reconcile the categories in a small worksheet. Begin with the observed total and list each proposed deduction separately: an identified treasury, a documented distribution reserve, or another clearly described category. For every deduction, retain the amount, evidence date, justification, and uncertainty. Do not subtract a balance twice because it appears under two different labels.

Suppose a fictional review shows units assigned to a treasury and units described as reserved for contributors. The useful question is whether those balances are genuinely separate and constrained, not whether a promotional page calls both “long term.” If the restrictions cannot be verified, present the circulation estimate as unresolved and explain how that affects comparisons. The broader digital asset screening framework helps keep observed facts separate from issuer claims.

4. Examine concentration with an explicit ownership model

A holder table needs interpretation before it becomes a concentration measure. Decide whether you are measuring token accounts, controlling wallets, or groups supported by evidence of common control. Keep those views separate. Label infrastructure balances and possible related holdings only when the classification has a documented basis.

Prepare both an unadjusted view and a clearly explained adjusted view. The unadjusted view preserves what the data actually reports. The adjusted view can exclude a verified liquidity account or group confirmed related addresses, but every adjustment should be reversible. Unknown addresses remain unknown; a suggestive transfer pattern alone should not become a confident identity claim.

Then ask a practical question: which observed balances could plausibly alter available supply or trading conditions if moved? Record scheduled releases, known restrictions, and missing evidence beside the balances. This produces a more useful screening note than assigning a universal acceptable percentage. Different operating models require different interpretations, and a concentration figure alone does not establish intent.

5. Review liquidity at the size and route being considered

Define the transaction size before evaluating liquidity. A displayed price is only one observation; an exit review should document the route, quoted output, fees, time, and conditions attached to that quote. Use an indicative quote or appropriate simulation for research, clearly distinguished from a completed trade. Do not report an estimate as a guaranteed executable result.

Compare several hypothetical sizes using the same observation window and unit convention. Record whether the route changes, whether quoted output becomes materially worse, and whether the available evidence becomes too weak to interpret. Describe the quote asset as well: an apparent exit into another token leaves exposure to that token and to the additional steps needed to reach the intended destination.

Inspect the concentration of the available route. Which pool or venue supplies it, who can alter the relevant arrangement, and what evidence supports any claim that liquidity is restricted from withdrawal? A claim that liquidity is “locked” needs an identified mechanism, scope, and expiry. Write down those details instead of awarding a generic pass based on the word.

6. Read the findings together and preserve unresolved cases

Combine the sections through concrete scenarios. If a documented release occurs, which balances could move and which route would absorb them? If a transfer restriction is exercised, which assumption in the exit review changes? If the main quote asset or venue becomes unavailable, is an alternative route independently supported by evidence?

Use three outcomes for each question: supported, contradicted, or unresolved. Supported means the stated claim has evidence of appropriate scope and freshness. Contradicted means the evidence conflicts with it. Unresolved means a necessary fact remains unavailable or ambiguous. Do not silently convert missing information into either zero risk or proof of misconduct.

Finish with the next useful action: identify a missing account, reconcile a supply mismatch, request a control explanation, or refresh an expired quote. Add the relevant exposures to a portfolio screening record so that shared custody, venues, and quote assets remain visible across otherwise different holdings.

A compact decision note can contain four sentences: the identity checked, the most consequential supported finding, the unresolved issue, and the evidence needed next. For a fictional candidate with a retained issuance role and an unexplained reserve balance, the next step might be to reconcile the reserve and obtain the issuance policy. A conclusion about market attractiveness would go beyond that evidence. This format keeps the review focused on the present decision while preserving a clear route for revisiting it after new information arrives.

Conclusion: make the review easy to challenge

A strong Solana screening note names the exact mint, explains each important control, reconciles supply assumptions, and tests a realistic execution path. Its strength comes from traceable evidence and explicit limits. Keep the dated observations, the interpretation, and the next review trigger together. Another reader should be able to identify both why a finding was reached and what new evidence would change it.