Deployer records · Robinhood Chain

Every wallet they run. Not just the one you're looking at.

Serial deployers rotate addresses. VOUCH maps the cluster behind a contract, scores it against what the rest of the chain actually does, and shows the evidence for every link.

Established Caution Pattern detected No record
Coverage
Genesis
Deployers on file
0
Clusters mapped
0
Cohort graduation rate
0

No recordInsufficient sample

01 — Verdicts

Four states, and only one of them is a pass

Most scanners have two settings: fine and scam. That guarantees a fresh wallet looks safe on its first launch, which is precisely when it isn't.

No record

Fewer than five launches. Not a warning and not a clearance. There is simply nothing here to judge yet.

  • Never rendered as a pass
  • Most first-time deployers land here
  • So does every fresh scam wallet

Established

Earned, not defaulted into. Requires positive evidence across a real sample.

  • Five or more launches
  • Graduation rate above cohort median
  • No sells into own liquidity
  • No sub-hour abandonments

Caution

One confirmed signal, or a cluster tie strong enough to matter but not to conclude.

  • A single confirmed signal
  • Or a cluster link above 70%
  • Evidence always named

Pattern detected

Repetition across a cluster, not a single bad launch. The bar is deliberately high.

  • Two or more confirmed signals
  • Corroborated across linked wallets
  • Minimum sample enforced
02 — Signals

Weighted by how much they actually prove

Pons locks liquidity permanently at graduation, so creators cannot pull it. Anyone selling you a "liquidity pulled" metric on this chain has not read the contracts. These are the vectors that exist.

01

Sweep consolidation

Where proceeds end up. Deployers rotate launch wallets constantly and almost never rotate the address the money lands in.

Strong
02

Fee-recipient reuse

Pons pays 70% of trade fees to the creator. That destination is set once and forgotten across dozens of launches.

Strong
03

Creator sells

Buying your own launch at block zero and selling into the buyers who followed. Timestamped against the launch block.

Strong
04

Funding timing

Wallets funded in the same block, or minutes apart, from a source that funds few others.

Moderate
05

Abandonment rate

Launches left inside an hour. Common enough across the chain that it only carries weight in volume.

Moderate
06

Shared funder alone

Bridges and exchange hot wallets fund thousands of unrelated people. Corroborating only. Never a link on its own.

Weak
03 — Guardrails

Built to be wrong as rarely as possible

A tool that flags everyone is as useless as one that flags nobody. Three rules do most of the work of keeping honest deployers off the wall.

Rule 01

Base rate, not raw ratio

Most launches die everywhere, on every chain. Three graduations from thirty-four is near normal, not damning. Graduation is scored as deviation from the cohort median, so ordinary outcomes read as ordinary.

Rule 02

High-degree funders excluded

Any address funding more than roughly fifty distinct wallets is dropped from the cluster graph entirely. Without that rule, one bridge merges half the chain into a single imaginary person.

Rule 03

No verdict without a sample

Under five launches there is no pattern, only noise. Those wallets return no record, which is an honest answer rather than a flattering one.

Rule 04

Evidence or it doesn't ship

Every link carries the specific finding that produced it and a confidence score. A 96% sweep tie and a 58% funding coincidence are different claims, and the record says which one you're reading.

04 — Access

The record is free. Speed is the product.

Anyone can look up any deployer, forever, without a wallet. Charging people to find out they are about to be robbed would defeat the point of building it.

Public windowNo token required

Any contract, full deployer record, cluster map, and the evidence behind every link. No wallet connection, no signup, no rate limit worth mentioning.

FreeAlways

ClearanceHolder tier

Live alerts the moment a watchlisted deployer or anything in their cluster touches the launch factory.

50,000VOUCH held

RegistrarHolder tier

The raw feed and the scoring API behind it, plus your own calls timestamped on the public record.

500,000VOUCH held

Every alert sent is paid in VOUCH and destroyed on delivery. Supply falls as a direct function of how much the terminal actually gets used, and only then. A burn with no usage behind it is just a smaller pile of nothing.

Open the terminal