Anti-poser scannerRobinhood Chain · EVM

LARP checkany projectbefore you ape

Paste a URL, an X handle, or a contract address. Get a LARP Score 0–100 and the red flags spelled out in plain English — with the evidence attached, before your money moves.

>paste URL, @handle, or CALARP check→
  • Free checks
  • No wallet needed
  • Public data only
  • ~10 seconds
Reading the public recordlive
  • 01site + whitepapertext, structure, template match
  • 02githubcommits, contributors, forks
  • 03socialsaccount age, history, engagement
  • 04contractsource, authorities, traps
  • 05holdersconcentration, LP, clusters
  • 06dev walletage, funding trail, prior rugs

Read-only. LARPED never connects a wallet to the target, never transacts, and never contacts the project. It reads what anyone could read — it just reads all of it at once.

Public data onlyTouches nothingSignals, not accusationsEvidence on every flagScore is free for everyoneDocs · Code · Socials · Contract · Holders · WalletPublic data onlyTouches nothingSignals, not accusationsEvidence on every flagScore is free for everyoneDocs · Code · Socials · Contract · Holders · Wallet
§01The problem

Buying early
means buying
blind

The signals of a fake project are all public — and all scattered. No single tab shows you every one of them at once.

Checking it yourself is slow and needs expertise most buyers don't have. By the time you've read the repo and traced the wallets, the entry is gone — or you skip the check and ape on vibes.

And the tools that do exist scan exactly one layer: contract safety. A contract can be perfectly “safe” and the project still a total LARP — a poser with nothing behind the marketing.

What you'd have to open yourself06 TABS
  • 01the whitepapera reskinned template
  • 02the githubempty, or a renamed fork
  • 03the x accountthree days old, bought followers
  • 04the contracta mint function nobody mentioned
  • 05the holdersone wallet holds 40%
  • 06the dev walletrugged twice before
→

LARPED reads all six at once and hands you one number with the receipts attached. DYOR was never the problem. The tooling was.

§02How it works

Three steps.
Ten seconds.

No account, no wallet, no configuration. The paste box is the whole product surface — everything else happens on our side, and every result arrives with the public sources that produced it.

  1. 01Paste

    Anything you've got

    A project URL, an X handle, or a contract address. LARPED resolves it into one profile — the site, socials, repo and token that are publicly linked together.

    input · url / @handle / ca

  2. 02Fetch

    Touch nothing

    Site and whitepaper text, GitHub metadata, social account history, contract, holders and the dev-wallet trail — read in parallel, read-only, public sources only.

    read-only · no wallet · no contact

  3. 03Score

    One number, with receipts

    Deterministic rules handle the on-chain layers. A reasoning layer reads docs, code and socials against our private pattern library. Six sub-scores fuse into one LARP Score, a band, and a one-line verdict.

    output · 0–100 + red flags + evidence

§03The score

Low is a LARP.
High is a receipt.

The LARP Score runs 0–100. Low means the project is wearing a costume. High means the public record actually backs the story. It is a risk and credibility signal — never a “buy”.

LARP0–24

Full LARP. Reskin + empty repo + fresh wallet. Walk away.

SUS25–49

Heavy poser signals. A lot here doesn't add up — high risk.

MIXED50–74

Some substance, some red flags. Read the breakdown.

REAL75–100

Low LARP. The public record backs the story. Still DYOR.

Six dimensions, one number

Σ = 100 · weights are a draft, tuned against labeled sets
§01reasoning

Narrative & Docs

20%

Whitepaper and site plagiarism, template reskins, buzzword density with nothing under it, copy-paste About and roadmap sections.

§02rules + reasoning

Code & Build

20%

Does the repo exist and is it real — genuine commits versus an empty shell or a renamed fork, contributor history, last activity.

§03rules

On-chain Contract

20%

Verified source, mint / freeze / owner powers, honeypot and tax traps, proxy and upgrade risk.

§04rules + reasoning

Social Footprint

15%

Account age, post history, organic versus bought followers, engagement realness, sudden manufactured hype spikes.

§05rules

Holder Distribution

15%

Top-holder concentration, LP locked or burned or loose, sniper and bundle clusters at launch.

§06rules

Team & Dev Wallet

10%

Dev-wallet age, prior rugs and serial redeploys, funding trail, linked wallet clusters.

The dimensions are public. The weighting curve is not — that is the part a poser would love to reverse-engineer, and the part they never get. Fake one layer and the other five tell on you.

§04Example report

This is what
comes back

Two illustrative subjects — flip between them. Same engine, same rules, nothing to hide. Every flag in a real report carries a link to the public source that triggered it.

Subject
LARP report — $XYZExample — illustrative data
LARP Score
23/100
LARP

“Full LARP. Reskin + empty repo + fresh wallet. Walk away.”

Narrative & Docs15
Code & Build8
On-chain Contract20
Social Footprint28
Holder Distribution22
Team & Dev Wallet10
Findings05 items

  • Whitepaper matches a known template — 87% structural overlap

    evidence · docs · pattern #f21

  • GitHub repository is empty — 0 commits, 0 contributors

    evidence · github · api

  • X account age: 3 days, follower curve inconsistent with engagement

    evidence · socials · timeline

  • Dev wallet funded by an address tied to a prior rug

    evidence · on-chain · tx trail

  • Top holder controls 41% of supply outside the LP

    evidence · on-chain · holders

Signals from public data at the time of the check. Not financial or legal advice, and not an allegation of fraud against anyone. Scores change — re-check for the latest.

§05The edge

We learned it
from inside
the factory

LARPED's operator ran a template factory: 200+ landing pages and whitepapers shipped to projects. That archive is a map of how fake projects are assembled — not guessed at from the outside, but watched being built.

It became a private LARP-pattern library. The reasoning layer is primed on it, so LARPED recognizes construction patterns that generic scanners have never seen.

  • The reskinned template

    Same grid, same hero, same “as featured in” strip. New logo, new ticker. We know the skeletons by heart.

  • The copy-paste About

    The same three paragraphs circulate across a hundred sites with the noun swapped out.

  • The stock team

    The same portrait assets and the same fake partner logos, reused project to project.

  • The whitepaper mad-lib

    A fixed structure with the ticker find-and-replaced. Section headings never move.

Same skeleton, different logo200+ ARCHIVED
PROJECT A
PROJECT B
PROJECT C

Three different “projects”. One layout, one copy deck, one whitepaper structure. To a buyer they look like three teams. To LARPED they look like one file, renamed.

Public

The six dimensions

Private

Weights + pattern library

§06Safe & legal by construction

A trust product
that defames
real builders dies

So the guardrails are structural, not promises. LARPED is built so that being wrong about an honest project is expensive for us and recoverable for them.

01

Public information only

Everything LARPED reads is already visible to anyone with a browser and a block explorer. Nothing behind a login, nothing private, nothing leaked.

02

Touches nothing

No wallet connected to the target, no transactions, no scraping behind logins, no contacting the project. LARPED observes; it never interacts.

03

Signals, not accusations

Output is framed as risk signals with evidence and timestamps — never a legal claim of fraud against any project or person. Borderline cases lean MIXED, not LARP.

04

Show the receipts

Every flag links to the public source that triggered it, so the reader judges for themselves. There is a dispute path, and a human reviews it.

§07Recent checks
Public feed
Preview — goes live with the scanner
  • $XYZ18LARPrepo deleted mid-check
  • $GHI44SUSLP unlock detected
  • $ABC61MIXEDdocs original, socials thin
  • $DEF88REALrecord consistent across layers
  • $JKL31SUStemplate match 74%

The rows above are illustrative, not real checks — the anonymized live feed switches on when the scanner opens. A product that scores other people's honesty does not get to fake its own numbers, so nothing here is dressed up as activity that hasn't happened yet.

§08$LARPED

The token never
buys the truth

A whale and a free user checking the same project get the same number. $LARPED buys depth, quota, speed and API access — never the score or its correctness. A trust product that paywalls the truth is itself a LARP.

Free

no token, no wallet

  • Daily checks
  • Basic score + top red flags
  • Public report links
  • 3 watchlist slots

Scout

> 0 $LARPED

  • 2× daily quota
  • Full red-flag list
  • Holder badge

Sleuth

≥ 100k $LARPED

  • Unlimited checks
  • Full evidence deep-dive
  • 25 watchlist slots + alerts
  • History export

Hunter

≥ 1M $LARPED

  • API access
  • 200 watchlist slots
  • Dev-wallet cluster trace
  • New-detector early access

Oracle

≥ 10M $LARPED

  • High-rate API
  • White-label score badge
  • Unlimited watchlist + batch
  • Detector roadmap signal

Tier checks read your live on-chain balance — no staking, no lockup. API can also be bought in stables; the token gives a discount, never a forced purchase.

Launch terms — posted before, not after
Supply
1,000,000,000 — fixed
Launch
Fair launch on pons.family
LP
Locked permanently — no withdrawal function
Pre-mine
0% — creator bundle ≤5%, bought at market, disclosed
Emissions
None. Zero inflation, forever
Buyback
15% of revenue market-buys, txs traceable
Contract address

CA drops at launch

$LARPED has no contract address yet. It will be announced only from @larped_fun and t.me/larped_fun, and posted here. Anyone offering a presale, a whitelist or an “early CA” is running the exact play this scanner was built to catch.

§09FAQ

Questions
worth asking

If a tool judges other people's credibility, it had better be able to explain itself.

01What is a LARP Score, and does low mean good or bad?
It is a 0–100 credibility signal. Low means more LARP — more poser signals, less substance. High means the public record backs the project's story. 0–24 is LARP, 25–49 SUS, 50–74 MIXED, 75–100 REAL. Think of it like a test score: higher is healthier.
02What exactly does LARPED read?
Public information only: site and whitepaper text, GitHub metadata, public social-account metadata and history, and on-chain data — contract, holders, LP status and the dev-wallet trail. Nothing behind a login, nothing private.
03Does LARPED interact with the projects it scores?
Never. No wallet is connected to the target, no transactions are sent, no logins are bypassed, and the project is never contacted. LARPED reads the same public sources you could open yourself — it just reads all of them at once.
04Is a low score an accusation of fraud?
No, and this matters. A LARP Score is a risk signal derived from public data, with the evidence and a timestamp attached. It is not a legal claim of fraud or wrongdoing against any project or person, and it never will be.
05How do you handle false positives?
Thresholds are deliberately biased against false positives — borderline cases land in MIXED rather than LARP. Every flag carries its evidence so readers can judge for themselves, missing data lowers confidence instead of silently scoring zero, and anyone can dispute a report for human review.
06Can a founder dispute a report?
Yes. Anyone — founder or not — can flag a report for human review from the report page. The status is tracked, and reports are corrected when the review finds we got it wrong.
07Why does a score change over time?
Because projects change. A repo gets deleted, LP unlocks, a top holder dumps, socials get scrubbed. Every report is timestamped and reflects the public record at the moment of the check — re-check for the latest, or add the project to a watchlist and get told when something material moves.
08How is this different from a contract scanner?
Contract scanners answer one question: will this token trap my funds? That is one of six dimensions here. A contract can be perfectly safe while the project is a total LARP — reskinned docs, empty repo, rented followers, a dev wallet with history. LARPED scores the whole project.
09Can a project game the score?
Faking one layer is easy. Faking all six at once — original docs, a real commit history, aged organic socials, a clean contract, distributed holders and a clean wallet trail — is most of the work of actually being real. The weighting curve and pattern library stay private, and detectors are re-tuned against fresh rugs.
10Do I need a wallet or an account?
No. Checks run without connecting anything, and public report pages open for anyone. A wallet is optional and only ever used to read your live $LARPED balance for tier perks — never required to run a check.
11Is it free?
Yes, and it stays that way. The free tier includes daily checks, the score, the top red flags, public report links and watchlist slots. $LARPED buys quota, depth, speed and API access — never the score or its correctness.
12Has $LARPED launched?
Not yet. There is no contract address, no presale, and no whitelist. The CA will be announced only from @larped_fun and t.me/larped_fun and posted on this page. Anyone DMing you an early allocation is a scammer.
13Is this financial advice?
No. LARPED describes public signals about authenticity — it never gives a buy, sell or hold recommendation, and a high score is not an endorsement. DYOR. NFA.
14Are you affiliated with Robinhood?
No. LARPED is an independent application and is not affiliated with, endorsed by, or sponsored by Robinhood Markets, Inc. “Robinhood Chain” is referenced solely to identify the underlying public blockchain network.