on record

Program Stats

mainnet·all·since Jul 9, 2026i·8,101 programs·3,817 new · 4,284 upgrades

Deploys over timei

0500010000archiverecord startsMar '22Mar '23Feb '24Jan '25Dec '25

Frameworksi

anchor407860% → 45%▼ -14pp
native211422% → 30%▲ +8pp
pinocchio164617% → 23%▲ +5pp
unknown1081% → 2%→ +0pp
anchor v2210% → 0%→ +0pp
quasar10% → 0%→ 0pp

IDL, security.txt, verifiedi

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

Categoriesi

DEX
505
STAKING
334
LAUNCHPAD
160
LENDING
86
PERPS
89
BRIDGE
115
ORACLE
91
NFT
84
GOV
52
AIRDROP
23
TOKEN
50
INFRA
93
DEFI
488
UNKNOWN
5798

Integrationsi

SPL Token
4104
Token-2022
2678
Associated Token
1310
Pump.fun
674
Meteora DLMM
439
Raydium CLMM
390
Orca Whirlpool
380
Metaplex Metadata
316
Raydium AMM
303
Jupiter
184

Identityi

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

Lineagei

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

Controli

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

Build machinei

MacBuilt with the macOS platform-tools download, or on a Mac home folder.
2145
LinuxBuilt with the Linux download. Includes Docker builds.
2828
no clueNo machine paths left in the binary: stripped or remapped at build time.
2971
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.
7910

sBPF versioni

v314770% → 25%▲ +25pp
v2920% → 2%→ +1pp
v1300% → 1%→ +1pp
v032291% → 54%▲ +54pp
not read327399% → 19%▼ -80pp

Recycled — byte-clone redeploysi

6.8%of today's 3,817 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.
259
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.
13392
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 all · updated 2026-11-21 11:21 UTC