on record

Program Stats

mainnet·last 30d·3,249 programs·1,455 new · 1,794 upgrades

Deploys over timei

0500100010/2310/2911/411/1011/16

Frameworksi

IDL, security.txt, verifiedi

IDL
8.3%
security.txt
7.5%
verified build
3%
all three
1.2%

Categoriesi

Integrationsi

SPL Token
989
Token-2022
649
Associated Token
340
Pump.fun
205
Meteora DLMM
138
Orca Whirlpool
117
Raydium CLMM
116
Raydium AMM
91
Metaplex Metadata
59
Jupiter
45

Identityi

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

Lineagei

Controli

Build machinei

MacBuilt with the macOS platform-tools download, or on a Mac home folder.
399
LinuxBuilt with the Linux download. Includes Docker builds.
626
no clueNo machine paths left in the binary: stripped or remapped at build time.
1144

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

sBPF versioni

v3102127% → 34%▲ +7pp
v2711% → 3%→ +1pp
v1181% → 1%→ +0pp
v0213671% → 62%▼ -8pp
not read30% → 0%→ 0pp

Recycled — byte-clone redeploysi

9%of today's 1,455 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.
131
Pump.fun snipersThe confident bot subset: redeploys wired to Pump.fun — the launch-sniper signature.
25
already closedDeploys whose ProgramData is already gone — rent reclaimed, likely a throwaway bot that moved on.
3471
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 30d · updated 2026-11-21 14:44 UTC