on record

Program Stats

mainnet·last 24h·216 programs·108 new · 108 upgrades

Deploys over timei

0255015:0020:0001:0006:0011:00

Frameworksi

IDL, security.txt, verifiedi

IDL
8.8%
security.txt
5.6%
verified build
1.9%
all three
0.9%

Categoriesi

Integrationsi

SPL Token
46
Token-2022
28
Meteora DLMM
16
Orca Whirlpool
15
Raydium CLMM
14
Raydium AMM
12
Pump.fun
11
Associated Token
9
Metaplex Metadata
3
Jupiter
3

Identityi

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

Lineagei

Controli

Build machinei

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

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

sBPF versioni

v35830% → 23%▼ -7pp
v2145% → 8%▲ +3pp
v122% → 0%→ -2pp
v014264% → 68%▲ +5pp

Recycled — byte-clone redeploysi

23.1%of today's 108 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.
25
Pump.fun snipersThe confident bot subset: redeploys wired to Pump.fun — the launch-sniper signature.
14
already closedDeploys whose ProgramData is already gone — rent reclaimed, likely a throwaway bot that moved on.
62
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 24h · updated 2026-11-21 14:50 UTC