on record

Program Stats

last 48h·258 programs·153 new · 105 upgrades

Deploys over timei

Deploys vs upgradesi

new programs
153
upgrades
105

Frameworksi

anchor12247% → 48%→ +1pp
pinocchio10244% → 36%▼ -8pp
native349% → 16%▲ +7pp

Integrationsi

SPL Token
95
Pump.fun
74
Token-2022
64
Associated Token
23
Meteora DLMM
14
Raydium CLMM
12
Orca Whirlpool
9
Raydium AMM
8
Metaplex Metadata
5
Jupiter
5

Categoriesi

DEFI
150
TOKEN
2
NFT
18
INFRA
2
GOV
0
UNKNOWN
86

Identityi

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

Lineagei

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

Controli

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

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.
5
untracedCouldn't reach the funding origin.
253

Recycled — byte-clone redeploysi

64.7%of today's 153 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.
99
Pump.fun snipersThe confident bot subset: redeploys wired to Pump.fun — the launch-sniper signature.
67
already closedDeploys whose ProgramData is already gone — rent reclaimed, likely a throwaway bot that moved on.
102
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 48hh · updated 2026-07-13 15:32 UTC