on record

Program Stats

mainnet·last 90d·6,869 programs·3,278 new · 3,591 upgrades

Deploys over timei

0100020008/249/119/2910/1711/4

Frameworksi

anchor277152% → 43%▼ -9pp
native176928% → 32%▲ +4pp
pinocchio126019% → 23%▲ +4pp
unknown851% → 2%→ +1pp
anchor v2170% → 0%→ +0pp
quasar00% → 0%→ +0pp

IDL, security.txt, verifiedi

IDL
9.6%
security.txt
8.8%
verified build
3.6%
all three
0.9%

Categoriesi

DEX
328
STAKING
209
LAUNCHPAD
102
LENDING
50
PERPS
59
BRIDGE
82
ORACLE
55
NFT
42
GOV
33
AIRDROP
15
TOKEN
27
INFRA
69
DEFI
321
UNKNOWN
4510

Integrationsi

SPL Token
2861
Token-2022
1919
Associated Token
949
Pump.fun
536
Meteora DLMM
311
Raydium CLMM
273
Orca Whirlpool
259
Raydium AMM
211
Metaplex Metadata
194
Jupiter
126

Identityi

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

Lineagei

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

Controli

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

Build machinei

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

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

sBPF versioni

v315532% → 32%▲ +30pp
v2860% → 2%→ +2pp
v1280% → 1%→ +1pp
v032207% → 65%▲ +59pp
not read198291% → 0%▼ -91pp

Recycled — byte-clone redeploysi

7.1%of today's 3,278 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.
232
Pump.fun snipersThe confident bot subset: redeploys wired to Pump.fun — the launch-sniper signature.
26
already closedDeploys whose ProgramData is already gone — rent reclaimed, likely a throwaway bot that moved on.
9291
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 90d · updated 2026-11-20 15:33 UTC