CASE DESK 4663 · R1

RH Deep
Dive

Performance claims under pressure. Token-launch relationships under evidence.

READ THE LABEL, NOT THE VIBE.

Risk scores are defensive screening signals. They do not prove fraud, criminal conduct, common control, or identity.

PERFORMINGevidence-qualified participants
CASEStoken-risk candidates
CORROBORATEDmulti-signal hypotheses
ACTIVE ALERTSconfidence-gated triggers
ROTATORStagged wallet hypotheses

TRACK A

The public record,
after friction.

Participants appear only when timestamped, source-linked, execution-realistic records support the calculation. Screenshots and isolated winners do not qualify.

TRACK D

Connections in ink.
Uncertainty intact.

ENTITY RELATIONSHIP GRAPHEDGE WIDTH = CONFIDENCE
ACCUMULATION / DISTRIBUTIONPUBLIC DEX-LINKED EVIDENCE
ANNOTATED EVIDENCE TIMELINELAUNCHES · LIQUIDITY · ROTATIONS · ALERTS

TRACK C

Watch the baton.
Tag the hands.

Wallets appear only after repeated sell→buy sequences across different tokens touch labeled DEX infrastructure. Tags describe the on-chain role; they do not identify a person.

TRACK B

Follow the links.
Respect the gaps.

WATCH WIRE

Signals that clear
the confidence gate.

No alert is an accusation. Each one carries an alternative explanation and a lawful defensive action.

METHODOLOGY

Evidence has
a hierarchy.

Every major finding uses one grammar: conclusion, status, evidence, confidence, alternative explanation, limitations, next validation step.

01

Separate the scores

Performance is not evidence quality. Contract risk is not attribution confidence. Completeness changes certainty, not the underlying observation.

02

Require independent links

Common funding plus shared authority may support a cluster hypothesis. One router, template, or synchronized block does not.

03

Net the money

Extraction ranges subtract documented capital, liquidity, gas, and costs. Transfers inside the same proposed cluster are removed once.

04

Preserve unknowns

Missing evidence stays unknown. The system never substitutes zero, invents a fill, assumes a wallet owner, or infers Robinhood usage from asset availability.

05

Prove the handoff

A displayed rotation requires at least two transaction-linked sell→buy legs across distinct tokens. One transfer, one price pump, or a shared router is not a rotation pattern.

LIVE SOURCE REGISTER

IMPORTANT LIMITATIONS