on record

Program Stats

mainnet·last 90d·6,710 programs·3,101 new · 3,609 upgrades

Deploys over timei

0100020008/179/49/2210/1010/28

Frameworksi

anchor281255% → 44%▼ -11pp
native167726% → 30%▲ +4pp
pinocchio119517% → 23%▲ +6pp
unknown911% → 2%→ +1pp
anchor v2180% → 0%→ 0pp
quasar00% → 0%→ +0pp

IDL, security.txt, verifiedi

IDL
10.1%
security.txt
8.9%
verified build
3.8%
all three
0.9%

Categoriesi

DEX
342
STAKING
212
LAUNCHPAD
106
LENDING
56
PERPS
58
BRIDGE
79
ORACLE
57
NFT
42
GOV
37
AIRDROP
15
TOKEN
26
INFRA
62
DEFI
334
UNKNOWN
4367

Integrationsi

SPL Token
2875
Token-2022
1939
Associated Token
945
Pump.fun
514
Meteora DLMM
294
Raydium CLMM
270
Orca Whirlpool
260
Raydium AMM
206
Metaplex Metadata
195
Jupiter
126

Identityi

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

Lineagei

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

Controli

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

Build machinei

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

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

sBPF versioni

v312860% → 27%▲ +27pp
v2820% → 2%→ +2pp
v1250% → 1%→ +0pp
v029801% → 62%▲ +61pp
not read233799% → 9%▼ -90pp

Recycled — byte-clone redeploysi

7.8%of today's 3,101 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.
242
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.
8472
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-12 15:30 UTC