on record

Program Stats

mainnet·last 48h·409 programs·168 new · 241 upgrades

Deploys over timei

05010011/19 16:0011/20 02:0011/20 12:0011/20 22:0011/21 08:00

Frameworksi

IDL, security.txt, verifiedi

IDL
9.5%
security.txt
5.1%
verified build
2.2%
all three
0.7%

Categoriesi

Integrationsi

SPL Token
75
Token-2022
44
Associated Token
23
Pump.fun
22
Meteora DLMM
16
Raydium AMM
13
Raydium CLMM
13
Orca Whirlpool
13
Metaplex Metadata
5
Compute Budget
3

Identityi

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

Lineagei

Controli

Build machinei

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

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.
207

sBPF versioni

v312434% → 27%▼ -7pp
v2246% → 6%→ +0pp
v120% → 1%→ +1pp
v025960% → 66%▲ +5pp

Recycled — byte-clone redeploysi

16.7%of today's 168 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.
28
Pump.fun snipersThe confident bot subset: redeploys wired to Pump.fun — the launch-sniper signature.
16
already closedDeploys whose ProgramData is already gone — rent reclaimed, likely a throwaway bot that moved on.
163
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 48h · updated 2026-11-21 03:07 UTC