on record

Program Stats

mainnet·last 7d·1,119 programs·510 new · 609 upgrades

Deploys over timei

012525011/1411/1611/1711/1911/20

Frameworksi

IDL, security.txt, verifiedi

IDL
7.6%
security.txt
6.3%
verified build
2.5%
all three
1.2%

Categoriesi

Integrationsi

SPL Token
251
Token-2022
155
Associated Token
77
Pump.fun
65
Meteora DLMM
47
Raydium CLMM
36
Orca Whirlpool
33
Raydium AMM
28
Jupiter
12
Metaplex Metadata
11

Identityi

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

Lineagei

Controli

Build machinei

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

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

sBPF versioni

v342234% → 40%▲ +6pp
v2392% → 4%→ +2pp
v140% → 0%→ +0pp
v065463% → 56%▼ -7pp

Recycled — byte-clone redeploysi

7.6%of today's 510 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.
39
Pump.fun snipersThe confident bot subset: redeploys wired to Pump.fun — the launch-sniper signature.
13
already closedDeploys whose ProgramData is already gone — rent reclaimed, likely a throwaway bot that moved on.
1086
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 7d · updated 2026-11-21 12:40 UTC