on record

Program Stats

mainnet·last 1y·since Jul 9, 2026i·8,071 programs·3,791 new · 4,280 upgrades

Deploys over timei

0500010000archiverecord startsNov '25Feb '26Apr '26Jul '26Sep '26

Frameworksi

anchor406560% → 46%▼ -14pp
native210322% → 30%▲ +8pp
pinocchio163817% → 23%▲ +5pp
unknown1081% → 2%→ +0pp
anchor v2210% → 0%→ +0pp
quasar10% → 0%→ 0pp

IDL, security.txt, verifiedi

IDL
10.4%
security.txt
8.8%
verified build
3.9%
all three
1%

Categoriesi

DEX
502
STAKING
338
LAUNCHPAD
158
LENDING
85
PERPS
89
BRIDGE
115
ORACLE
90
NFT
85
GOV
52
AIRDROP
23
TOKEN
50
INFRA
94
DEFI
484
UNKNOWN
5771

Integrationsi

SPL Token
4091
Token-2022
2667
Associated Token
1310
Pump.fun
670
Meteora DLMM
432
Raydium CLMM
382
Orca Whirlpool
372
Metaplex Metadata
315
Raydium AMM
295
Jupiter
181

Identityi

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

Lineagei

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

Controli

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

Build machinei

MacBuilt with the macOS platform-tools download, or on a Mac home folder.
2149
LinuxBuilt with the Linux download. Includes Docker builds.
2814
no clueNo machine paths left in the binary: stripped or remapped at build time.
2949
not readNo stored bytecode to read yet.
24

Fundingi

known entityDeployer was funded from a labeled exchange or bridge.
24
traced funderFunded from a specific wallet we could trace, but not a labeled entity.
34
untracedCouldn't reach the funding origin.
7878

sBPF versioni

v314670% → 25%▲ +25pp
v2860% → 1%→ +1pp
v1280% → 0%→ +0pp
v032151% → 54%▲ +53pp
not read327599% → 19%▼ -80pp

Recycled — byte-clone redeploysi

6.7%of today's 3,791 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.
253
Pump.fun snipersThe confident bot subset: redeploys wired to Pump.fun — the launch-sniper signature.
23
already closedDeploys whose ProgramData is already gone — rent reclaimed, likely a throwaway bot that moved on.
13273
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 1y · updated 2026-11-20 15:34 UTC