Token Check

What observable risks exist around this token?

What Token Check is

Token Check is a separate product pillar from Wallet Check. You paste a token contract / mint address and REKT CHECK reports what public on-chain data shows about that token: who holds it, which holders are observably connected, which authorities are still active, how much liquidity is measurable, and whether sell activity has actually been observed.

Token Check is informational and is not investment advice. It never tells you to buy or sell, never labels a token a scam or a rug, and lower observed risk is not the same thing as safe.

Availability

  • Solana — LIVE
  • Base — PLANNED: adapter not implemented, no data is shown
  • Ethereum — PLANNED: adapter not implemented, no data is shown
  • BNB Chain — PLANNED: adapter not implemented, no data is shown
  • HyperEVM — PLANNED: adapter not implemented, no data is shown
  • Robinhood Chain — PLANNED: adapter not implemented, no data is shown

The engine, relationship graph, risk components and UI are chain-agnostic. Each chain needs one adapter; a PLANNED chain never renders as if it had data.

Token identity

  • Name, symbol, mint address, decimals and supply are read from the chain and token metadata.
  • Price, market cap, FDV and the known pool come from observable markets.
  • Token age is the age of the OLDEST observable market for the token, not a claim about when the mint was created.
  • Anything unavailable is shown as UNKNOWN, UNAVAILABLE or UNPRICED. Nothing is invented and nothing missing becomes zero.

Holder distribution and classification

  • The top 20 token accounts are analysed, with the owner resolved where the chain exposes it.
  • Top 1 / 5 / 10 / 20 share of supply is reported twice: RAW (every account) and ADJUSTED (pools, burns and program accounts excluded).
  • Accounts are classified structurally: liquidity pool, burn address, program / contract, authority-linked, custodial or wallet. Unrecognised accounts stay UNKNOWN.
  • Exclusions are always documented on the result page — a pool is market depth, not a holder's position.

Holder relationships and clusters

Relationships are observations, never conclusions. Token Check uses exactly four labels:

DIRECT TRANSFER OBSERVED

This token moved directly between two analysed holders.

FUNDING RELATIONSHIP OBSERVED

A native (gas asset) transfer was observed between two analysed holders.

COMMON DISTRIBUTION SOURCE

Two analysed holders received this token from the same sending address.

CONNECTED

Linked to another holder transitively through the observations above.
REKT CHECK never asserts SAME OWNER, INSIDER or TEAM. Shared transfers are evidence of a connection, not proof of common ownership or intent.
  • Clusters are connected components over those edges, computed on the analysed top 20 holders.
  • A cluster needs at least 2 members and at least one observed edge.
  • Every cluster shows combined balance, combined share of supply, the relationship types involved, the transaction count and a VIEW EVIDENCE drawer with signatures, amounts and timestamps.
  • Relationships are derived from a bounded sample of up to 100 recent transactions involving the mint. Absence of observed links is not proof that none exist.

Creator and authorities

  • Mint authority and freeze authority are read from the mint account. Revoked is reported as REVOKED; present is reported as ACTIVE.
  • Creator / deployer and update authority are reported only when the token exposes a verifiable record — otherwise UNKNOWN.
  • Authority-linked holdings are the share of supply held by addresses that also hold an authority.
  • Authority-linked transfers are counted inside the bounded transaction sample only.

Liquidity

  • Only measurable liquidity is reported: the USD depth visible in observable pools.
  • The primary pool, market/DEX, pair and pool age are shown when observable.
  • LP lock status is always NOT VERIFIED. REKT CHECK does not verify LP locks, vesting or ownership renouncement, and never claims a token's liquidity is LOCKED or that a token is SAFE.
  • Measurable liquidity under $25,000 raises a low-liquidity signal.

Sell activity evidence

There is no honeypot simulator and no fake sellability test. Token Check reports buy-side and sell-side movements it actually observed against observable pools inside the bounded sample, how many distinct sellers were seen, and when the last sell was observed.

Fewer than 5 observed sells raises a limited-sell-activity signal. That is missing evidence, not proof that selling is blocked.

REKT Risk is not the REKT Score

The REKT Score is a 0–100 measure of a wallet's trading history. REKT Risk is a separate 0–100 measure of observable risk around a token. They share no math, no inputs and no storage, and neither is a consumer credit score, a creditworthiness rating or a risk rating used for lending, insurance, employment or tenancy decisions.

0–20 LOW

LOW observed risk.

21–40 MODERATE

MODERATE observed risk.

41–60 ELEVATED

ELEVATED observed risk.

61–80 HIGH

HIGH observed risk.

81–100 EXTREME

EXTREME observed risk.
Status: IN VALIDATION. The component architecture and the individual signals are live, but the numeric REKT Risk value and band are NOT published until the formula is validated against documented real cases. Result pages show the measurable signals instead of a number.
  • Concentration — largest holder at or above 20% of supply, or top 10 at or above 50%.
  • Connected holders — largest observed cluster holding 15% of supply or more.
  • Authorities — mint authority active, freeze authority active, or authority-linked concentration.
  • Liquidity — low measurable liquidity.
  • Age — oldest observable market younger than 7 days.
  • Trading evidence — limited observed sell activity.
  • Distribution — unusual distribution shape.

Language we use

  • We say: LOWER OBSERVED RISK, HIGHER OBSERVED RISK, RISK SIGNAL DETECTED, CONNECTED WALLETS, CONCENTRATION, SELL ACTIVITY OBSERVED, AUTHORITY ACTIVE.
  • We never say: SAFE TO BUY, BUY, SELL, SCAM, RUG, GUARANTEED or LOCKED.
  • Low observed risk does not mean safe. Every result carries that statement.

Snapshots, cost safety and refresh

  • Each completed check is stored as a durable snapshot with chain, mint, timestamp, engine version, methodology version, risk methodology version, coverage and source metadata.
  • Viewing a token result reads the snapshot and makes ZERO provider calls.
  • A snapshot is reused for up to 30 minutes; RE-CHECK always runs a fresh analysis and stores a new snapshot.
  • A fresh analysis is bounded: holder depth, the transaction sample and the number of outbound calls are all capped, and every call is recorded in internal provider-cost instrumentation.

Run a Token Check