on record

Program Stats

last 168h·735 programs·330 new · 405 upgrades

Deploys over timei

01002007/77/87/107/117/13

Frameworksi

anchor33552% → 43%▼ -9pp
pinocchio28531% → 42%▲ +11pp
native10516% → 14%▼ -2pp
unknown101% → 1%→ +0pp

Categoriesi

DEFI
455
TOKEN
8
NFT
34
INFRA
7
GOV
2
UNKNOWN
229

Integrationsi

SPL Token
312
Token-2022
216
Pump.fun
169
Associated Token
76
Meteora DLMM
50
Raydium CLMM
39
Orca Whirlpool
34
Raydium AMM
31
Jupiter
20
Metaplex Metadata
18

Identityi

namedA project name was recovered from the binary.
354
has repoA source-code repo was found in the binary or a verified build.
15
opaqueNo name, repo, or security.txt — anonymous bytecode.
379

Lineagei

novelNo known code relative on record — genuinely new code.
121
variantLoosely similar to a known program, but not a direct copy.
403
fork≥60% code match to a known program — a fork or close derivative.
211

Controli

mutableHas an upgrade authority — the deployer can still replace the code (including to rug).
733
frozenUpgrade authority is null — the code can never be changed by anyone.
2
verified buildThe on-chain bytecode reproduces from public source code.
7

Fundingi

known entityDeployer was funded from a labeled exchange or bridge.
0
traced funderFunded from a specific wallet we could trace, but not a labeled entity.
167
untracedCouldn't reach the funding origin.
568

Recycled — byte-clone redeploysi

62.4%of today's 330 new deploys are byte-clone redeploys, not new code
redeploysNew deploys that are byte-clones of known code — same program, fresh id. A fact, not a judgment.
206
Pump.fun snipersThe confident bot subset: redeploys wired to Pump.fun — the launch-sniper signature.
138
already closedDeploys whose ProgramData is already gone — rent reclaimed, likely a throwaway bot that moved on.
227
What's a throwaway bot?

A disposable on-chain program a trader deploys to run one strategy — almost always sniping new Pump.fun token launches — then closes minutes later to reclaim its rent, redeploying under a fresh id for the next run.

Why a program at all?

Sniping means "buy the instant the pool exists, atomically, or abort" — you can't do that reliably from a wallet. A tiny custom program bundles the whole attempt (and often multi-venue routing) into a single instruction that either lands complete or reverts.

Why thousands of failed transactions?

That's the race. The bot fires on every launch; most attempts lose the block or the token rugs, so they revert. The failures are the strategy — spray for the few that land.

Why redeploy and close?

The ~0.2 SOL of rent is refundable on close, and a fresh program id sidesteps any blocklist or reputation built against a known address. Cheaper and stealthier to burn identities than to keep one — so one operator can wear dozens of "new program" identities in a day.

How On Record catches it

Exact-bytecode dedup (same sha256 = same bot) collapses the redeploys into one cluster; lifecycle tracking sees the deploy → close; the failed-tx count confirms the intent. No explorer distinguishes "new protocol" from "same bot, 30th identity today" — that's a novelty-definition problem, which is exactly what this radar solves.

last 7dh · updated 2026-07-13 21:02 UTC