FOXSCAN
Evidence, not vibes Methodology overview — not a live scan

FoxScanner Signal Room

A risk verdict should show its work.

FoxScanner follows the holder picture behind a newly launched BNB Chain token: where supply moved, which wallets appear related, and how concentrated the result is.

Example evidence graph: launch transaction paths resolve into related wallet clusters and a holder-risk verdict.
Illustrative methodology Static example — no live wallet data
01Transaction 02Wallet 03Cluster 04Verdict

How the scan works

Evidence moves forward. Assumptions do not.

Four deterministic stages turn on-chain holder evidence into the risk band shown on a token report.

  1. Launch context

    Locate the starting point

    Identify the supported launch source and earliest relevant transfers available to the scan.

    Report outputLaunch source and timing context

  2. Transfer trail

    Trace where supply moved

    Read token transfers from launch into the wallets that make up the current holder picture.

    Report outputSnipers, fresh wallets, and concentration

  3. Wallet relationships

    Group connected behavior

    Use observable transfer relationships to surface wallets that may act as one holder group.

    Report outputLinked-wallet clusters and combined share

  4. Holder-risk verdict

    Resolve the evidence

    Apply the same holder-risk rules to the available evidence and keep unavailable fields visibly unknown.

    Report outputRisk band, score, and contributing signals

Scan boundaries

Know exactly what the verdict covers.

A clean holder picture does not clear risks that sit outside holder and transfer analysis.

Included in this signal

What we check

  • Linked walletsObservable transfer relationships between holders.
  • Sniper activityEarly acquisition patterns visible to the scan.
  • Fresh walletsWallet age and activity context where available.
  • Supply concentrationHolder share, including related-wallet groupings.

Outside the current signal

What we do not check

  • Contract ownershipOwner privileges and administrative controls.
  • Mint permissionsWhether supply can be expanded by contract logic.
  • Honeypot behaviorWhether buyers can sell under every contract condition.
  • Transfer taxesBuy, sell, or dynamic fee behavior.

Use the verdict as one input. Review contract-level risks separately before making a trading decision.

Scoring principles

Rules before reputation.

The holder-risk verdict is designed to be reproducible, independent, and explicit about missing evidence.

01

Same inputs. Same rules.

Supported tokens pass through the same holder-risk method. Project identity does not change the rules.

02

Payment cannot change the verdict.

Commercial relationships, verification, or paid token-page features do not improve the holder-risk score.

03

Unknown stays unknown.

Unavailable or incomplete evidence is labeled as such instead of being treated as favorable.

Evidence sources

Each source has a job.

Source availability varies by token. Names below describe data roles and supported contexts, not endorsements or partnerships.

Launch context

four.meme · Flap · Genius.fun

Identify supported launch origin and early context when available.

On-chain evidence

BNB Chain

Read transfers, holders, and observable wallet relationships.

Market context

GeckoTerminal · DexScreener

Add market and pool context where a matching source is available.

Contact and accountability

Route the signal to the right conversation.

FoxScanner currently handles these conversations through X. Choose the intent so the request is clear before you leave the site.